From: "Paul E. McKenney" <paulmck@kernel.org>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
kernel-team@fb.com, mingo@kernel.org
Cc: 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, akiyks@gmail.com,
"Paul Heidekrüger" <paul.heidekrueger@in.tum.de>,
"Marco Elver" <elver@google.com>,
"Charalampos Mainas" <charalampos.mainas@gmail.com>,
"Pramod Bhatotia" <pramod.bhatotia@in.tum.de>,
"Soham Chakraborty" <s.s.chakraborty@tudelft.nl>,
"Martin Fink" <martin.fink@in.tum.de>,
"Paul E . McKenney" <paulmck@kernel.org>
Subject: [PATCH memory-model 1/5] tools/memory-model: Weaken ctrl dependency definition in explanation.txt
Date: Wed, 19 Oct 2022 16:06:47 -0700 [thread overview]
Message-ID: <20221019230651.2502538-1-paulmck@kernel.org> (raw)
In-Reply-To: <20221019230640.GA2502305@paulmck-ThinkPad-P17-Gen-1>
From: Paul Heidekrüger <paul.heidekrueger@in.tum.de>
The current informal control dependency definition in explanation.txt is
too broad and, as discussed, needs to be updated.
Consider the following example:
> if(READ_ONCE(x))
> return 42;
>
> WRITE_ONCE(y, 42);
>
> return 21;
The read event determines whether the write event will be executed "at all"
- as per the current definition - but the formal LKMM does not recognize
this as a control dependency.
Introduce a new definition which includes the requirement for the second
memory access event to syntactically lie within the arm of a non-loop
conditional.
Link: https://lore.kernel.org/all/20220615114330.2573952-1-paul.heidekrueger@in.tum.de/
Cc: Marco Elver <elver@google.com>
Cc: Charalampos Mainas <charalampos.mainas@gmail.com>
Cc: Pramod Bhatotia <pramod.bhatotia@in.tum.de>
Cc: Soham Chakraborty <s.s.chakraborty@tudelft.nl>
Cc: Martin Fink <martin.fink@in.tum.de>
Co-developed-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Paul Heidekrüger <paul.heidekrueger@in.tum.de>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
---
tools/memory-model/Documentation/explanation.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/tools/memory-model/Documentation/explanation.txt b/tools/memory-model/Documentation/explanation.txt
index ee819a402b698..11a1d2d4f681c 100644
--- a/tools/memory-model/Documentation/explanation.txt
+++ b/tools/memory-model/Documentation/explanation.txt
@@ -464,9 +464,10 @@ to address dependencies, since the address of a location accessed
through a pointer will depend on the value read earlier from that
pointer.
-Finally, a read event and another memory access event are linked by a
-control dependency if the value obtained by the read affects whether
-the second event is executed at all. Simple example:
+Finally, a read event X and a write event Y are linked by a control
+dependency if Y syntactically lies within an arm of an if statement and
+X affects the evaluation of the if condition via a data or address
+dependency (or similarly for a switch statement). Simple example:
int x, y;
--
2.31.1.189.g2e36527f23
next prev parent reply other threads:[~2022-10-19 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 23:06 [PATCH memory-model 0/5] LKMM updates for v6.2 Paul E. McKenney
2022-10-19 23:06 ` Paul E. McKenney [this message]
2022-10-19 23:06 ` [PATCH memory-model 2/5] docs/memory-barriers.txt: Add a missed closing parenthesis Paul E. McKenney
2022-10-19 23:06 ` [PATCH memory-model 3/5] docs/memory-barriers.txt/kokr: introduce io_stop_wc() and add implementation for ARM64 Paul E. McKenney
2022-10-19 23:06 ` [PATCH memory-model 4/5] docs/memory-barriers.txt/kokr: Add memory barrier dma_mb() Paul E. McKenney
2022-10-19 23:06 ` [PATCH memory-model 5/5] docs/memory-barriers.txt/kokr: Fix confusing name of 'data dependency barrier' 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=20221019230651.2502538-1-paulmck@kernel.org \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=charalampos.mainas@gmail.com \
--cc=dhowells@redhat.com \
--cc=elver@google.com \
--cc=j.alglave@ucl.ac.uk \
--cc=kernel-team@fb.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=martin.fink@in.tum.de \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paul.heidekrueger@in.tum.de \
--cc=peterz@infradead.org \
--cc=pramod.bhatotia@in.tum.de \
--cc=s.s.chakraborty@tudelft.nl \
--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
all inboxes | Powered by JetHome®