From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Paul E. McKenney" <paulmck@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Will Deacon <will.deacon@arm.com>,
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>,
Akira Yokosawa <akiyks@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>
Subject: Re: [RFC PATCH] tools/memory-model: Remove (dep ; rfi) from ppo
Date: Fri, 22 Feb 2019 12:21:28 +0100 [thread overview]
Message-ID: <20190222112128.GA7213@andrea> (raw)
In-Reply-To: <20190220132714.GI32494@hirez.programming.kicks-ass.net>
> What I do object to is a model that's weaker than any possible sane
> hardware.
Not the first time I hear you calling this out. And inevitably, every
time, other slogans come to my mind: "C is not an assembly language",
"No features (ordering) without users", ...
For the record, I won't try to push this patch further; I also have no
plans to touch herd7 internals in order to add the ad-hoc flag for the
(dep ; rfi) thing. (Maybe others will/can step in here.)
In the meantime, the hope (admittedly, probably vain) is that this RFC
could serve as a further warning or as a reference to those developers
who are quivering to use (dep ; rfi): enjoy it, be careful.
Andrea
next prev parent reply other threads:[~2019-02-22 11:21 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 22:57 [RFC PATCH] tools/memory-model: Remove (dep ; rfi) from ppo Andrea Parri
2019-02-19 22:57 ` Andrea Parri
2019-02-20 2:01 ` Paul E. McKenney
2019-02-20 2:01 ` Paul E. McKenney
2019-02-20 9:26 ` Peter Zijlstra
2019-02-20 9:26 ` Peter Zijlstra
2019-02-20 9:57 ` Will Deacon
2019-02-20 9:57 ` Will Deacon
2019-02-20 13:17 ` Andrea Parri
2019-02-20 13:17 ` Andrea Parri
2019-02-20 13:14 ` Andrea Parri
2019-02-20 13:14 ` Andrea Parri
2019-02-20 13:27 ` Peter Zijlstra
2019-02-20 13:27 ` Peter Zijlstra
2019-02-22 11:21 ` Andrea Parri [this message]
2019-02-22 11:21 ` Andrea Parri
2019-02-22 13:00 ` Peter Zijlstra
2019-02-22 13:00 ` Peter Zijlstra
2019-02-25 17:55 ` Paul E. McKenney
2019-02-25 17:55 ` Paul E. McKenney
2019-02-26 9:21 ` Peter Zijlstra
2019-02-26 9:21 ` Peter Zijlstra
2019-02-26 9:30 ` Peter Zijlstra
2019-02-26 9:30 ` Peter Zijlstra
2019-02-26 10:45 ` Peter Zijlstra
2019-02-26 10:45 ` Peter Zijlstra
2019-02-26 11:21 ` Peter Zijlstra
2019-02-26 11:21 ` Peter Zijlstra
2019-02-26 11:25 ` Peter Zijlstra
2019-02-26 11:25 ` Peter Zijlstra
2019-02-26 11:30 ` Peter Zijlstra
2019-02-26 11:30 ` Peter Zijlstra
2019-02-26 11:38 ` Borislav Petkov
2019-02-26 11:38 ` Borislav Petkov
2019-02-26 13:49 ` Peter Zijlstra
2019-02-26 13:49 ` Peter Zijlstra
2019-02-26 14:28 ` Paul E. McKenney
2019-02-26 14:28 ` Paul E. McKenney
2019-02-26 14:47 ` Peter Zijlstra
2019-02-26 14:47 ` Peter Zijlstra
2019-02-26 15:39 ` Paul E. McKenney
2019-02-26 15:39 ` Paul E. McKenney
2019-02-26 14:56 ` Akira Yokosawa
2019-02-26 14:56 ` Akira Yokosawa
2019-02-26 15:04 ` Paul E. McKenney
2019-02-26 15:04 ` Paul E. McKenney
2019-02-26 15:09 ` Akira Yokosawa
2019-02-26 15:09 ` Akira Yokosawa
2019-02-26 15:04 ` Peter Zijlstra
2019-02-26 15:04 ` Peter Zijlstra
2019-03-06 15:46 ` Akira Yokosawa
2019-03-06 15:46 ` Akira Yokosawa
2019-03-06 16:58 ` Peter Zijlstra
2019-03-06 16:58 ` Peter Zijlstra
2019-03-06 17:26 ` Paul E. McKenney
2019-03-06 17:26 ` Paul E. McKenney
2019-03-06 17:24 ` Paul E. McKenney
2019-03-06 17:24 ` Paul E. McKenney
2019-03-02 15:27 ` Akira Yokosawa
2019-03-02 15:27 ` Akira Yokosawa
2019-03-04 16:09 ` Paul E. McKenney
2019-03-04 16:09 ` Paul E. McKenney
2019-02-20 13:41 ` Will Deacon
2019-02-20 13:41 ` Will Deacon
2019-02-20 15:30 ` Alan Stern
2019-02-20 15:30 ` Alan Stern
2019-02-20 15:22 ` Alan Stern
2019-02-20 15:22 ` Alan Stern
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=20190222112128.GA7213@andrea \
--to=andrea.parri@amarulasolutions.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.com \
/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