From: Yicong Yang <yangyicong@huawei.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: <yangyicong@hisilicon.com>, <catalin.marinas@arm.com>,
<will@kernel.org>, <sudeep.holla@arm.com>, <tglx@linutronix.de>,
<peterz@infradead.org>, <mpe@ellerman.id.au>,
<linux-arm-kernel@lists.infradead.org>, <mingo@redhat.com>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>,
<pierre.gondois@arm.com>, <dietmar.eggemann@arm.com>,
<linuxppc-dev@lists.ozlabs.org>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <morten.rasmussen@arm.com>,
<msuchanek@suse.de>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <prime.zeng@hisilicon.com>,
<linuxarm@huawei.com>, <xuwei5@huawei.com>,
<guohanjun@huawei.com>
Subject: Re: [PATCH v10 3/4] arm64: topology: Support SMT control on ACPI based system
Date: Tue, 24 Dec 2024 20:30:14 +0800 [thread overview]
Message-ID: <a5dfbe0a-43aa-ee0d-fdb4-af2e2a2cc854@huawei.com> (raw)
In-Reply-To: <20241223164014.000032cc@huawei.com>
On 2024/12/24 0:40, Jonathan Cameron wrote:
> On Fri, 20 Dec 2024 15:53:12 +0800
> Yicong Yang <yangyicong@huawei.com> wrote:
>
>> From: Yicong Yang <yangyicong@hisilicon.com>
>>
>> For ACPI we'll build the topology from PPTT and we cannot directly
>> get the SMT number of each core. Instead using a temporary xarray
>> to record the heterogeneous information (from ACPI_PPTT_ACPI_IDENTICAL)
>> and SMT information of the first core in its heterogeneous CPU cluster
>> when building the topology. Then we can know the largest SMT number
>> in the system. If a homogeneous system's using ACPI 6.2 or later,
>> all the CPUs should be under the root node of PPTT. There'll be
>> only one entry in the xarray and all the CPUs in the system will
>> be assumed identical.
>>
>> The core's SMT control provides two interface to the users [1]:
>> 1) enable/disable SMT by writing on/off
>> 2) enable/disable SMT by writing thread number 1/max_thread_number
>>
>> If a system have more than one SMT thread number the 2) may
>> not handle it well, since there're multiple thread numbers in the
>> system and 2) only accept 1/max_thread_number. So issue a warning
>> to notify the users if such system detected.
>>
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/sysfs-devices-system-cpu#n542
>> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
>
> A few trivial things inline. Either way it's fine as really just my style
> preferences
>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
>> ---
>> arch/arm64/kernel/topology.c | 66 ++++++++++++++++++++++++++++++++++++
>> 1 file changed, 66 insertions(+)
>>
>> diff --git a/arch/arm64/kernel/topology.c b/arch/arm64/kernel/topology.c
>> index 1a2c72f3e7f8..85cb18d72a29 100644
>> --- a/arch/arm64/kernel/topology.c
>> +++ b/arch/arm64/kernel/topology.c
>> @@ -15,8 +15,10 @@
>> #include <linux/arch_topology.h>
>> #include <linux/cacheinfo.h>
>> #include <linux/cpufreq.h>
>> +#include <linux/cpu_smt.h>
>> #include <linux/init.h>
>> #include <linux/percpu.h>
>> +#include <linux/xarray.h>
>>
>> #include <asm/cpu.h>
>> #include <asm/cputype.h>
>> @@ -37,17 +39,28 @@ static bool __init acpi_cpu_is_threaded(int cpu)
>> return !!is_threaded;
>> }
>>
>> +struct cpu_smt_info {
>> + int thread_num;
>> + int core_id;
>> +};
>> +
>> /*
>> * Propagate the topology information of the processor_topology_node tree to the
>> * cpu_topology array.
>> */
>> int __init parse_acpi_topology(void)
>> {
>> + int max_smt_thread_num = 0;
>> + struct cpu_smt_info *entry;
>> + struct xarray hetero_cpu;
>> + unsigned long hetero_id;
>> int cpu, topology_id;
>>
>> if (acpi_disabled)
>> return 0;
>>
>> + xa_init(&hetero_cpu);
>> +
>> for_each_possible_cpu(cpu) {
>> topology_id = find_acpi_cpu_topology(cpu, 0);
>> if (topology_id < 0)
>> @@ -57,6 +70,32 @@ int __init parse_acpi_topology(void)
>> cpu_topology[cpu].thread_id = topology_id;
>> topology_id = find_acpi_cpu_topology(cpu, 1);
>> cpu_topology[cpu].core_id = topology_id;
>> +
>> + /*
>> + * In the PPTT, CPUs below a node with the 'identical
>> + * implementation' flag have the same number of threads.
>> + * Count the number of threads for only one CPU (i.e.
>> + * one core_id) among those with the same hetero_id.
>> + * See the comment of find_acpi_cpu_topology_hetero_id()
>> + * for more details.
>> + *
>> + * One entry is created for each node having:
>> + * - the 'identical implementation' flag
>> + * - its parent not having the flag
>> + */
>> + hetero_id = find_acpi_cpu_topology_hetero_id(cpu);
>> + entry = (struct cpu_smt_info *)xa_load(&hetero_cpu, hetero_id);
>
> Given xa_load returns a void *,
>
> entry = xa_load(&hetero_cpu, hetero_id);
>
> should be fine (I haven't checked local style, so feel free to ignore if
> local style is to cast anyway). Maybe drag the definition of entry into
> a more local scope as well.
>
sure. will get rid of the cast and checked it won't violate the local style.
>
>> + if (!entry) {
>> + entry = kzalloc(sizeof(*entry), GFP_KERNEL);
>> + WARN_ON(!entry);
>> +
>> + entry->core_id = topology_id;
>> + entry->thread_num = 1;
>> + xa_store(&hetero_cpu, hetero_id,
>> + entry, GFP_KERNEL);
>> + } else if (entry->core_id == topology_id) {
>> + entry->thread_num++;
>> + }
>> } else {
>> cpu_topology[cpu].thread_id = -1;
>> cpu_topology[cpu].core_id = topology_id;
>> @@ -67,6 +106,33 @@ int __init parse_acpi_topology(void)
>> cpu_topology[cpu].package_id = topology_id;
>> }
>>
>> + /*
>> + * This should be a short loop depending on the number of heterogeneous
>> + * CPU clusters. Typically on a homogeneous system there's only one
>> + * entry in the XArray.
>> + */
>> + xa_for_each(&hetero_cpu, hetero_id, entry) {
>> + if (entry->thread_num != max_smt_thread_num && max_smt_thread_num)
>> + pr_warn_once("Heterogeneous SMT topology is partly supported by SMT control\n");
>> +
>> + if (entry->thread_num > max_smt_thread_num)
>> + max_smt_thread_num = entry->thread_num;
>
> As with DT, maybe min is more informative?
>
> max_smt_thread_num = min(max_smt_thread_num, entry->thread_num);
>
> I don't care strongly about it though.
either's ok with me, will keep it consistent with DT.
Thanks.
next prev parent reply other threads:[~2024-12-24 12:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 7:53 [PATCH v10 0/4] Support SMT control on arm64 Yicong Yang
2024-12-20 7:53 ` [PATCH v10 1/4] cpu/SMT: Provide a default topology_is_primary_thread() Yicong Yang
2024-12-20 7:59 ` Yicong Yang
2024-12-23 16:34 ` Jonathan Cameron
2024-12-24 12:15 ` Yicong Yang
2024-12-26 7:18 ` Shrikanth Hegde
2024-12-26 11:36 ` Yicong Yang
2024-12-20 7:53 ` [PATCH v10 2/4] arch_topology: Support SMT control for OF based system Yicong Yang
2024-12-23 16:33 ` Jonathan Cameron
2024-12-24 12:23 ` Yicong Yang
2024-12-20 7:53 ` [PATCH v10 3/4] arm64: topology: Support SMT control on ACPI " Yicong Yang
2024-12-23 16:40 ` Jonathan Cameron
2024-12-24 12:30 ` Yicong Yang [this message]
2024-12-20 7:53 ` [PATCH v10 4/4] arm64: Kconfig: Enable HOTPLUG_SMT Yicong Yang
2024-12-23 16:40 ` Jonathan Cameron
2024-12-26 9:23 ` [PATCH v10 0/4] Support SMT control on arm64 Shrikanth Hegde
2024-12-26 11:50 ` Yicong Yang
2024-12-26 12:28 ` Shrikanth Hegde
2024-12-27 7:16 ` Yicong Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a5dfbe0a-43aa-ee0d-fdb4-af2e2a2cc854@huawei.com \
--to=yangyicong@huawei.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=guohanjun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=peterz@infradead.org \
--cc=pierre.gondois@arm.com \
--cc=prime.zeng@hisilicon.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xuwei5@huawei.com \
--cc=yangyicong@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®