Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gavin Shan <gshan@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, sudeep.holla@arm.com,
	rafael@kernel.org, Jonathan.Cameron@huawei.com,
	drjones@redhat.com, zhenyzha@redhat.com, shan.gavin@gmail.com
Subject: [PATCH] arch_topology: Limit threads to one specific cluster
Date: Tue, 24 May 2022 16:12:12 +0800	[thread overview]
Message-ID: <20220524081212.1363105-1-gshan@redhat.com> (raw)

The sibling information for one particular CPU is updated after ACPI
PPTT table is parsed. struct cpu_topology::thread_sibling tracks the
the CPUs in same core. However, cluster isn't considered when it's
populated. In this case, multiple threads belonging to different
clusters can be put together through the sibling information. It
eventually leads to unexpected warning from sched subsystem.

For example, the following warning is observed in a VM where we have
2 sockets, 4 clusters, 8 cores and 16 threads and the CPU topology
is populated as below.

   CPU  Socket-ID  Cluster-ID  Core-ID  Thread-ID
   ----------------------------------------------
    0      0          0          0        0
    1      0          0          0        1
    2      0          0          1        0
    3      0          0          1        1
    4      0          1          0        0
    5      0          1          0        1
    6      0          1          1        0
    7      0          1          1        1
    8      1          0          0        0
    9      1          0          0        1
   10      1          0          1        0
   11      1          0          1        1
   12      1          1          0        0
   13      1          1          0        1
   14      1          1          1        0
   15      1          1          1        1

  [    0.592181] CPU: All CPU(s) started at EL1
  [    0.593766] alternatives: patching kernel code
  [    0.595890] BUG: arch topology borken
  [    0.597210]      the SMT domain not a subset of the CLS domain
  [    0.599286]      child=0-1,4-5    sd=0-3

  # cat /sys/devices/system/cpu/cpu0/topology/cluster_cpus_list
  0-3
  # cat /sys/devices/system/cpu/cpu0/topology/thread_siblings_list
  0-1,4-5

This fixes the issue by limiting threads to one specific cluster.
With this applied, the unexpected warning disappears in the VM.

  # cat /sys/devices/system/cpu/cpu0/topology/cluster_cpus_list
  0-3
  # cat /sys/devices/system/cpu/cpu0/topology/thread_siblings_list
  0-1

Signed-off-by: Gavin Shan <gshan@redhat.com>
---
 drivers/base/arch_topology.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
index f73b836047cf..25a63a89ae7d 100644
--- a/drivers/base/arch_topology.c
+++ b/drivers/base/arch_topology.c
@@ -710,7 +710,8 @@ void update_siblings_masks(unsigned int cpuid)
 		cpumask_set_cpu(cpuid, &cpu_topo->core_sibling);
 		cpumask_set_cpu(cpu, &cpuid_topo->core_sibling);
 
-		if (cpuid_topo->core_id != cpu_topo->core_id)
+		if (cpuid_topo->cluster_id != cpu_topo->cluster_id ||
+		    cpuid_topo->core_id != cpu_topo->core_id)
 			continue;
 
 		cpumask_set_cpu(cpuid, &cpu_topo->thread_sibling);
-- 
2.23.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-05-24  8:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  8:12 Gavin Shan [this message]
2022-05-24  8:51 ` [PATCH] arch_topology: Limit threads to one specific cluster Sudeep Holla
2022-05-24  9:05   ` Gavin Shan
2022-05-24 10:59     ` Sudeep Holla

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=20220524081212.1363105-1-gshan@redhat.com \
    --to=gshan@redhat.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=drjones@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=shan.gavin@gmail.com \
    --cc=sudeep.holla@arm.com \
    --cc=zhenyzha@redhat.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