From: Yicong Yang <hidden> Date: 2024-10-30 12:54:53
From: Yicong Yang <redacted>
The core CPU control framework supports runtime SMT control which
is not yet supported on arm64. Besides the general vulnerabilities
concerns we want this runtime control on our arm64 server for:
- better single CPU performance in some cases
- saving overall power consumption
This patchset implements it in the following aspects:
- Provides a default topology_is_primary_thread()
- support retrieve SMT thread number on OF based system
- support retrieve SMT thread number on ACPI based system
- select HOTPLUG_SMT for arm64
Tests has been done on our real ACPI based arm64 server and on
ACPI/OF based QEMU VMs.
Change since v6:
- Fix unused variable if !CONFIG_ARM64 || !CONFIG_RISV found by lkp-test
- Fix max_smt_thread_num updating in OF path pointed by Pierre
- Drop unused variable and refine the comments/commit per Pierre
Link: https://lore.kernel.org/linux-arm-kernel/20241015021841.35713-1-yangyicong@huawei.com/
Change since v5:
- Drop the dependency on CONFIG_SMP since it's always on on arm64, per Pierre
- Avoid potential multiple calls of cpu_smt_set_num_threads() on asymmetric system, per Dietmar
- Detect heterogenous SMT topology and issue a warning for partly support, per Pierre
- Thanks Dietmar for testing, didn't pickup the tag due to code changes. Thanks testing by Pierre
Link: https://lore.kernel.org/linux-arm-kernel/20240806085320.63514-1-yangyicong@huawei.com/
Change since v4:
- Provide a default topology_is_primary_thread() in the framework, Per Will
Link: https://lore.kernel.org/linux-arm-kernel/20231121092602.47792-1-yangyicong@huawei.com/
Change since v3:
- Fix some build and kconfig error reported by kernel test robot [off-list ref]
Link: https://lore.kernel.org/linux-arm-kernel/20231114040110.54590-1-yangyicong@huawei.com/
Change since v2:
- Detect SMT thread number at topology build from ACPI/DT, avoid looping CPUs
- Split patches into ACPI/OF/arch_topology path and enable the kconfig for arm64
Link: https://lore.kernel.org/linux-arm-kernel/20231010115335.13862-1-yangyicong@huawei.com/
Yicong Yang (4):
cpu/SMT: Provide a default topology_is_primary_thread()
arch_topology: Support SMT control for OF based system
arm64: topology: Support SMT control on ACPI based system
arm64: Kconfig: Enable HOTPLUG_SMT
arch/arm64/Kconfig | 1 +
arch/arm64/kernel/topology.c | 57 +++++++++++++++++++++++++++++
arch/powerpc/include/asm/topology.h | 1 +
arch/x86/include/asm/topology.h | 2 +-
drivers/base/arch_topology.c | 24 ++++++++++++
include/linux/topology.h | 14 +++++++
6 files changed, 98 insertions(+), 1 deletion(-)
--
2.24.0
From: Yicong Yang <hidden> Date: 2024-10-30 12:54:51
From: Yicong Yang <redacted>
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 <redacted>
---
arch/arm64/kernel/topology.c | 57 ++++++++++++++++++++++++++++++++++++
1 file changed, 57 insertions(+)
@@ -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;++/*+*InthePPTT,CPUsbelowanodewiththe'identical+*implementation'flaghavethesamenumberofthreads.+*CountthenumberofthreadsforonlyoneCPU(i.e.+*onecore_id)amongthosewiththesamehetero_id.+*Seethecommentoffind_acpi_cpu_topology_hetero_id()+*formoredetails.+*+*Oneentryiscreatedforeachnodehaving:+*-the'identicalimplementation'flag+*-itsparentnothavingtheflag+*/+hetero_id=find_acpi_cpu_topology_hetero_id(cpu);+entry=(structcpu_smt_info*)xa_load(&hetero_cpu,hetero_id);+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);+}elseif(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,24 @@ int __init parse_acpi_topology(void)cpu_topology[cpu].package_id=topology_id;}+/*+*Thisshouldbeashortloopdependingonthenumberofheterogeneous+*CPUclusters.Typicallyonahomogeneoussystemthere'sonlyone+*entryintheXArray.+*/+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;++xa_erase(&hetero_cpu,hetero_id);+kfree(entry);+}++cpu_smt_set_num_threads(max_smt_thread_num,max_smt_thread_num);+xa_destroy(&hetero_cpu);return0;}#endif
From: Yicong Yang <hidden> Date: 2024-10-30 12:54:55
From: Yicong Yang <redacted>
Currently if architectures want to support HOTPLUG_SMT they need to
provide a topology_is_primary_thread() telling the framework which
thread in the SMT cannot offline. However arm64 doesn't have a
restriction on which thread in the SMT cannot offline, a simplest
choice is that just make 1st thread as the "primary" thread. So
just make this as the default implementation in the framework and
let architectures like x86 that have special primary thread to
override this function (which they've already done).
There's no need to provide a stub function if !CONFIG_SMP or
!CONFIG_HOTPLUG_SMP. In such case the testing CPU is already
the 1st CPU in the SMT so it's always the primary thread.
Signed-off-by: Yicong Yang <redacted>
---
arch/powerpc/include/asm/topology.h | 1 +
arch/x86/include/asm/topology.h | 2 +-
include/linux/topology.h | 14 ++++++++++++++
3 files changed, 16 insertions(+), 1 deletion(-)
From: Yicong Yang <hidden> Date: 2024-10-30 12:54:58
From: Yicong Yang <redacted>
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 <redacted>
---
drivers/base/arch_topology.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
@@ -502,6 +503,10 @@ core_initcall(free_raw_capacity);#endif#if defined(CONFIG_ARM64) || defined(CONFIG_RISCV)++/* Maximum SMT thread number detected used to enable the SMT control */+staticunsignedintmax_smt_thread_num;+/**Thisfunctionreturnsthelogiccpunumberofthenode.*Therearebasicallythreekindsofreturnvalues:
@@ -561,6 +566,17 @@ static int __init parse_core(struct device_node *core, int package_id,i++;}while(1);+/*+*Ifmax_smt_thread_numhasbeeninitializedanddoesn'tmatch+*thethreadnumberofthisentry,thenthesystemhas+*heterogeneousSMTtopology.+*/+if(max_smt_thread_num&&max_smt_thread_num!=i)+pr_warn_once("Heterogeneous SMT topology is partly supported by SMT control\n");++if(max_smt_thread_num<i)+max_smt_thread_num=i;+cpu=get_cpu_for_node(core);if(cpu>=0){if(!leaf){
@@ -673,6 +689,14 @@ static int __init parse_socket(struct device_node *socket)if(!has_socket)ret=parse_cluster(socket,0,-1,0);+/*+*NotifytheCPUframeworkoftheSMTsupport.Athreadnumberof1+*canbehandledbytheframeworksowedon'tneedtocheck+*max_smt_thread_numtoseewesupportSMTornot.+*/+if(max_smt_thread_num)+cpu_smt_set_num_threads(max_smt_thread_num,max_smt_thread_num);+returnret;}
Please do not glue defines and functions together w/o a newline in between.
+static inline bool topology_is_primary_thread(unsigned int cpu)
+{
+ /*
+ * On SMT hotplug the primary thread of the SMT won't be disabled.
+ * Architectures do have a special primary thread (e.g. x86) need
+ * to override this function. Otherwise just make the first thread
+ * in the SMT as the primary thread.
+ */
+ return cpu == cpumask_first(topology_sibling_cpumask(cpu));
How is that supposed to work? Assume both siblings are offline, then the
sibling mask is empty and you can't boot the CPU anymore.
Thanks,
tglx
Please do not glue defines and functions together w/o a newline in between.
sure, will add a newline here.
quoted
+static inline bool topology_is_primary_thread(unsigned int cpu)
+{
+ /*
+ * On SMT hotplug the primary thread of the SMT won't be disabled.
+ * Architectures do have a special primary thread (e.g. x86) need
+ * to override this function. Otherwise just make the first thread
+ * in the SMT as the primary thread.
+ */
+ return cpu == cpumask_first(topology_sibling_cpumask(cpu));
How is that supposed to work? Assume both siblings are offline, then the
sibling mask is empty and you can't boot the CPU anymore.
For architectures' using arch_topology, topology_sibling_cpumask() will at least
contain the tested CPU itself. This is initialized in
drivers/base/arch_topology.c:reset_cpu_topology(). So it won't be empty here.
Besides we don't need to check topology_is_primary_thread() at boot time:
-> cpu_up(cpu)
cpu_bootable()
if (cpu_smt_control == CPU_SMT_ENABLED &&
cpu_smt_thread_allowed(cpu)) // will always return true if !CONFIG_SMT_NUM_THREADS_DYNAMIC
return true; // we'll always return here and @cpu is always bootable
Also tested fine in practice.
Thanks.
From: Thomas Gleixner <hidden> Date: 2024-10-31 13:33:25
On Thu, Oct 31 2024 at 20:17, Yicong Yang wrote:
On 2024/10/30 22:55, Thomas Gleixner wrote:
quoted
quoted
+static inline bool topology_is_primary_thread(unsigned int cpu)
+{
+ /*
+ * On SMT hotplug the primary thread of the SMT won't be disabled.
+ * Architectures do have a special primary thread (e.g. x86) need
+ * to override this function. Otherwise just make the first thread
+ * in the SMT as the primary thread.
+ */
+ return cpu == cpumask_first(topology_sibling_cpumask(cpu));
How is that supposed to work? Assume both siblings are offline, then the
sibling mask is empty and you can't boot the CPU anymore.
For architectures' using arch_topology, topology_sibling_cpumask() will at least
contain the tested CPU itself. This is initialized in
drivers/base/arch_topology.c:reset_cpu_topology(). So it won't be
empty here.
Fair enough. Can you please expand the comment and say:
The sibling cpumask of a offline CPU contains always the CPU
itself.
Besides we don't need to check topology_is_primary_thread() at boot time:
-> cpu_up(cpu)
cpu_bootable()
if (cpu_smt_control == CPU_SMT_ENABLED &&
cpu_smt_thread_allowed(cpu)) // will always return true if !CONFIG_SMT_NUM_THREADS_DYNAMIC
return true; // we'll always return here and @cpu is always bootable
cpu_smt_control is not guaranteed to have CPU_SMT_ENABLED state, so this
argument is bogus.
Also tested fine in practice.
I've heard that song before.
What matters is not what you tested. What matters is whether the code is
correct _and_ understandable.
Thanks,
tglx
From: Yicong Yang <hidden> Date: 2024-11-01 03:18:45
On 2024/10/31 21:33, Thomas Gleixner wrote:
On Thu, Oct 31 2024 at 20:17, Yicong Yang wrote:
quoted
On 2024/10/30 22:55, Thomas Gleixner wrote:
quoted
quoted
+static inline bool topology_is_primary_thread(unsigned int cpu)
+{
+ /*
+ * On SMT hotplug the primary thread of the SMT won't be disabled.
+ * Architectures do have a special primary thread (e.g. x86) need
+ * to override this function. Otherwise just make the first thread
+ * in the SMT as the primary thread.
+ */
+ return cpu == cpumask_first(topology_sibling_cpumask(cpu));
How is that supposed to work? Assume both siblings are offline, then the
sibling mask is empty and you can't boot the CPU anymore.
For architectures' using arch_topology, topology_sibling_cpumask() will at least
contain the tested CPU itself. This is initialized in
drivers/base/arch_topology.c:reset_cpu_topology(). So it won't be
empty here.
Fair enough. Can you please expand the comment and say:
The sibling cpumask of a offline CPU contains always the CPU
itself.
Sure, will make it clear.
quoted
Besides we don't need to check topology_is_primary_thread() at boot time:
-> cpu_up(cpu)
cpu_bootable()
if (cpu_smt_control == CPU_SMT_ENABLED &&
cpu_smt_thread_allowed(cpu)) // will always return true if !CONFIG_SMT_NUM_THREADS_DYNAMIC
return true; // we'll always return here and @cpu is always bootable
cpu_smt_control is not guaranteed to have CPU_SMT_ENABLED state, so this
argument is bogus.
sorry for didn't explain all the cases here.
For cpu_sm_control == {CPU_SMT_ENABLED, CPU_SMT_NOT_SUPPORTED, CPU_SMT_NOT_IMPLEMENTED},
all the cpu's bootable and we won't check topology_is_primary_thread().
static inline bool cpu_bootable(unsigned int cpu)
{
if (cpu_smt_control == CPU_SMT_ENABLED && cpu_smt_thread_allowed(cpu))
return true;
/* All CPUs are bootable if controls are not configured */
if (cpu_smt_control == CPU_SMT_NOT_IMPLEMENTED)
return true;
/* All CPUs are bootable if CPU is not SMT capable */
if (cpu_smt_control == CPU_SMT_NOT_SUPPORTED)
return true;
if (topology_is_primary_thread(cpu)) // Will be true for all the CPUs when thread sibling's not built
// Only true for primary thread if thread sibling's updated
// thread sibling will be updated once the CPU's bootup, for arm64
// in secondary_start_kernel()
return true;
return !cpumask_test_cpu(cpu, &cpus_booted_once_mask); // Also be updated once the CPU's bootup, in
// secondary_start_kernel() for arm64
// Will return false in the second check of
// cpu_bootable() in the call chain below
}
For cpu_smt_control == {CPUS_SMT_DISABLED, CPU_SMT_FORCE_DISABLED} if user specified the
boot option "nosmt" or "nosmt=force", it'll be a bit more complex. For a non-primary
thread CPU, cpu_bootable() will return true and it'll be boot. Then after thread sibling's
built cpu_bootable() will be checked secondly it the cpuhp callbacks, since it'll return
false then and we'll roll back and offline it.
// for a non-primary thread CPU, system boot with "nosmt" or "nosmt=force"
-> cpu_up()
cpu_bootable() -> true, since the thread sibling mask only coutains CPU itself
[...]
cpuhp_bringup_ap()
bringup_wait_for_ap_online()
if (!cpu_bootable(cpu)) // target CPU has been bringup, thread sibling mask's updated
// then this non-primay thread won't be bootable in this case
return -ECANCELED // roll back and offline this CPU
Thanks.
From: Thomas Gleixner <hidden> Date: 2024-11-01 09:31:47
On Fri, Nov 01 2024 at 11:18, Yicong Yang wrote:
On 2024/10/31 21:33, Thomas Gleixner wrote:
quoted
cpu_smt_control is not guaranteed to have CPU_SMT_ENABLED state, so this
argument is bogus.
sorry for didn't explain all the cases here.
For cpu_sm_control == {CPU_SMT_ENABLED, CPU_SMT_NOT_SUPPORTED, CPU_SMT_NOT_IMPLEMENTED},
all the cpu's bootable and we won't check topology_is_primary_thread().
You don't have to copy the code to me. I'm familiar with it.
All I need is a proper explanation why your topology_is_primary_thread()
implementation is correct under all circumstances.
Thanks,
tglx
From: Pierre Gondois <pierre.gondois@arm.com> Date: 2024-11-07 17:20:30
On 10/30/24 13:54, Yicong Yang wrote:
quoted hunk
From: Yicong Yang <redacted>
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 <redacted>
---
arch/arm64/kernel/topology.c | 57 ++++++++++++++++++++++++++++++++++++
1 file changed, 57 insertions(+)
@@ -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;++/*+*InthePPTT,CPUsbelowanodewiththe'identical+*implementation'flaghavethesamenumberofthreads.+*CountthenumberofthreadsforonlyoneCPU(i.e.+*onecore_id)amongthosewiththesamehetero_id.+*Seethecommentoffind_acpi_cpu_topology_hetero_id()+*formoredetails.+*+*Oneentryiscreatedforeachnodehaving:+*-the'identicalimplementation'flag+*-itsparentnothavingtheflag+*/+hetero_id=find_acpi_cpu_topology_hetero_id(cpu);+entry=(structcpu_smt_info*)xa_load(&hetero_cpu,hetero_id);+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);+}elseif(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,24 @@ int __init parse_acpi_topology(void)cpu_topology[cpu].package_id=topology_id;}+/*+*Thisshouldbeashortloopdependingonthenumberofheterogeneous+*CPUclusters.Typicallyonahomogeneoussystemthere'sonlyone+*entryintheXArray.+*/+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;++xa_erase(&hetero_cpu,hetero_id);+kfree(entry);+}
I think you need to check that max_smt_thread_num !=0,
like in the DT path. Otherwise on a platform with no SMT,
max_smt_thread_num = 0 and I hit:
kernel/cpu::cpu_smt_set_num_threads()
WARN_ON(!num_threads || (num_threads > max_threads));
->
if (max_smt_thread_num)
cpu_smt_set_num_threads(max_smt_thread_num, max_smt_thread_num);
Please do not glue defines and functions together w/o a newline in between.
sure, will add a newline here.
quoted
quoted
+static inline bool topology_is_primary_thread(unsigned int cpu)
+{
+ /*
+ * On SMT hotplug the primary thread of the SMT won't be disabled.
+ * Architectures do have a special primary thread (e.g. x86) need
+ * to override this function. Otherwise just make the first thread
+ * in the SMT as the primary thread.
+ */
+ return cpu == cpumask_first(topology_sibling_cpumask(cpu));
How is that supposed to work? Assume both siblings are offline, then the
sibling mask is empty and you can't boot the CPU anymore.
For architectures' using arch_topology, topology_sibling_cpumask() will at least
contain the tested CPU itself. This is initialized in
drivers/base/arch_topology.c:reset_cpu_topology(). So it won't be empty here.
Besides we don't need to check topology_is_primary_thread() at boot time:
-> cpu_up(cpu)
cpu_bootable()
if (cpu_smt_control == CPU_SMT_ENABLED &&
cpu_smt_thread_allowed(cpu)) // will always return true if !CONFIG_SMT_NUM_THREADS_DYNAMIC
return true; // we'll always return here and @cpu is always bootable
Also tested fine in practice.
Thanks.
FWIW, I also tested the case where:
- setting maxcpus=1 in the kernel cmdline to have CPUs that never booted
- setting smt to off:
'echo off > /sys/devices/system/cpu/smt/control'
and effectively the primary CPUs can boot and secondary CPUs can't,
so it works as expected.
From: Yicong Yang <hidden> Date: 2024-11-08 08:06:54
On 2024/11/8 1:20, Pierre Gondois wrote:
On 10/30/24 13:54, Yicong Yang wrote:
quoted
From: Yicong Yang <redacted>
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 <redacted>
---
arch/arm64/kernel/topology.c | 57 ++++++++++++++++++++++++++++++++++++
1 file changed, 57 insertions(+)
[...]
quoted
@@ -67,6 +106,24 @@ 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;
+
+ xa_erase(&hetero_cpu, hetero_id);
+ kfree(entry);
+ }
I think you need to check that max_smt_thread_num !=0,
like in the DT path. Otherwise on a platform with no SMT,
max_smt_thread_num = 0 and I hit:
kernel/cpu::cpu_smt_set_num_threads()
WARN_ON(!num_threads || (num_threads > max_threads));
->
if (max_smt_thread_num)
cpu_smt_set_num_threads(max_smt_thread_num, max_smt_thread_num);
sorry for this silly mistake. yes we should do the same like in the DT path.
I'll get this fixed. thanks for testing.