[PATCH] docs: litmus-tests: Clarify about the RCU pre-initialization test

From: Joel Fernandes (Google)
Date: Mon May 11 2020 - 22:06:46 EST


Since this test was moved to tools/memory-model/, make sure that it is
at least referenced from Documentation/litmus-tests/'s README.

Signed-off-by: Joel Fernandes (Google) <joel@xxxxxxxxxxxxxxxxx>
---
Documentation/litmus-tests/README | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Documentation/litmus-tests/README b/Documentation/litmus-tests/README
index ac0b270b456c1..53f09e74734a4 100644
--- a/Documentation/litmus-tests/README
+++ b/Documentation/litmus-tests/README
@@ -11,7 +11,6 @@ tools/memory-model/README.

atomic (/atomic derectory)
--------------------------
-
Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus
Test that an atomic RMW followed by a smp_mb__after_atomic() is
stronger than a normal acquire: both the read and write parts of
@@ -23,8 +22,11 @@ Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus

RCU (/rcu directory)
--------------------
-
RCU+sync+read.litmus
RCU+sync+free.litmus
Both the above litmus tests demonstrate the RCU grace period guarantee
that an RCU read-side critical section can never span a grace period.
+
+MP+onceassign+derefonce.litmus (moved to tools/memory-model/litmus-tests/)
+ Demonstrates that rcu_assign_pointer() and rcu_dereference() to
+ ensure that an RCU reader will not see pre-initialization garbage.
--
2.26.2.645.ge9eca65c58-goog