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
Subject: [PATCH tip/core/rcu 0/8] random RCU fixes and updates
Date: Wed, 22 Sep 2010 17:50:33 -0700 [thread overview]
Message-ID: <20100923005033.GA22006@linux.vnet.ibm.com> (raw)
Hello!
This patchset contains fixes for problems identified in -next testing
and some statistics and documentation updates. The patches are as follows:
1. Update stallwarn.txt to include stall warnings caused by
real-time processes (yes, even in mainline kernels).
2. Fix some performance bugs in TINY_PREEMPT_RCU.
3. Fix an overactive rcu_bootup_announce_oddness() warning.
4. Eliminate a redundant #ifdef (from Christian Dietrich).
5. Fix the new sparse-aware primitives to correctly handle
macro arguments with side effects.
6. Fix some issues sparse found in rcutorture.c.
7. Add some tracing data to help compute estimates of how long
RCU callbacks are queued.
8. Fix up the Kconfig message for PROVE_RCU_REPEATEDLY.
For a testing-only version of this patchset from git, please see:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/testing
Thanx, Paul
Documentation/RCU/stallwarn.txt | 18 ++++++++++++++++++
Documentation/RCU/trace.txt | 13 ++++++++++++-
include/linux/rcupdate.h | 14 +++++++++++---
kernel/rcutiny_plugin.h | 12 ++++++++----
kernel/rcutorture.c | 8 +++++---
kernel/rcutree.c | 3 +++
kernel/rcutree.h | 3 +++
kernel/rcutree_plugin.h | 2 +-
kernel/rcutree_trace.c | 10 +++++++---
kernel/srcu.c | 2 --
lib/Kconfig.debug | 4 ++++
11 files changed, 72 insertions(+), 17 deletions(-)
next reply other threads:[~2010-09-23 0:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 0:50 Paul E. McKenney [this message]
2010-09-23 0:50 ` [PATCH tip/core/rcu 1/8] rcu: upgrade stallwarn.txt documentation for CPU-bound RT processes Paul E. McKenney
2010-09-23 0:50 ` [PATCH tip/core/rcu 2/8] rcu: performance fixes to TINY_PREEMPT_RCU callback checking Paul E. McKenney
2010-09-23 0:50 ` [PATCH tip/core/rcu 3/8] rcu: fix _oddness handling of verbose stall warnings Paul E. McKenney
2010-09-23 0:50 ` [PATCH tip/core/rcu 4/8] kernel: Removing undead ifdef CONFIG_DEBUG_LOCK_ALLOC Paul E. McKenney
2010-09-23 0:50 ` [PATCH tip/core/rcu 5/8] rcu: only one evaluation of arg in rcu_dereference_check() unless sparse Paul E. McKenney
2010-09-23 13:13 ` Arnd Bergmann
2010-09-23 17:23 ` Paul E. McKenney
2010-09-23 0:50 ` [PATCH tip/core/rcu 6/8] rcu: fix sparse errors in rcutorture.c Paul E. McKenney
2010-09-23 0:50 ` [PATCH tip/core/rcu 7/8] rcu: Add tracing data to support queueing models Paul E. McKenney
2010-09-23 0:50 ` [PATCH tip/core/rcu 8/8] rcu: Add advice to PROVE_RCU_REPEATEDLY kernel config parameter 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=20100923005033.GA22006@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--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=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