Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp12807015rwd; Fri, 23 Jun 2023 10:55:26 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ74aspax90ng2NG16rHfWbpEMLzOrJ/5YDUXPmuoBllc7T2RNLdV6y1Ru+13FcuBIbybe6y X-Received: by 2002:a17:90a:1906:b0:25b:dae4:205 with SMTP id 6-20020a17090a190600b0025bdae40205mr11310730pjg.32.1687542926105; Fri, 23 Jun 2023 10:55:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687542926; cv=none; d=google.com; s=arc-20160816; b=q35zJ9HP+DWCT/vcNhAZJZZBFT9c4Vvc3tSFiHpp3w43vAj+8Zyx8MhLAznwxA6NJn QCRJBJLvUjg+YrG25Vspx+kOTZHgdJam8o4IpIgeHJk3Zq3/tzOwZ0DVNURDfRxhAEvG pZPo1HSq0Ezzlmz8y7tmI7HGrZVoFw/2BvcrPv5bFxPi2njImA4K2MuKmx0gUOZbEHvT KZqQ8hIK2xgl5Lb7DvTAE+uiIgSLj6Dxv5kMSBbiuvIgKf3YV1Jm8hU4byRS7bD11uVR PCHVTMtIzztQthUcWTDmJHo8I/O7r52BTpV7KRx/HhjYyekGDyliRn3gi0OCkyLR6T6P 1E8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=jk2Q+3BObVQgNnldSFI+vDMtiYVrVMXbHswqqG1uq+g=; b=0lJHdpJBm9k75JK8gxCRRkVTTVJNkTBhDzXq9JxNj6RFPLodLXCkE0drzEVI+ZuzQG q8mynD6Jj0x0+bSVD+Xq3JPMFPX5mJyV9Y+srWlX1/saMRNzgyKNZqOm0/+mH5nRhdvh pcoz1zemd6aM6uTwgyxD35B4H0nqSZWzsLheNaxmsWo2LoPPLFbWIWwPSmrxQhn7d6R8 83rqcMrXq48S/QLEB80QVm6IYdDDOIn8En7pl8M3W/S1pFDJTd4lu1bwOE1juqfdLqkP P0okb3HtUWWVBBpP0xN/l/9mpSv/UR38owDxX2+4KYQYux4Miq9ri2Mx4LjNBBqjAhzX vxyQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@xen0n.name header.s=mail header.b=c7ReWnrw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x4-20020a63db44000000b005486a1e9440si9789762pgi.780.2023.06.23.10.55.07; Fri, 23 Jun 2023 10:55:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@xen0n.name header.s=mail header.b=c7ReWnrw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231887AbjFWReU (ORCPT + 99 others); Fri, 23 Jun 2023 13:34:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53148 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229451AbjFWReS (ORCPT ); Fri, 23 Jun 2023 13:34:18 -0400 Received: from mailbox.box.xen0n.name (mail.xen0n.name [115.28.160.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B745E1FC2; Fri, 23 Jun 2023 10:34:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xen0n.name; s=mail; t=1687541652; bh=uijmNbUmIlHkh56jJTNP2T+S8lHX64iWOnrHTLZxmMY=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=c7ReWnrwTc9Z/yK/YxC63JsOxA9Ryx737DuAuXNPnXzjONrx43KxaW58qqTnmf5wa vcBAKCY6htQxSV4Ljc8ozyQ9fQAqvAKLzv2/2cTylYnPWouKP8/3deP8ypWTkbt+hO JkcqaXhSmlP1nGMj2yVoRdr+ONFZJkcIRgT8V2AU= Received: from [192.168.9.172] (unknown [101.88.25.181]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mailbox.box.xen0n.name (Postfix) with ESMTPSA id E9C0C600A9; Sat, 24 Jun 2023 01:34:11 +0800 (CST) Message-ID: Date: Sat, 24 Jun 2023 01:34:11 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH] LoongArch: Add SMT (Simultaneous Multi-Threading) support Content-Language: en-US To: "Rafael J. Wysocki" , Huacai Chen Cc: Liupu Wang , Len Brown , Jianmin Lv , Marc Zyngier , Tiezhu Yang , Binbin Zhou , Bibo Mao , Josh Poimboeuf , loongarch@lists.linux.dev, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, Huacai Chen References: <20230614093755.88881-1-wangliupu@loongson.cn> From: WANG Xuerui In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 6/24/23 01:20, Rafael J. Wysocki wrote: > On Thu, Jun 15, 2023 at 4:31 AM Huacai Chen wrote: >> Hi, Rafael, >> >> On Thu, Jun 15, 2023 at 2:24 AM Rafael J. Wysocki wrote: >>> On Wed, Jun 14, 2023 at 11:38 AM Liupu Wang wrote: >>>> [snip] >>>> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig >>>> index ccbeab9500ec..00dd309b6682 100644 >>>> --- a/drivers/acpi/Kconfig >>>> +++ b/drivers/acpi/Kconfig >>>> @@ -542,10 +542,10 @@ config ACPI_PFRUT >>>> >>>> if ARM64 >>>> source "drivers/acpi/arm64/Kconfig" >>>> +endif >>>> >>>> config ACPI_PPTT >>>> bool >>>> -endif >>> x86 doesn't use PPTT as of today. Why do you enable it for them? >> ACPI_PPTT is an invisible symbol, it cannot be enabled by explicitly >> selecting and its default value is n, so I think it isn't enabled for >> x86. On the other hand, moving it out of ARM64 can make other archs >> don't need to modify this file any more if they need PPTT. > AFAICS, setting ACPI_PPTT causes pptt.c to be compiled and if it is > never going to be used by the given arch, it will just be dead code. > > Can't this be avoided? FYI I've just tried a x86_64 defconfig build and ACPI_PPTT isn't being enabled, nor is there a pptt.o signifying the same thing. > drivers/acpi/Makefile > 109:obj-$(CONFIG_ACPI_PPTT)     += pptt.o This should mean that, if nothing is selecting ACPI_PPTT then the file isn't going to be compiled? Right now it seems only arch/arm64 and arch/loongarch are doing so based on my cursory grep. Or do you mean we should be extra careful and keep the guard around the symbol to ensure it's nonexistent on other irrelevant arches? -- WANG "xen0n" Xuerui Linux/LoongArch mailing list: https://lore.kernel.org/loongarch/