public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
	bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/7] Post RCU callbacks at early boot
Date: Wed, 21 Jan 2015 02:07:50 -0800	[thread overview]
Message-ID: <20150121100750.GA22883@linux.vnet.ibm.com> (raw)

Hello!  

This series, probably for v3.21, contains changes that allow RCU callbacks
to be posted at very early boot, as in before rcu_init() is called.
This was requested by the tracing folks.  This series applies against
tip/core/rcu, and probably not against current mainline.

The patches in this series are as follows:

1.	Abstract initialization of callback lists.

2.	Wire up the rcu_state structures' ->rda pointers at compile time.

3.	Prevent early boot callbacks from splatting.

4.	Refine diagnostics for lacking an rcuo kthread for no-CBs
	CPUs that have callbacks posted.

5.	Avoid clobbering lists of early boot callbacks.

6.	Move early boot callbacks as needed by no-CBs CPUs.

7.	Move early boot callbacks tests to beginning of rcu_init().

This passes modest rcutorture testing, but is probably missing a corner
case or two.

							Thanx, Paul

------------------------------------------------------------------------

 b/kernel/rcu/tree.c        |   52 ++++++++++++++++++++++++++++++++-------------
 b/kernel/rcu/tree_plugin.h |   27 ++++++++++++-----------
 2 files changed, 51 insertions(+), 28 deletions(-)


             reply	other threads:[~2015-01-21 10:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 10:07 Paul E. McKenney [this message]
2015-01-21 10:08 ` [PATCH RFC tip/core/rcu 1/7] rcu: Abstract default callback-list initialization from init_callback_list() Paul E. McKenney
2015-01-21 10:08   ` [PATCH RFC tip/core/rcu 2/7] rcu: Wire ->rda pointers at compile time Paul E. McKenney
2015-01-21 10:08   ` [PATCH RFC tip/core/rcu 3/7] rcu: Prevent early-boot RCU callbacks from splatting Paul E. McKenney
2015-01-21 10:08   ` [PATCH RFC tip/core/rcu 4/7] rcu: Refine diagnostics for lacking kthread for no-CBs callbacks Paul E. McKenney
2015-01-21 10:08   ` [PATCH RFC tip/core/rcu 5/7] rcu: Avoid clobbering early boot callbacks Paul E. McKenney
2015-01-21 10:08   ` [PATCH RFC tip/core/rcu 6/7] rcu: Move early-boot callbacks to no-CBs lists for no-CBs CPUs Paul E. McKenney
2015-01-21 10:08   ` [PATCH RFC tip/core/rcu 7/7] rcu: Move early boot callback tests earlier 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=20150121100750.GA22883@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bobby.prani@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhart@linux.intel.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@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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