mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: "Paul Heidekrüger" <Paul.Heidekrueger@in.tum.de>
Cc: Andrea Parri <parri.andrea@gmail.com>,
	Will Deacon <will@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Nicholas Piggin <npiggin@gmail.com>,
	David Howells <dhowells@redhat.com>,
	Jade Alglave <j.alglave@ucl.ac.uk>,
	Luc Maranget <luc.maranget@inria.fr>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Akira Yokosawa <akiyks@gmail.com>,
	Daniel Lustig <dlustig@nvidia.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	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>
Subject: Re: [PATCH v3] tools/memory-model: Weaken ctrl dependency definition in explanation.txt
Date: Sat, 3 Sep 2022 11:54:27 -0400	[thread overview]
Message-ID: <YxN4s+ZcPiV7u5XG@rowland.harvard.edu> (raw)
In-Reply-To: <D7E3D42D-2ABE-4D16-9DCA-0605F0C84F7D@in.tum.de>

On Sat, Sep 03, 2022 at 01:41:34PM +0200, Paul Heidekrüger wrote:
> On 3. Sep 2022, at 03:27, Alan Stern <stern@rowland.harvard.edu> wrote:
> 
> > On Fri, Sep 02, 2022 at 09:13:40PM +0000, Paul Heidekrüger wrote:
> >> +Finally, a read event X and another memory access 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;
> 
> Hang on, shouldn't this read "a write event" instead of "another memory
> access event"? Control dependencies only provide ordering from READ_ONCE to
> WRITE_ONCE, not from READ_ONCE to (READ | WRITE)_ONCE?
> 
> Or am I missing something?

Whoops, you're right.  Somehow I missed that.  Go ahead and change it; 
you can keep by S-O-B.

Alan

      reply	other threads:[~2022-09-03 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 21:13 Paul Heidekrüger
2022-09-03  1:27 ` Alan Stern
2022-09-03 11:41   ` Paul Heidekrüger
2022-09-03 15:54     ` Alan Stern [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=YxN4s+ZcPiV7u5XG@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=Paul.Heidekrueger@in.tum.de \
    --cc=akiyks@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=charalampos.mainas@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dlustig@nvidia.com \
    --cc=elver@google.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=joel@joelfernandes.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=martin.fink@in.tum.de \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pramod.bhatotia@in.tum.de \
    --cc=s.s.chakraborty@tudelft.nl \
    --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®