From: "Paul E. McKenney" <paulmck@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
lkmm@lists.linux.dev, kernel-team@meta.com, mingo@kernel.org,
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,
Jonas Oberhauser <jonas.oberhauser@huaweicloud.com>
Subject: Re: [PATCH memory-model 7/7] tools/memory-model: Distinguish between syntactic and semantic tags
Date: Tue, 25 Feb 2025 10:18:54 -0800 [thread overview]
Message-ID: <42d5f3b4-de3e-4110-8273-01b25b92a7c8@paulmck-laptop> (raw)
In-Reply-To: <ec893c4e-b4eb-4279-be66-1ca7e6bce7b1@gmail.com>
On Tue, Feb 25, 2025 at 01:28:08PM +0900, Akira Yokosawa wrote:
> On Thu, 20 Feb 2025 08:14:03 -0800, Paul E. McKenney wrote:
> > From: Jonas Oberhauser <jonas.oberhauser@huaweicloud.com>
> >
> > Not all annotated accesses provide the semantics their syntactic tags
> > would imply. For example, an 'acquire tag on a write does not imply that
> > the write is finally in the Acquire set and provides acquire ordering.
> >
> > To distinguish in those cases between the syntactic tags and actual
> > sets, we capitalize the former, so 'ACQUIRE tags may be present on both
> > reads and writes, but only reads will appear in the Acquire set.
> >
> > For tags where the two concepts are the same we do not use specific
> > capitalization to make this distinction.
> >
> > Reported-by: Boqun Feng <boqun.feng@gmail.com>
> > Signed-off-by: Jonas Oberhauser <jonas.oberhauser@huaweicloud.com>
> > Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
> > Tested-by: Boqun Feng <boqun.feng@gmail.com>
> > Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
>
> Tested-by: Akira Yokosawa <akiyks@gmail.com> # herdtools7.7.58
I applied your tag to this commit and the previous one, and also your
suggested Co-developed-by tags, thank you very much!
Thanx, Paul
> > ---
> > .../Documentation/herd-representation.txt | 44 ++--
> > tools/memory-model/linux-kernel.bell | 22 +-
> > tools/memory-model/linux-kernel.def | 198 +++++++++---------
> > 3 files changed, 132 insertions(+), 132 deletions(-)
>
prev parent reply other threads:[~2025-02-25 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 16:13 [PATCH memory-model 0/7] LKMM updates for v6.15 Paul E. McKenney
2025-02-20 16:13 ` [PATCH memory-model 1/7] tools/memory-model: Add atomic_and()/or()/xor() and add_negative Paul E. McKenney
2025-02-20 16:13 ` [PATCH memory-model 2/7] tools/memory-model: Add atomic_andnot() with its variants Paul E. McKenney
2025-02-20 16:13 ` [PATCH memory-model 3/7] tools/memory-model: Legitimize current use of tags in LKMM macros Paul E. McKenney
2025-02-20 16:14 ` [PATCH memory-model 4/7] tools/memory-model: Define applicable tags on operation in tools/ Paul E. McKenney
2025-02-20 16:14 ` [PATCH memory-model 5/7] tools/memory-model: Define effect of Mb tags on RMWs " Paul E. McKenney
2025-02-20 16:14 ` [PATCH memory-model 6/7] tools/memory-model: Switch to softcoded herd7 tags Paul E. McKenney
2025-02-25 4:24 ` Akira Yokosawa
2025-02-25 7:40 ` Hernan Ponce de Leon
2025-02-20 16:14 ` [PATCH memory-model 7/7] tools/memory-model: Distinguish between syntactic and semantic tags Paul E. McKenney
2025-02-25 4:28 ` Akira Yokosawa
2025-02-25 18:18 ` Paul E. McKenney [this message]
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=42d5f3b4-de3e-4110-8273-01b25b92a7c8@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=j.alglave@ucl.ac.uk \
--cc=jonas.oberhauser@huaweicloud.com \
--cc=kernel-team@meta.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkmm@lists.linux.dev \
--cc=luc.maranget@inria.fr \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--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).