mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul Heidekrüger" <Paul.Heidekrueger@in.tum.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Joel Fernandes <joel@joelfernandes.org>,
	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>,
	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] tools/memory-model: Weaken ctrl dependency definition in explanation.txt
Date: Fri, 2 Sep 2022 22:53:26 +0200	[thread overview]
Message-ID: <2FD673C3-F8FA-428C-B8B1-4DBC71AFDF0C@in.tum.de> (raw)
In-Reply-To: <YxIQrT+jFteFd8+e@rowland.harvard.edu>

[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]

On 2. Sep 2022, at 16:18, Alan Stern <stern@rowland.harvard.edu> wrote:

> On Fri, Sep 02, 2022 at 10:40:34AM +0200, Paul Heidekrüger wrote:
>> On 31. Aug 2022, at 19:38, Alan Stern <stern@rowland.harvard.edu> 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.  Similarly for switch statements.
>>>> 
>>>> What do you think?
>>> 
>>> I like the second one.  How about combining the last two sentences?  
>>> 
>>> 	... via a data or address dependency (or similarly for a switch 
>>> 	statement).
>> 
>> Yes, sounds good!
>> 
>>> Now I suppose someone will pipe up and ask about the conditional 
>>> expressions in "for", "while" and "do" statements...  :-)
>> 
>> Happy to have obliged :-)
>> https://lore.kernel.org/all/20F4C097-24B4-416B-95EE-AC11F5952B44@in.tum.de/
>> 
>> Do you think the text should explicitly address control dependencies in the
>> context of loops as well? If yes, would it be a separate patch, or would it
>> make sense to combine it with this one?
> 
> Anything else should be a separate patch.
> 
> For the time being, I'm happy not to worry about loops.  In the end
> we'll probably have to describe them as though they were unrolled,
> with all the complications that entails.

OK, sounds good!

Since there aren't any other immediate objections, I'll go ahead an resubmit
a v3 version of the patch with all the changes we discussed then.

Many thanks,
Paul

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5449 bytes --]

      reply	other threads:[~2022-09-02 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 20:44 Paul Heidekrüger
2022-08-30 21:08 ` Joel Fernandes
2022-08-30 21:12   ` Joel Fernandes
2022-08-31  1:57     ` Alan Stern
2022-08-31 16:42       ` Paul Heidekrüger
2022-08-31 17:38         ` Alan Stern
2022-08-31 18:27           ` Paul E. McKenney
2022-09-02  8:40           ` Paul Heidekrüger
2022-09-02 14:18             ` Alan Stern
2022-09-02 20:53               ` Paul Heidekrüger [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=2FD673C3-F8FA-428C-B8B1-4DBC71AFDF0C@in.tum.de \
    --to=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=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=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®