linux.git/Documentation/atomic_ops.txt, branch master

Documentation/atomic_ops.txt: convert to ReST markup

2016-12-01T00:40:52+00:00

... and move to core-api folder.

Signed-off-by: Silvio Fricke 
Signed-off-by: Jonathan Corbet

Documentation: atomic_ops: use {READ,WRITE}_ONCE()

2016-11-16T23:17:03+00:00

While the {READ,WRITE}_ONCE() macros should be used in preference to
ACCESS_ONCE(), the atomic documentation uses the latter exclusively.

To point people in the right direction, and as a step towards the
eventual removal of ACCESS_ONCE(), update the documentation to use the
{READ,WRITE}_ONCE() macros as appropriate.

Signed-off-by: Mark Rutland 
Cc: Boqun Feng 
Cc: Peter Zijlstra 
Cc: Will Deacon 
Acked-by: Paul E. McKenney 
Signed-off-by: Jonathan Corbet

docs: fix locations of several documents that got moved

2016-10-24T10:12:35+00:00

The previous patch renamed several files that are cross-referenced
along the Kernel documentation. Adjust the links to point to
the right places.

Signed-off-by: Mauro Carvalho Chehab

locking/atomics, cmpxchg: Privatize the inclusion of asm/cmpxchg.h

2015-09-13T08:35:46+00:00

After commit:

  654672d4ba1a ("locking/atomics: Add _{acquire|release|relaxed}() variants of some atomic operations")

Architectures may only provide {cmp,}xchg_relaxed definitions in
asm/cmpxchg.h. Other variants, such as {cmp,}xchg, may be built in
linux/atomic.h, which means simply including asm/cmpxchg.h may not get
the definitions of all the{cmp,}xchg variants.

Therefore, we should privatize the inclusions of asm/cmpxchg.h to
keep it only included in arch/* and replace the inclusions outside
with linux/atomic.h

Signed-off-by: Boqun Feng 
Signed-off-by: Peter Zijlstra (Intel) 
Acked-by: Greg Kroah-Hartman 
Acked-by: Will Deacon 
Cc: Andrew Morton 
Cc: Aybuke Ozdemir 
Cc: Chris Brannon 
Cc: Davidlohr Bueso 
Cc: Greg Kroah-Hartman 
Cc: Jonathan Corbet 
Cc: Kirk Reiser 
Cc: Kishon Vijay Abraham I 
Cc: Linus Torvalds 
Cc: Paul E. McKenney 
Cc: Peter Zijlstra 
Cc: Samuel Thibault 
Cc: Shradha Shah 
Cc: Thomas Gleixner 
Cc: William Hubbs 
Cc: devel@driverdev.osuosl.org
Cc: linux-net-drivers@solarflare.com
Cc: speakup@linux-speakup.org
Link: http://lkml.kernel.org/r/1440589966-26280-1-git-send-email-boqun.feng@gmail.com
Signed-off-by: Ingo Molnar

locking/Documentation: Clarify failed cmpxchg() memory ordering semantics

2015-08-03T08:57:09+00:00

A failed cmpxchg does not provide any memory ordering guarantees, a
property that is used to optimise the cmpxchg implementations on Alpha,
PowerPC and arm64.

This patch updates atomic_ops.txt and memory-barriers.txt to reflect
this.

Signed-off-by: Will Deacon 
Signed-off-by: Peter Zijlstra (Intel) 
Cc: Andrew Morton 
Cc: Davidlohr Bueso 
Cc: Douglas Hatch 
Cc: H. Peter Anvin 
Cc: Jonathan Corbet 
Cc: Linus Torvalds 
Cc: Paul E. McKenney 
Cc: Peter Zijlstra 
Cc: Scott J Norton 
Cc: Thomas Gleixner 
Cc: Waiman Long 
Link: http://lkml.kernel.org/r/20150716151006.GH26390@arm.com
Signed-off-by: Ingo Molnar

documentation: Clarify memory-barrier semantics of atomic operations

2015-02-26T19:57:31+00:00

All value-returning atomic read-modify-write operations must provide full
memory-barrier semantics on both sides of the operation.  This commit
clarifies the documentation to make it clear that these memory-barrier
semantics are provided by the operations themselves, not by their callers.

Reported-by: Peter Hurley 
Signed-off-by: Paul E. McKenney

documentation: Add atomic_long_t to atomic_ops.txt

2014-11-13T18:34:54+00:00

Signed-off-by: Paul E. McKenney 
Reviewed-by: Pranith Kumar

arch,doc: Convert smp_mb__*()

2014-04-18T12:20:48+00:00

Update the documentation to reflect the change of barrier primitives.

Signed-off-by: Peter Zijlstra 
Reviewed-by: Paul E. McKenney 
Acked-by: David Howells 
Link: http://lkml.kernel.org/n/tip-xslfehiga1twbk5uk94rij1e@git.kernel.org
Cc: Linus Torvalds 
Cc: Randy Dunlap 
Cc: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ingo Molnar

Documentation: Memory barrier semantics of atomic_xchg()

2013-01-08T22:14:55+00:00

Add atomic_xchg() to documentation for atomic operations and
memory barriers.

Signed-off-by: Richard Braun 
Signed-off-by: Paul E. McKenney 
Reviewed-by: Josh Triplett

doc: Add load/store guarantees to Documentation/atomic-ops.txt

2011-12-11T18:31:58+00:00

An IRC discussion uncovered many conflicting opinions on what types
of data may be atomically loaded and stored.  This commit therefore
calls this out the official set: pointers, longs, ints, and chars (but
not shorts).  This commit also gives some examples of compiler mischief
that can thwart atomicity.

Please note that this discussion is relevant to !SMP kernels if
CONFIG_PREEMPT=y: preemption can cause almost as much trouble as can SMP.

Signed-off-by: Paul E. McKenney 
Cc: Richard Henderson 
Cc: Ivan Kokshaysky 
Cc: Matt Turner 
Cc: Russell King 
Cc: Haavard Skinnemoen 
Cc: Hans-Christian Egtvedt 
Cc: Mike Frysinger 
Cc: Mikael Starvik 
Cc: Jesper Nilsson 
Cc: David Howells 
Cc: Yoshinori Sato 
Cc: Richard Kuo 
Cc: Jes Sorensen 
Cc: Hirokazu Takata 
Cc: Geert Uytterhoeven 
Cc: Michal Simek 
Cc: Ralf Baechle 
Cc: Koichi Yasutake 
Cc: Jonas Bonn 
Cc: Kyle McMartin 
Cc: Helge Deller 
Cc: "James E.J. Bottomley" 
Cc: Benjamin Herrenschmidt 
Cc: Paul Mackerras 
Cc: Martin Schwidefsky 
Cc: Heiko Carstens 
Cc: Chen Liqin 
Cc: Lennox Wu 
Cc: Paul Mundt 
Cc: "David S. Miller" 
Cc: Chris Metcalf 
Cc: Jeff Dike 
Cc: Richard Weinberger 
Cc: Guan Xuetao 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin" 
Cc: Chris Zankel