From: Jonas Oberhauser <jonas.oberhauser@huawei.com>
To: "paulmck@kernel.org" <paulmck@kernel.org>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>
Cc: Boqun Feng <boqun.feng@gmail.com>,
"parri.andrea@gmail.com" <parri.andrea@gmail.com>,
"will@kernel.org" <will@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"dhowells@redhat.com" <dhowells@redhat.com>,
"j.alglave@ucl.ac.uk" <j.alglave@ucl.ac.uk>,
"luc.maranget@inria.fr" <luc.maranget@inria.fr>,
"akiyks@gmail.com" <akiyks@gmail.com>,
"dlustig@nvidia.com" <dlustig@nvidia.com>,
"joel@joelfernandes.org" <joel@joelfernandes.org>,
"urezki@gmail.com" <urezki@gmail.com>,
"quic_neeraju@quicinc.com" <quic_neeraju@quicinc.com>,
"frederic@kernel.org" <frederic@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] tools: memory-model: Make plain accesses carry dependencies
Date: Sun, 4 Dec 2022 00:15:27 +0000 [thread overview]
Message-ID: <43c7ea9ebdd14497b85633950b014240@huawei.com> (raw)
In-Reply-To: <20221203231122.GZ4001@paulmck-ThinkPad-P17-Gen-1>
-----Original Message-----
From: Paul E. McKenney [mailto:paulmck@kernel.org]
Sent: Sunday, December 4, 2022 12:11 AM
To: stern@rowland.harvard.edu
> On Sat, Dec 03, 2022 at 04:32:19PM -0500, stern@rowland.harvard.edu wrote:
> > My advice: Omit them both.
> It would be good to reference something or another. ;-)
I also prefer to not refer to that presentation.
If there is a feeling that more context is needed, I would first prefer to enhance the commit message itself in some way. (Personally I don't feel that this is needed, and the imho the issue stands by itself even without reference to OOTA, which could be resolved fully independently e.g. by Viktor's suggestion to just axiomatically forbid OOTA --- the issue addressed by this patch would still exist).
If that's not satisfactory, I would also consent to publishing the e-mails from the thread starting where I relayed Viktor's observation of the relaxed accesses, but I don't recall it saying anything substantially beyond the current commit log + the documentation included in the patch.
best wishes, jonas
next prev parent reply other threads:[~2022-12-04 0:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 12:51 [PATCH v2] tools: memory-model: Make plain accesses carry dependencies Jonas Oberhauser
2022-12-02 14:44 ` Akira Yokosawa
2022-12-02 18:49 ` Boqun Feng
2022-12-03 11:58 ` Jonas Oberhauser
2022-12-03 19:02 ` Paul E. McKenney
2022-12-03 20:14 ` Boqun Feng
2022-12-03 20:40 ` Paul E. McKenney
2022-12-03 20:34 ` stern
2022-12-03 20:44 ` Paul E. McKenney
2022-12-03 20:52 ` Boqun Feng
2022-12-03 21:16 ` Paul E. McKenney
2022-12-03 21:32 ` stern
2022-12-03 23:11 ` Paul E. McKenney
2022-12-04 0:15 ` Jonas Oberhauser [this message]
2022-12-04 8:33 ` Boqun Feng
2022-12-05 13:42 ` Jonas Oberhauser
2022-12-05 16:18 ` stern
2022-12-06 20:46 ` Boqun Feng
2022-12-06 20:52 ` Boqun Feng
2022-12-08 21:37 ` stern
2022-12-05 19:49 ` Boqun Feng
2022-12-07 1:43 ` Boqun Feng
2022-12-08 21:06 ` Boqun Feng
2022-12-09 0:01 ` 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=43c7ea9ebdd14497b85633950b014240@huawei.com \
--to=jonas.oberhauser@huawei.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=frederic@kernel.org \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=quic_neeraju@quicinc.com \
--cc=stern@rowland.harvard.edu \
--cc=urezki@gmail.com \
--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