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@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,
	eric.dumazet@gmail.com, darren@dvhart.com, patches@linaro.org
Subject: [PATCH tip/core/rcu 0/6] Preview of fifth set of RCU changes for 3.3
Date: Mon, 12 Dec 2011 16:41:44 -0800	[thread overview]
Message-ID: <20111213004144.GA32120@linux.vnet.ibm.com> (raw)

Hello!

This patchset adds to the earlier sets:

	https://lkml.org/lkml/2011/11/2/363
	https://lkml.org/lkml/2011/11/15/302
	https://lkml.org/lkml/2011/11/28/588
	https://lkml.org/lkml/2011/12/3/77

This fifth set adds rcutorture tests for the recently added
srcu_read_lock_raw(), additional tracing to further evaluate
RCU_FAST_NO_HZ, addition of an export to assist with rcutorture testing,
bug fixes, and documentation.  The patches are as follows:

1.	Add rcutorture tests for srcu_read_lock_raw().
2.	Add tracing to further validate RCU_FAST_NO_HZ by giving more
	information on RCU's state at the time it decides to stop
	invoking callbacks.
3.	Add the 2010 RCU API LWN article to the RCU documentation
	(courtesy of Kees Cook).
4.	Revert patch that permitted rtmutex acquisition with interrupts
	disabled.  Per LKML discussions (https://lkml.org/lkml/2011/12/5/63),
	it was decided to illegalize IRQ-disable code sections that
	partially overlap with RCU read-side critical sections.  Code
	to enforce this illegalization is in progress.
5.	Add ACCESS_ONCE() to rcu_boost() return value.
6.	Export cpu_up() so that rcutorture can exercise CPU hotplug
	and RCU when rcutorture is built as a module.

For a testing-only version of this patchset from git, please see the
following subject-to-rebase branch, based on 3.2-rc5:

git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next

							Thanx, Paul

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

 b/Documentation/RCU/whatisRCU.txt |    1 +
 b/include/trace/events/rcu.h      |   38 +++++++++++++++++++++++++++++---------
 b/kernel/cpu.c                    |    1 +
 b/kernel/rcutiny.c                |   10 ++++++++--
 b/kernel/rcutiny_plugin.h         |   25 +++++++++++++++++++++++++
 b/kernel/rcutorture.c             |   26 +++++++++++++++++++++++++-
 b/kernel/rcutree.c                |    8 ++++++--
 b/kernel/rcutree_plugin.h         |    5 -----
 b/kernel/rtmutex.c                |    8 --------
 kernel/rcutiny_plugin.h           |    4 ++--
 kernel/rcutree_plugin.h           |    3 ++-
 11 files changed, 99 insertions(+), 30 deletions(-)


             reply	other threads:[~2011-12-13  0:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13  0:41 Paul E. McKenney [this message]
2011-12-13  0:42 ` [PATCH RFC tip/core/rcu 1/6] rcu: Add rcutorture tests for srcu_read_lock_raw() Paul E. McKenney
2011-12-13  0:42   ` [PATCH RFC tip/core/rcu 2/6] rcu: Augment rcu_batch_end tracing for idle and callback state Paul E. McKenney
2011-12-13  0:42   ` [PATCH RFC tip/core/rcu 3/6] docs: Additional LWN links to RCU API Paul E. McKenney
2011-12-13  0:42   ` [PATCH RFC tip/core/rcu 4/6] Revert "rcu: Permit rt_mutex_unlock() with irqs disabled" Paul E. McKenney
2011-12-13  0:42   ` [PATCH RFC tip/core/rcu 5/6] rcu: Apply ACCESS_ONCE() to rcu_boost() return value Paul E. McKenney
2011-12-13  0:42   ` [PATCH RFC tip/core/rcu 6/6] cpu: Export cpu_up() 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=20111213004144.GA32120@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=eric.dumazet@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=patches@linaro.org \
    --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