From: Jonas Oberhauser <jonas.oberhauser@huawei.com>
To: Boqun Feng <boqun.feng@gmail.com>,
Jonas Oberhauser <jonas.oberhauser@huaweicloud.com>
Cc: "paulmck@kernel.org" <paulmck@kernel.org>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"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: Sat, 3 Dec 2022 11:58:36 +0000 [thread overview]
Message-ID: <4262e55407294a5989e766bc4dc48293@huawei.com> (raw)
In-Reply-To: <Y4pIwqK7SWft1xCl@boqun-archlinux>
-----Original Message-----
From: Boqun Feng [mailto:boqun.feng@gmail.com]
Sent: Friday, December 2, 2022 7:50 PM
> > Reviewed-by: Reviewed-by: Alan Stern <stern@rowland.harvard.edu>
> s/Reviewed-by: Reviewed-by:/Reviewed-by:^2 to save some space ? ;-)
Oh, I didn't know I'm allowed to compress things like that! Can I use ² as well to save another character?
> I wonder is this patch a first step to solve the OOTA problem you reported in OSS:
> https://static.sched.com/hosted_files/osseu2022/e1/oss-eu22-jonas.pdf
> If so maybe it's better to put the link in the commit log I think.
It's not directly related to that specific problem, it does solve some other OOTA issues though.
If you think we should link to the talk, there's also a video with slightly more updated slides from the actual talk: https://www.youtube.com/watch?v=iFDKhIxKhoQ
do you think I should link to both then?
Best wishes,
jonas
next prev parent reply other threads:[~2022-12-03 11:58 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 [this message]
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
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=4262e55407294a5989e766bc4dc48293@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=jonas.oberhauser@huaweicloud.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.