From: "Paul E. McKenney" <paulmck@linux•vnet.ibm.com>
To: mingo@kernel•org
Cc: linux-arch@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
corbet@lwn•net, peterz@infradead•org, rusty@rustcorp•com.au,
oleg@redhat•com, josh@joshtriplett•org, dhowells@redhat•com,
paulus@samba•org, torvalds@linux-foundation•org
Subject: [GIT PULL locking/mb] Locking/memory-barrier commits
Date: Fri, 13 Dec 2013 23:48:46 -0800 [thread overview]
Message-ID: <20131214074846.GA23612@linux.vnet.ibm.com> (raw)
Hello, Ingo,
This pull request contains additions to the memory-barrier documentation,
along with a downgrading of UNLOCK+LOCK to no longer be a full memory
barrier, and finally an smp_mb__after_unlock_lock() that allows upgrading
a particular LOCK to pair with a preceding UNLOCK to form a full memory
barrier, and application of smp_mb__after_unlock_lock() to RCU.
The first four documentation commits are ready for 3.14:
b145f8acfd82 (Add needed ACCESS_ONCE() calls to memory-barriers.txt)
6be08d626389 (Add long atomic examples to memory-barriers.txt)
c89bb78cfbe1 (Prohibit speculative writes)
b2ba08be67fc (Document ACCESS_ONCE())
The remaining commits might or might not be, but are at a point where
getting them into -tip is appropriate given other changes in this area,
e.g., Peter's smp_load_acquire() and smp_store_release().
These changes are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git locking/mb
for you to fetch changes up to 9f9df17e265b2c5aea11a95e3e69269d005ac0ae:
powerpc: Full barrier for smp_mb__after_unlock_lock() (2013-12-13 09:05:13 -0800)
----------------------------------------------------------------
Paul E. McKenney (7):
Documentation/memory-barriers.txt: Add needed ACCESS_ONCE() calls to memory-barriers.txt
Documentation/memory-barriers.txt: Add long atomic examples to memory-barriers.txt
Documentation/memory-barriers.txt: Document ACCESS_ONCE()
locking: Add an smp_mb__after_unlock_lock() for UNLOCK+LOCK barrier
Documentation/memory-barriers.txt: Downgrade UNLOCK+LOCK
rcu: Apply smp_mb__after_unlock_lock() to preserve grace periods
powerpc: Full barrier for smp_mb__after_unlock_lock()
Peter Zijlstra (1):
Documentation/memory-barriers.txt: Prohibit speculative writes
Documentation/memory-barriers.txt | 733 ++++++++++++++++++++++++++++++------
arch/powerpc/include/asm/spinlock.h | 2 +
include/linux/spinlock.h | 10 +
kernel/rcu/tree.c | 18 +-
kernel/rcu/tree_plugin.h | 13 +
5 files changed, 661 insertions(+), 115 deletions(-)
reply other threads:[~2013-12-14 7:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131214074846.GA23612@linux.vnet.ibm.com \
--to=paulmck@linux$(echo .)vnet.ibm.com \
--cc=corbet@lwn$(echo .)net \
--cc=dhowells@redhat$(echo .)com \
--cc=josh@joshtriplett$(echo .)org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mingo@kernel$(echo .)org \
--cc=oleg@redhat$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=rusty@rustcorp$(echo .)com.au \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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