Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 3dbf0913 authored by SeongJae Park's avatar SeongJae Park Committed by Ingo Molnar
Browse files

locking/Documentation: Fix formatting inconsistencies 



Signed-off-by: default avatarSeongJae Park <sj38.park@gmail.com>
Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Acked-by: default avatarDavid Howells <dhowells@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: bobby.prani@gmail.com
Cc: dipankar@in.ibm.com
Cc: dvhart@linux.intel.com
Cc: edumazet@google.com
Cc: fweisbec@gmail.com
Cc: jiangshanlai@gmail.com
Cc: josh@joshtriplett.org
Cc: mathieu.desnoyers@efficios.com
Cc: oleg@redhat.com
Cc: rostedt@goodmis.org
Link: http://lkml.kernel.org/r/1460476375-27803-4-git-send-email-paulmck@linux.vnet.ibm.com


Signed-off-by: default avatarIngo Molnar <mingo@kernel.org>
parent 01e1cd6d

Documentation/memory-barriers.txt

+4 −4
Original line number Diff line number Diff line
@@ -149,7 +149,7 @@ As a further example, consider this sequence of events: 


	CPU 1		CPU 2

	===============	===============

	{ A == 1, B == 2, C = 3, P == &A, Q == &C }

	{ A == 1, B == 2, C == 3, P == &A, Q == &C }

	B = 4;		Q = P;

	P = &B		D = *Q;
@@ -518,7 +518,7 @@ following sequence of events: 


	CPU 1		      CPU 2

	===============	      ===============

	{ A == 1, B == 2, C = 3, P == &A, Q == &C }

	{ A == 1, B == 2, C == 3, P == &A, Q == &C }

	B = 4;

	<write barrier>

	WRITE_ONCE(P, &B)
@@ -545,7 +545,7 @@ between the address load and the data load: 


	CPU 1		      CPU 2

	===============	      ===============

	{ A == 1, B == 2, C = 3, P == &A, Q == &C }

	{ A == 1, B == 2, C == 3, P == &A, Q == &C }

	B = 4;

	<write barrier>

	WRITE_ONCE(P, &B);
@@ -3043,7 +3043,7 @@ The Alpha defines the Linux kernel's memory barrier model. 
See the subsection on "Cache Coherency" above.



VIRTUAL MACHINE GUESTS

-------------------

----------------------



Guests running within virtual machines might be affected by SMP effects even if

the guest itself is compiled without SMP support.  This is an artifact of