From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, 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, dhowells@redhat.com,
edumazet@google.com, darren@dvhart.com, fweisbec@gmail.com,
sbw@mit.edu
Subject: [PATCH v4 tip/core/locking 0/4] Memory-barrier documentation updates
Date: Wed, 4 Dec 2013 14:46:28 -0800 [thread overview]
Message-ID: <20131204224628.GA30159@linux.vnet.ibm.com> (raw)
Hello!
This series applies some long-needed updates to memory-barriers.txt:
1. Add ACCESS_ONCE() calls where needed to ensure their inclusion
in code copy-and-pasted from this file.
2. Add long atomic examples alongside the existing atomics.
3. Prohibit architectures supporting the Linux kernel from
speculating stores.
4. Document what ACCESS_ONCE() does along with a number of situations
requiring its use.
Changes from v3:
o Fix typos noted by Peter Zijlstra.
o Added the documentation about ACCESS_ONCE(), which expands on
http://thread.gmane.org/gmane.linux.kernel.mm/82891/focus=14696,
ably summarized by Jon Corbet at http://lwn.net/Articles/508991/.
Changes from v2:
o Update examples so that that load against which the subsequent
store is to be ordered is part of the "if" condition.
o Add an example showing how the compiler can remove "if"
conditions and how to prevent it from doing so.
o Add ACCESS_ONCE() to the compiler-barrier section.
o Add a sentence noting that transitivity requires smp_mb().
Changes from v1:
o Combined with Peter Zijlstra's speculative-store-prohibition patch.
o Added more pitfalls to avoid when prohibiting speculative
stores, along with how to avoid them.
o Applied Josh Triplett's review comments.
Thanx, Paul
b/Documentation/memory-barriers.txt | 666 ++++++++++++++++++++++++++++--------
1 file changed, 533 insertions(+), 133 deletions(-)
next reply other threads:[~2013-12-04 22:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 22:46 Paul E. McKenney [this message]
2013-12-04 22:46 ` [PATCH tip/core/locking 1/4] Documentation/memory-barriers.txt: Add needed ACCESS_ONCE() calls to memory-barriers.txt Paul E. McKenney
2013-12-04 22:46 ` [PATCH tip/core/locking 2/4] Documentation/memory-barriers.txt: Add long atomic examples " Paul E. McKenney
2013-12-04 22:46 ` [PATCH tip/core/locking 4/4] Documentation/memory-barriers.txt: Document ACCESS_ONCE() Paul E. McKenney
2013-12-05 9:33 ` Ingo Molnar
2013-12-05 9:52 ` Mathieu Desnoyers
2013-12-05 10:11 ` Ingo Molnar
2013-12-05 18:02 ` Paul E. McKenney
2013-12-10 13:24 ` Ingo Molnar
2013-12-10 17:36 ` Paul E. McKenney
2013-12-05 9:50 ` Ingo Molnar
2013-12-05 18:05 ` Paul E. McKenney
2013-12-05 22:47 ` Paul E. McKenney
2013-12-10 15:10 ` Ingo Molnar
2013-12-10 17:37 ` Paul E. McKenney
2013-12-05 20:21 ` Jonathan Corbet
2013-12-05 21:44 ` Paul E. McKenney
2013-12-10 15:20 ` Ingo Molnar
2013-12-10 17:44 ` Paul E. McKenney
2013-12-10 18:28 ` Ingo Molnar
2013-12-10 19:01 ` Paul E. McKenney
2013-12-10 19:46 ` Ingo Molnar
2013-12-10 20:09 ` Paul E. McKenney
2013-12-05 0:10 ` [PATCH v4 tip/core/locking 0/4] Memory-barrier documentation updates Josh Triplett
2013-12-05 10:59 ` Henrik Austad
2013-12-05 12:28 ` Ingo Molnar
2013-12-05 13:51 ` Steven Rostedt
2013-12-05 18:05 ` David Miller
2013-12-05 18:18 ` Paul E. McKenney
2013-12-05 18:44 ` David Miller
2013-12-05 19:01 ` Paul E. McKenney
2013-12-10 15:24 ` Ingo Molnar
2013-12-05 12:29 ` [PATCH v4 tip/core/locking 3/4] Documentation/memory-barriers.txt: Prohibit speculative writes Ingo Molnar
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=20131204224628.GA30159@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--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@kernel.org \
--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
Powered by JetHome