[GIT PULL rcu/next] fixes and breakup of memory-barrier-decreasepatch
From: Paul E. McKenney
Date: Sat May 21 2011 - 10:06:30 EST
Hello, Ingo,
This pull requests covers some RCU bug fixes and one patch rework.
The first group breaks up the infamous now-reverted (but ultimately
vindicated) "Decrease memory-barrier usage based on semi-formal proof"
commit into five commits. These five commits immediately follow the
revert, and the diff across all six of these commits is empty, so that
the effect of the five commits is to revert the revert.
Another commit, "Avoid build error for third-party modules", fixes
a build error reported by Randy Dunlap.
Another pair of commits, "Add atomic_or()" and "Avoid acquiring rcu_node
locks in timer functions", fix a lockdep splat reported by Valdis Kletnieks.
Finally, "Remove waitqueue usage for cpu, node, and boost kthreads", from
Peter Zijlstra, simplifies the RCU kthread wakeup logic and that also fixes a
bug that resulted in a crash.
These changes are available in the -rcu git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/next
------------------>
Paul E. McKenney (8):
rcu: Add memory barriers
rcu: Remove old memory barriers from rcu_process_callbacks()
rcu: Don't do reschedule unless in irq
rcu: Make rcu_enter_nohz() pay attention to nesting
rcu: Decrease memory-barrier usage based on semi-formal proof
rcu: Avoid build error for third-party modules
atomic: Add atomic_or()
rcu: Avoid acquiring rcu_node locks in timer functions
Peter Zijlstra (1):
rcu: Remove waitqueue usage for cpu, node, and boost kthreads
Documentation/RCU/trace.txt | 17 ++---
include/linux/atomic.h | 13 ++++
include/linux/rcupdate.h | 5 +-
kernel/rcutree.c | 162 +++++++++++++++++--------------------------
kernel/rcutree.h | 30 ++++----
kernel/rcutree_plugin.h | 23 +-----
kernel/rcutree_trace.c | 12 ++--
7 files changed, 112 insertions(+), 150 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/