Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1387750

[PATCH locking 0/4] locktorture and memory-barriers.txt updates

From "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Newsgroups linux.kernel
Subject [PATCH locking 0/4] locktorture and memory-barriers.txt updates
Date 2016-04-26 19:30 +0200
Message-ID <rseY9-34w-3@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


Hello!

This series contains a few memory-barriers.txt updates and a locktorture
cleanup:

1.	Add a disclaimer to memory-barrier.txt, courtesy of
	Peter Zijlstra.

2.	Explicitly state the purpose of memory-barrier.txt, courtesy
	of David Howells.

3.	Explicitly state that ACQUIRE applies to loads and that
	RELEASE applies to stores, courtesy of Will Deacon.

4.	Simplify torture_runnable computation in locktorture, replacing
	a multiline #ifdef with an IS_ENABLED() that fits into an
	existing line.

							Thanx, Paul

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

 Documentation/memory-barriers.txt |   39 +++++++++++++++++++++++++++++++++++++-
 kernel/locking/locktorture.c      |    7 ------
 2 files changed, 39 insertions(+), 7 deletions(-)

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

[PATCH locking 0/4] locktorture and memory-barriers.txt updates "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-04-26 19:30 +0200
  [PATCH locking 3/4] documentation: ACQUIRE applies to loads, RELEASE applies to stores "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-04-26 19:30 +0200
    [tip:locking/core] locking/Documentation: Clarify that ACQUIRE  applies to loads, RELEASE applies to stores tip-bot for Will Deacon <tipbot@zytor.com> - 2016-04-28 12:30 +0200

csiph-web