From: Andrea Parri <parri.andrea@gmail.com>
To: Hernan Ponce de Leon <hernan.poncedeleon@huaweicloud.com>
Cc: Boqun Feng <boqun.feng@gmail.com>,
stern@rowland.harvard.edu, will@kernel.org, peterz@infradead.org,
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,
jonas.oberhauser@huaweicloud.com
Subject: Re: [PATCH v3] tools/memory-model: Document herd7 (abstract) representation
Date: Tue, 18 Jun 2024 11:54:04 +0200 [thread overview]
Message-ID: <ZnFZPJlILp5B9scN@andrea> (raw)
In-Reply-To: <07513d65-386d-1bfb-f5ad-8979708d5523@huaweicloud.com>
> This follows from rmw \subset po. However, this might not be immediately
> clear for the reader so having it explicit is a good idea.
Sure. How about as follows:
diff --git a/tools/memory-model/Documentation/herd-representation.txt b/tools/memory-model/Documentation/herd-representation.txt
index 2fe270e902635..8255a2ff62e5f 100644
--- a/tools/memory-model/Documentation/herd-representation.txt
+++ b/tools/memory-model/Documentation/herd-representation.txt
@@ -14,7 +14,7 @@
# SRCU, a Sleepable-Read-Copy-Update event
#
# po, a Program-Order link
-# rmw, a Read-Modify-Write link
+# rmw, a Read-Modify-Write link; every rmw link is a po link
#
# By convention, a blank entry/representation means "same as the preceding entry".
#
I can respin the patch shortly to add something along these lines and
the collected tags.
Andrea
next prev parent reply other threads:[~2024-06-18 9:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 20:17 [PATCH v3] tools/memory-model: Document herd7 (abstract) representation Andrea Parri
2024-06-17 22:53 ` Boqun Feng
2024-06-18 3:27 ` Andrea Parri
2024-06-18 3:38 ` Boqun Feng
2024-06-18 9:19 ` Hernan Ponce de Leon
2024-06-18 9:54 ` Andrea Parri [this message]
2024-06-18 10:20 ` Hernan Ponce de Leon
2024-06-18 14:29 ` Paul E. McKenney
2024-06-18 18:41 ` Andrea Parri
2024-06-18 18:59 ` Paul E. McKenney
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=ZnFZPJlILp5B9scN@andrea \
--to=parri.andrea@gmail.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=hernan.poncedeleon@huaweicloud.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=jonas.oberhauser@huaweicloud.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@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