mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srikar Dronamraju <srikar@linux.ibm.com>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Cc: Srikar Dronamraju <srikar@linux.ibm.com>,
	Samir Mulani <samir@linux.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] pseries/hotplug: Add CPU-to-node mappings for all present CPUs
Date: Mon, 12 Oct 2026 21:25:49 +0530	[thread overview]
Message-ID: <20261012155549.557256-2-srikar@linux.ibm.com> (raw)

When cores are added while the system is running in a lower SMT mode,
some threads of those cores remain offline. Moving the system to a
higher SMT mode later fails to online those threads.

For example, on a system with four cores:

  1. ppc64_cpu --smt=off
  2. nproc
       expected: 4
  3. ppc64_cpu --smt
       expected/actual: "SMT is off"
  4. drmgr -c cpu -a -q 4
  5. ppc64_cpu --smt
       expected/actual: "SMT is off"
  6. ppc64_cpu --smt=8
  7. ppc64_cpu --smt
       expected: SMT=8
       actual:   SMT=1: 4-7; SMT=8: 0-3
  8. nproc
       expected: 64
       actual:   36

Post commit d1099e2276df ("powerpc/pseries: Honour current SMT state
when DLPAR onlining CPUs"), when new CPUs are added, the CPU-to-node
mapping is currently updated only for CPUs that are immediately onlined.
CPUs that are made present but remain offline due to the current SMT
mode therefore do not get a CPU-to-node mapping.

When those CPUs are subsequently onlined after switching to a higher
SMT mode, the online operation fails because the required CPU-to-node
mapping is missing.

Update the CPU-to-node mapping before applying the SMT restrictions so
that all newly present CPUs have a node mapping, including CPUs that
remain offline in the current SMT mode.

Fixes: d1099e2276df ("powerpc/pseries: Honour current SMT state when DLPAR onlining CPUs")
Reported-by: Samir Mulani <samir@linux.ibm.com>
Signed-off-by: Srikar Dronamraju <srikar@linux.ibm.com>
---
 arch/powerpc/platforms/pseries/hotplug-cpu.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/powerpc/platforms/pseries/hotplug-cpu.c b/arch/powerpc/platforms/pseries/hotplug-cpu.c
index bc6926dbf148..b5dc942eec63 100644
--- a/arch/powerpc/platforms/pseries/hotplug-cpu.c
+++ b/arch/powerpc/platforms/pseries/hotplug-cpu.c
@@ -402,6 +402,7 @@ static int dlpar_online_cpu(struct device_node *dn)
 			if (get_hard_smp_processor_id(cpu) != thread)
 				continue;
 
+			find_and_update_cpu_nid(cpu);
 			if (!topology_is_primary_thread(cpu)) {
 				if (cpu_smt_control != CPU_SMT_ENABLED)
 					break;
@@ -410,7 +411,6 @@ static int dlpar_online_cpu(struct device_node *dn)
 			}
 
 			cpu_maps_update_done();
-			find_and_update_cpu_nid(cpu);
 			rc = device_online(get_cpu_device(cpu));
 			if (rc) {
 				dlpar_offline_cpu(dn);
-- 
2.43.7


                 reply	other threads:[~2026-10-12 15:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261012155549.557256-2-srikar@linux.ibm.com \
    --to=srikar@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=samir@linux.ibm.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®