From: egyszeregy@freemail.hu
To: stern@rowland.harvard.edu, parri.andrea@gmail.com,
will@kernel.org, peterz@infradead.org, boqun.feng@gmail.com,
npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
luc.maranget@inria.fr, paulmck@kernel.org, akiyks@gmail.com,
dlustig@nvidia.com, joel@joelfernandes.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
lkmm@lists.linux.dev
Cc: "Benjamin Szőke" <egyszeregy@freemail.hu>
Subject: [PATCH] tools/memory-model: Fix litmus-tests's file names.
Date: Mon, 9 Dec 2024 16:00:44 +0100 [thread overview]
Message-ID: <20241209150044.766-1-egyszeregy@freemail.hu> (raw)
From: Benjamin Szőke <egyszeregy@freemail.hu>
Makes a greater Hamming distance for name of Z6.0+pooncelock* files.
Signed-off-by: Benjamin Szőke <egyszeregy@freemail.hu>
---
tools/memory-model/Documentation/locking.txt | 4 ++--
tools/memory-model/Documentation/recipes.txt | 4 ++--
tools/memory-model/litmus-tests/README | 4 ++--
...ncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus} | 0
...s => Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus} | 0
5 files changed, 6 insertions(+), 6 deletions(-)
rename tools/memory-model/litmus-tests/{Z6.0+pooncelock+poonceLock+pombonce.litmus => Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus} (100%)
rename tools/memory-model/litmus-tests/{Z6.0+pooncelock+pooncelock+pombonce.litmus => Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus} (100%)
diff --git a/tools/memory-model/Documentation/locking.txt b/tools/memory-model/Documentation/locking.txt
index 65c898c64a93..c213aa4a8668 100644
--- a/tools/memory-model/Documentation/locking.txt
+++ b/tools/memory-model/Documentation/locking.txt
@@ -151,7 +151,7 @@ Ordering Provided by a Lock to CPUs Not Holding That Lock
It is not necessarily the case that accesses ordered by locking will be
seen as ordered by CPUs not holding that lock. Consider this example:
- /* See Z6.0+pooncelock+pooncelock+pombonce.litmus. */
+ /* See Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus. */
void CPU0(void)
{
spin_lock(&mylock);
@@ -184,7 +184,7 @@ ordering properties.
Ordering can be extended to CPUs not holding the lock by careful use
of smp_mb__after_spinlock():
- /* See Z6.0+pooncelock+poonceLock+pombonce.litmus. */
+ /* See Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus. */
void CPU0(void)
{
spin_lock(&mylock);
diff --git a/tools/memory-model/Documentation/recipes.txt b/tools/memory-model/Documentation/recipes.txt
index 03f58b11c252..3c55146e8fe4 100644
--- a/tools/memory-model/Documentation/recipes.txt
+++ b/tools/memory-model/Documentation/recipes.txt
@@ -126,7 +126,7 @@ However, it is not necessarily the case that accesses ordered by
locking will be seen as ordered by CPUs not holding that lock.
Consider this example:
- /* See Z6.0+pooncelock+pooncelock+pombonce.litmus. */
+ /* See Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus. */
void CPU0(void)
{
spin_lock(&mylock);
@@ -159,7 +159,7 @@ lock's ordering properties.
Ordering can be extended to CPUs not holding the lock by careful use
of smp_mb__after_spinlock():
- /* See Z6.0+pooncelock+poonceLock+pombonce.litmus. */
+ /* See Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus. */
void CPU0(void)
{
spin_lock(&mylock);
diff --git a/tools/memory-model/litmus-tests/README b/tools/memory-model/litmus-tests/README
index d311a0ff1ae6..82e5b58b8ac6 100644
--- a/tools/memory-model/litmus-tests/README
+++ b/tools/memory-model/litmus-tests/README
@@ -144,12 +144,12 @@ WRC+pooncerelease+fencermbonceonce+Once.litmus
The second is forbidden because smp_store_release() is
A-cumulative in LKMM.
-Z6.0+pooncelock+pooncelock+pombonce.litmus
+Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus
Is the ordering provided by a spin_unlock() and a subsequent
spin_lock() sufficient to make ordering apparent to accesses
by a process not holding the lock?
-Z6.0+pooncelock+poonceLock+pombonce.litmus
+Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus
As above, but with smp_mb__after_spinlock() immediately
following the spin_lock().
diff --git a/tools/memory-model/litmus-tests/Z6.0+pooncelock+poonceLock+pombonce.litmus b/tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus
similarity index 100%
rename from tools/memory-model/litmus-tests/Z6.0+pooncelock+poonceLock+pombonce.litmus
rename to tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus
diff --git a/tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+pombonce.litmus b/tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus
similarity index 100%
rename from tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+pombonce.litmus
rename to tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus
--
2.43.5
reply other threads:[~2024-12-09 15:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241209150044.766-1-egyszeregy@freemail.hu \
--to=egyszeregy@freemail.hu \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkmm@lists.linux.dev \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).