From: Srikar Dronamraju <srikar@linux.ibm.com>
To: "Nysal Jan K.A." <nysal@linux.ibm.com>
Cc: Sourabh Jain <sourabhjain@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Sachin P Bappalige <sachinpb@linux.ibm.com>,
stable@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Laurent Dufour <ldufour@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/kexec: Enable SMT before waking offline CPUs
Date: Tue, 28 Oct 2025 09:38:38 +0530 [thread overview]
Message-ID: <aQBBxlZebkLDhi2e@linux.ibm.com> (raw)
In-Reply-To: <20251025080512.85690-1-nysal@linux.ibm.com>
* Nysal Jan K.A. <nysal@linux.ibm.com> [2025-10-25 13:35:09]:
> diff --git a/arch/powerpc/kexec/core_64.c b/arch/powerpc/kexec/core_64.c
> index 222aa326dace..ff6df43720c4 100644
> --- a/arch/powerpc/kexec/core_64.c
> +++ b/arch/powerpc/kexec/core_64.c
> @@ -216,6 +216,11 @@ static void wake_offline_cpus(void)
> {
> int cpu = 0;
>
> + lock_device_hotplug();
> + cpu_smt_num_threads = threads_per_core;
> + cpu_smt_control = CPU_SMT_ENABLED;
> + unlock_device_hotplug();
> +
Nit: can we add a comment mentioning why we do it and probably move to a
small helper function of its own.
Otherwise looks good.
Reviewed-by: Srikar Dronamraju <srikar@linux.ibm.com>
> for_each_present_cpu(cpu) {
> if (!cpu_online(cpu)) {
> printk(KERN_INFO "kexec: Waking offline cpu %d.\n",
--
Thanks and Regards
Srikar Dronamraju
next prev parent reply other threads:[~2025-10-28 4:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 8:05 [PATCH] powerpc/kexec: Enable SMT before waking offline CPUs Nysal Jan K.A.
2025-10-28 0:51 ` kernel test robot
2025-10-28 4:08 ` Srikar Dronamraju [this message]
2025-10-28 4:44 ` Sourabh Jain
2025-10-28 10:55 ` [PATCH v2] " Nysal Jan K.A.
2025-10-28 17:26 ` Shrikanth Hegde
2025-10-29 3:36 ` Nysal Jan K.A.
2025-12-19 9:58 ` Sourabh Jain
2025-12-27 4:24 ` Madhavan Srinivasan
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=aQBBxlZebkLDhi2e@linux.ibm.com \
--to=srikar@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=ldufour@linux.ibm.com \
--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=nysal@linux.ibm.com \
--cc=sachinpb@linux.ibm.com \
--cc=sourabhjain@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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