From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
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: Re: [PATCH v3 tip/core/locking 0/3] Memory-barrier documentation updates
Date: Fri, 22 Nov 2013 20:00:05 -0800 [thread overview]
Message-ID: <20131123040005.GA2090@leaf> (raw)
In-Reply-To: <20131122192657.GA11924@linux.vnet.ibm.com>
On Fri, Nov 22, 2013 at 11:26:57AM -0800, Paul E. McKenney wrote:
> 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.
>
> 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.
For v3, all three patches:
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
prev parent reply other threads:[~2013-11-23 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 19:26 [PATCH v3 tip/core/locking 0/3] Memory-barrier documentation updates Paul E. McKenney
2013-11-22 19:27 ` [PATCH v3 RFC tip/core/locking 1/3] Documentation/memory-barriers.txt: Add needed ACCESS_ONCE() calls to memory-barriers.txt Paul E. McKenney
2013-11-22 19:27 ` [PATCH v3 RFC tip/core/locking 2/3] Documentation/memory-barriers.txt: Add long atomic examples " Paul E. McKenney
2013-11-23 4:00 ` Josh Triplett [this message]
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=20131123040005.GA2090@leaf \
--to=josh@joshtriplett.org \
--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=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=paulmck@linux.vnet.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