From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, randy.dunlap@oracle.com,
Valdis.Kletnieks@vt.edu, a.p.zijlstra@chello.nl
Subject: [GIT PULL rcu/next] fixes and breakup of memory-barrier-decrease patch
Date: Sat, 21 May 2011 07:06:13 -0700 [thread overview]
Message-ID: <20110521140613.GA13062@linux.vnet.ibm.com> (raw)
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(-)
next reply other threads:[~2011-05-21 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 14:06 Paul E. McKenney [this message]
2011-05-21 14:28 ` [GIT PULL rcu/next] fixes and breakup of memory-barrier-decrease patch Ingo Molnar
2011-05-21 19:08 ` Paul E. McKenney
2011-05-21 19:14 ` Ingo Molnar
2011-05-21 20:39 ` Paul E. McKenney
2011-05-22 9:04 ` Ingo Molnar
2011-05-22 16:17 ` 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=20110521140613.GA13062@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
/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