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@efficios.com,
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
Subject: [PATCH tip/core/rcu 0/2] v2 Tiny RCU changes for 3.9
Date: Sat, 26 Jan 2013 16:23:28 -0800 [thread overview]
Message-ID: <20130127002328.GA4847@linux.vnet.ibm.com> (raw)
Hello!
This series provides a couple of tiny-RCU changes:
1. Make Tiny RCU emit RCU CPU stall warnings when RCU_TRACE=y.
2. Allow TREE_PREEMPT_RCU to be used on UP systems.
Changes since v1:
o Updated #1 as suggested by Josh Triplett to simplify the
#if expressions.
o Added #2.
Thanx, Paul
b/init/Kconfig | 12 +++++++++
b/kernel/rcu.h | 7 +++++
b/kernel/rcupdate.c | 51 +++++++++++++++++++++++++++++++++++++++++
b/kernel/rcutiny.c | 6 +++-
b/kernel/rcutiny_plugin.h | 56 ++++++++++++++++++++++++++++++++++++++++++++++
b/kernel/rcutree.c | 46 ++-----------------------------------
b/kernel/rcutree.h | 5 ----
b/lib/Kconfig.debug | 2 -
8 files changed, 133 insertions(+), 52 deletions(-)
next reply other threads:[~2013-01-27 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 0:23 Paul E. McKenney [this message]
2013-01-27 0:23 ` [PATCH tip/core/rcu 1/2] rcu: Provide RCU CPU stall warnings for tiny RCU Paul E. McKenney
2013-01-27 0:23 ` [PATCH tip/core/rcu 2/2] rcu: Allow TREE_PREEMPT_RCU on UP systems Paul E. McKenney
2013-01-27 10:58 ` Josh Triplett
2013-01-27 10:57 ` [PATCH tip/core/rcu 1/2] rcu: Provide RCU CPU stall warnings for tiny RCU Josh Triplett
2013-01-29 5:56 ` Paul E. McKenney
2013-01-27 10:58 ` [PATCH tip/core/rcu 0/2] v2 Tiny RCU changes for 3.9 Josh Triplett
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=20130127002328.GA4847@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@efficios.com \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).