[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131205001054.GB28492@jtriplet-mobl1>
Date: Wed, 4 Dec 2013 16:10:54 -0800
From: Josh Triplett <josh@...htriplett.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, mingo@...nel.org,
laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org,
rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
darren@...art.com, fweisbec@...il.com, sbw@....edu
Subject: Re: [PATCH v4 tip/core/locking 0/4] Memory-barrier documentation
updates
On Wed, Dec 04, 2013 at 02:46:28PM -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.
>
> 4. Document what ACCESS_ONCE() does along with a number of situations
> requiring its use.
For all four patches in v4:
Reviewed-by: Josh Triplett <josh@...htriplett.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists