Skip to content

locktorture and memory-barriers.txt updates

Paul E. McKenney lkml 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4documentation: Add disclaimerDocumentation/memory-barriers.txt+17 -10 replies
2/4documentation: State purpose of memory-barriers.txtDocumentation/memory-barriers.txt+16 -00 replies
3/4documentation: ACQUIRE applies to loads, RELEASE applies to storesDocumentation/memory-barriers.txt+5 -00 replies
4/4locktorture: Simplify torture_runnable computationkernel/locking/locktorture.c+1 -60 replies

Reviews trailers per patch

1 of 4 patches has a Reviewed-by or Acked-by.

PatchPeter Zijlstra (Intel)
1/4
2/4
3/4A-b
4/4

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

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

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(-)