From: Pierre Gondois <pierre.gondois@arm.com>
To: Yicong Yang <yangyicong@huawei.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,
dietmar.eggemann@arm.com
Cc: 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,
jonathan.cameron@huawei.com, prime.zeng@hisilicon.com,
linuxarm@huawei.com, yangyicong@hisilicon.com, xuwei5@huawei.com,
guohanjun@huawei.com
Subject: Re: [PATCH v6 2/4] arch_topology: Support SMT control for OF based system
Date: Wed, 23 Oct 2024 17:43:29 +0200 [thread overview]
Message-ID: <eb7ec4c3-5995-4040-8992-bb95f4b9f923@arm.com> (raw)
In-Reply-To: <20241015021841.35713-3-yangyicong@huawei.com>
Hello Yicong,
On 10/15/24 04:18, Yicong Yang wrote:
> From: Yicong Yang <yangyicong@hisilicon.com>
>
> On building the topology from the devicetree, we've already
> gotten the SMT thread number of each core. Update the largest
> SMT thread number and enable the SMT control by the end of
> topology parsing.
>
> 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>
> ---
> drivers/base/arch_topology.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
> index 75fcb75d5515..5eed864df5e6 100644
> --- a/drivers/base/arch_topology.c
> +++ b/drivers/base/arch_topology.c
> @@ -11,6 +11,7 @@
> #include <linux/cleanup.h>
> #include <linux/cpu.h>
> #include <linux/cpufreq.h>
> +#include <linux/cpu_smt.h>
> #include <linux/device.h>
> #include <linux/of.h>
> #include <linux/slab.h>
> @@ -28,6 +29,7 @@
> static DEFINE_PER_CPU(struct scale_freq_data __rcu *, sft_data);
> static struct cpumask scale_freq_counters_mask;
> static bool scale_freq_invariant;
> +static unsigned int max_smt_thread_num;
> DEFINE_PER_CPU(unsigned long, capacity_freq_ref) = 1;
> EXPORT_PER_CPU_SYMBOL_GPL(capacity_freq_ref);
>
> @@ -561,6 +563,17 @@ static int __init parse_core(struct device_node *core, int package_id,
> i++;
> } while (1);
>
> + if (max_smt_thread_num < i)
> + max_smt_thread_num = i;
Shouldn't the conditions above/below be inverted ?
I.e. (max_smt_thread_num != i) should never be true if there is
max_smt_thread_num = i;
just before
> +
> + /*
> + * If max_smt_thread_num has been initialized and doesn't match
> + * the thread number of this entry, then the system has
> + * heterogeneous SMT topology.
> + */
> + if (max_smt_thread_num && max_smt_thread_num != i)
> + pr_warn_once("Heterogeneous SMT topology is partly supported by SMT control\n");
> +
> cpu = get_cpu_for_node(core);
> if (cpu >= 0) {
> if (!leaf) {
> @@ -673,6 +686,14 @@ static int __init parse_socket(struct device_node *socket)
> if (!has_socket)
> ret = parse_cluster(socket, 0, -1, 0);
>
> + /*
> + * Notify the CPU framework of the SMT support. A thread number of 1
> + * can be handled by the framework so we don't need to check
> + * max_smt_thread_num to see we support SMT or not.
> + */
> + if (max_smt_thread_num)
> + cpu_smt_set_num_threads(max_smt_thread_num, max_smt_thread_num);
> +
> return ret;
> }
>
next prev parent reply other threads:[~2024-10-23 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 2:18 [PATCH v6 0/4] Support SMT control on arm64 Yicong Yang
2024-10-15 2:18 ` [PATCH v6 1/4] cpu/SMT: Provide a default topology_is_primary_thread() Yicong Yang
2024-10-15 2:18 ` [PATCH v6 2/4] arch_topology: Support SMT control for OF based system Yicong Yang
2024-10-16 3:03 ` kernel test robot
2024-10-16 6:19 ` kernel test robot
2024-10-23 15:43 ` Pierre Gondois [this message]
2024-10-24 14:47 ` Yicong Yang
2024-10-15 2:18 ` [PATCH v6 3/4] arm64: topology: Support SMT control on ACPI " Yicong Yang
2024-10-24 8:44 ` Pierre Gondois
2024-10-24 15:09 ` Yicong Yang
2024-10-15 2:18 ` [PATCH v6 4/4] arm64: Kconfig: Enable HOTPLUG_SMT 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=eb7ec4c3-5995-4040-8992-bb95f4b9f923@arm.com \
--to=pierre.gondois@arm.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=jonathan.cameron@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=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 \
--cc=yangyicong@huawei.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