From: Joel Fernandes <joelagnelf@nvidia.com>
To: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Cc: Joel Fernandes <joelagnelf@nvidia.com>,
Andrea Righi <arighi@nvidia.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
rcu@vger.kernel.org
Subject: [PATCH v2] smp: Document preemption and stop_machine() mutual exclusion
Date: Sat, 5 Jul 2025 13:23:27 -0400 [thread overview]
Message-ID: <20250705172328.4114289-1-joelagnelf@nvidia.com> (raw)
Recently while revising RCU's cpu online checks, there was some discussion
around how IPIs synchronize with hotplug.
Add comments explaining how preemption disable creates mutual exclusion with
CPU hotplug's stop_machine mechanism. The key insight is that stop_machine()
atomically updates CPU masks and flushes IPIs with interrupts disabled, and
cannot proceed while any CPU (including the IPI sender) has preemption
disabled.
Cc: Andrea Righi <arighi@nvidia.com>
Cc: Paul E. McKenney <paulmck@kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>
Cc: rcu@vger.kernel.org
Co-developed-by: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Joel Fernandes <joelagnelf@nvidia.com>
---
v1->v2: Reworded a bit more (minor nit).
kernel/cpu.c | 4 ++++
kernel/smp.c | 12 ++++++++++++
2 files changed, 16 insertions(+)
diff --git a/kernel/cpu.c b/kernel/cpu.c
index a59e009e0be4..a8ce1395dd2c 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -1310,6 +1310,10 @@ static int takedown_cpu(unsigned int cpu)
/*
* So now all preempt/rcu users must observe !cpu_active().
+ *
+ * stop_machine() waits for all CPUs to enable preemption. This lets
+ * take_cpu_down() atomically update CPU masks and flush last IPI
+ * before new IPIs can be attempted to be sent.
*/
err = stop_machine_cpuslocked(take_cpu_down, NULL, cpumask_of(cpu));
if (err) {
diff --git a/kernel/smp.c b/kernel/smp.c
index 974f3a3962e8..842691467f9e 100644
--- a/kernel/smp.c
+++ b/kernel/smp.c
@@ -93,6 +93,9 @@ int smpcfd_dying_cpu(unsigned int cpu)
* explicitly (without waiting for the IPIs to arrive), to
* ensure that the outgoing CPU doesn't go offline with work
* still pending.
+ *
+ * This runs in stop_machine's atomic context with interrupts disabled,
+ * thus CPU offlining and IPI flushing happen together atomically.
*/
__flush_smp_call_function_queue(false);
irq_work_run();
@@ -418,6 +421,10 @@ void __smp_call_single_queue(int cpu, struct llist_node *node)
*/
static int generic_exec_single(int cpu, call_single_data_t *csd)
{
+ /*
+ * Preemption must be disabled by caller to mutually exclude with
+ * stop_machine() atomically updating CPU masks and flushing IPIs.
+ */
if (cpu == smp_processor_id()) {
smp_call_func_t func = csd->func;
void *info = csd->info;
@@ -640,6 +647,11 @@ int smp_call_function_single(int cpu, smp_call_func_t func, void *info,
/*
* prevent preemption and reschedule on another processor,
* as well as CPU removal
+ *
+ * get_cpu() disables preemption, ensuring mutual exclusion with
+ * stop_machine() where CPU offlining and last IPI flushing happen
+ * atomically versus this code. This guarantees here that the cpu_online()
+ * check and IPI sending are safe without losing IPIs due to offlining.
*/
this_cpu = get_cpu();
--
2.43.0
next reply other threads:[~2025-07-05 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 17:23 Joel Fernandes [this message]
2025-07-06 17:01 ` Paul E. McKenney
2025-07-07 7:50 ` Peter Zijlstra
2025-07-07 14:19 ` Joel Fernandes
2025-07-08 7:21 ` Peter Zijlstra
2025-07-08 14:00 ` Joel Fernandes
2025-07-07 15:56 ` Paul E. McKenney
2025-07-08 7:23 ` Peter Zijlstra
2025-07-08 22:52 ` Paul E. McKenney
2025-07-14 17:20 ` Paul E. McKenney
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=20250705172328.4114289-1-joelagnelf@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=arighi@nvidia.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@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
all inboxes | Powered by JetHome®