Hello!
This series provides LKMM updates:
1. locking/memory-barriers.txt: Improve documentation for writel()
example, courtesy of Parav Pandit.
2. memory-model: Add rmw-sequences to the LKMM, courtesy of Alan
Stern.
3. Documentation: Fixed a typo in atomic_t.txt, courtesy of
Kushagra Verma.
4. memory-model: Make plain accesses carry dependencies, courtesy
of Jonas Oberhauser.
Thanx, Paul
------------------------------------------------------------------------
b/Documentation/atomic_t.txt | 2 -
b/Documentation/memory-barriers.txt | 22 +++++++-------
b/tools/memory-model/Documentation/explanation.txt | 30 ++++++++++++++++++++
b/tools/memory-model/linux-kernel.bell | 6 ++++
b/tools/memory-model/linux-kernel.cat | 5 ++-
b/tools/memory-model/litmus-tests/dep+plain.litmus | 31 +++++++++++++++++++++
tools/memory-model/Documentation/explanation.txt | 9 +++++-
7 files changed, 90 insertions(+), 15 deletions(-)
From: Kushagra Verma <[email protected]>
Fixed a typo in the word 'architecture'.
Signed-off-by: Kushagra Verma <[email protected]>
Signed-off-by: Paul E. McKenney <[email protected]>
---
Documentation/atomic_t.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/atomic_t.txt b/Documentation/atomic_t.txt
index 0f1ffa03db09a..d7adc6d543db4 100644
--- a/Documentation/atomic_t.txt
+++ b/Documentation/atomic_t.txt
@@ -324,7 +324,7 @@ atomic operations.
Specifically 'simple' cmpxchg() loops are expected to not starve one another
indefinitely. However, this is not evident on LL/SC architectures, because
-while an LL/SC architecure 'can/should/must' provide forward progress
+while an LL/SC architecture 'can/should/must' provide forward progress
guarantees between competing LL/SC sections, such a guarantee does not
transfer to cmpxchg() implemented using LL/SC. Consider:
--
2.31.1.189.g2e36527f23