From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
edumazet@google.com, darren@dvhart.com, fweisbec@gmail.com,
sbw@mit.edu,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [PATCH tip/core/rcu 3/7] rcu: Remove comment referring to __stop_machine()
Date: Mon, 18 Mar 2013 14:16:52 -0700 [thread overview]
Message-ID: <1363641416-18642-3-git-send-email-paulmck@linux.vnet.ibm.com> (raw)
In-Reply-To: <1363641416-18642-1-git-send-email-paulmck@linux.vnet.ibm.com>
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Although it used to be that CPU_DYING notifiers executed on the outgoing
CPU with interrupts disabled and with all other CPUs spinning, this is
no longer the case. This commit therefore removes this obsolete comment.
Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
kernel/rcutree.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/kernel/rcutree.c b/kernel/rcutree.c
index b2fc234..71df6f9 100644
--- a/kernel/rcutree.c
+++ b/kernel/rcutree.c
@@ -2931,11 +2931,6 @@ static int __cpuinit rcu_cpu_notify(struct notifier_block *self,
break;
case CPU_DYING:
case CPU_DYING_FROZEN:
- /*
- * The whole machine is "stopped" except this CPU, so we can
- * touch any data without introducing corruption. We send the
- * dying CPU's callbacks to an arbitrarily chosen online CPU.
- */
for_each_rcu_flavor(rsp)
rcu_cleanup_dying_cpu(rsp);
rcu_cleanup_after_idle(cpu);
--
1.8.1.5
next prev parent reply other threads:[~2013-03-18 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 21:16 [PATCH tip/core/rcu 0/7] Fixes for 3.9 Paul E. McKenney
2013-03-18 21:16 ` [PATCH tip/core/rcu 1/7] rcu: Fix spacing problem Paul E. McKenney
2013-03-18 21:16 ` [PATCH tip/core/rcu 2/7] rcu: Avoid invoking RCU core on offline CPUs Paul E. McKenney
2013-03-18 21:16 ` Paul E. McKenney [this message]
2013-03-18 21:16 ` [PATCH tip/core/rcu 4/7] rcu: Delete unused rcu_node "wakemask" field Paul E. McKenney
2013-03-18 21:16 ` [PATCH tip/core/rcu 5/7] rcu: Fix hlist_bl_set_first_rcu() annotation Paul E. McKenney
2013-03-18 21:16 ` [PATCH tip/core/rcu 6/7] rcu: Add softirq-stall indications to stall-warning messages Paul E. McKenney
2013-03-18 21:16 ` [PATCH tip/core/rcu 7/7] rcu: Tone down debugging during boot-up and shutdown 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=1363641416-18642-3-git-send-email-paulmck@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--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®