From: Thomas Gleixner <tglx@linutronix.de>
To: Koichiro Den <koichiro.den@canonical.com>, linux-kernel@vger.kernel.org
Cc: peterz@infradead.org
Subject: Re: [PATCH] cpu/hotplug: disallow writing any state in atomic AP section to sysfs target
Date: Thu, 16 Jan 2025 14:21:14 +0100 [thread overview]
Message-ID: <87zfjqao8l.ffs@tglx> (raw)
In-Reply-To: <20241220141538.4018232-1-koichiro.den@canonical.com>
On Fri, Dec 20 2024 at 23:15, Koichiro Den wrote:
> diff --git a/kernel/cpu.c b/kernel/cpu.c
> index 34f1a09349fc..c877443f5888 100644
> --- a/kernel/cpu.c
> +++ b/kernel/cpu.c
> @@ -2127,6 +2127,7 @@ static struct cpuhp_step cpuhp_hp_states[] = {
> [CPUHP_BP_KICK_AP] = {
> .name = "cpu:kick_ap",
> .startup.single = cpuhp_kick_ap_alive,
> + .cant_stop = true,
Why? If it stops here, then no harm is done. The AP just waits for being
released. It won't change the state as that's a seperate handshake
mechanism.
> },
>
> /*
> @@ -2192,6 +2193,7 @@ static struct cpuhp_step cpuhp_hp_states[] = {
> * state for synchronsization */
> [CPUHP_AP_ONLINE] = {
> .name = "ap:online",
> + .cant_stop = true,
Your change log is pretty unclear about the reason for this change.
Thanks,
tglx
next prev parent reply other threads:[~2025-01-16 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 14:15 [PATCH] cpu/hotplug: disallow writing any state in atomic AP section to sysfs target Koichiro Den
2025-01-16 13:21 ` Thomas Gleixner [this message]
2025-01-18 7:40 ` Koichiro Den
2025-01-24 15:33 ` Vishal Chourasia
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=87zfjqao8l.ffs@tglx \
--to=tglx@linutronix.de \
--cc=koichiro.den@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.