From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: schwidefsky@de.ibm.com, borntraeger@de.ibm.com,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
parri.andrea@gmail.com, will.deacon@arm.com,
peterz@infradead.org, boqun.feng@gmail.com, npiggin@gmail.com,
dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
akiyks@gmail.com
Subject: Re: [PATCH RFC tools/memory-model] Add s390.{cfg,cat}
Date: Tue, 3 Apr 2018 08:16:42 -0700 [thread overview]
Message-ID: <20180403151642.GK3948@linux.vnet.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1804030946400.1399-100000@iolanthe.rowland.org>
On Tue, Apr 03, 2018 at 09:50:19AM -0400, Alan Stern wrote:
> On Mon, 2 Apr 2018, Paul E. McKenney wrote:
>
> > > > I will look at this more later, reaching end of both battery and useful
> > > > attention span...
> >
> > Like the following, perhaps?
> >
> > Thanx, Paul
> >
> > ------------------------------------------------------------------------
> >
> > s390
> >
> > include "fences.cat"
> > include "cos.cat"
> >
> > (* Fundamental coherence ordering *)
> > let com = rf | co | fr
> > acyclic po-loc | com as coherence
> >
> > (* Atomic *)
> > empty rmw & (fre;coe) as atom
> >
> > (* Fences *)
> > let mb = [M] ; fencerel(Mb) ; [M]
> >
> > (* TSO with multicopy atomicity *)
> > let po-ghb = ([R] ; po ; [M]) | ([M] ; po ; [W])
> > acyclic mb | po-ghb | fr | rf | co as sc
>
> Yes, that should work okay (apart from issues related to ordering of
> atomic accesses).
>
> By the way, what does that last "sc" stand for? Surely not Sequential
> Consistency! You might consider renaming it to "tso-mca".
Good point, fixed.
But it is the closest to SC in commercial computing systems, for whatever
that is worth. ;-)
Thanx, Paul
next prev parent reply other threads:[~2018-04-03 15:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 13:42 [PATCH RFC tools/memory-model] Add s390.{cfg,cat} Paul E. McKenney
2018-03-28 13:42 ` Paul E. McKenney
2018-03-28 13:48 ` Peter Zijlstra
2018-03-28 13:48 ` Peter Zijlstra
2018-03-28 14:20 ` Paul E. McKenney
2018-03-28 14:20 ` Paul E. McKenney
2018-03-28 16:49 ` Paul E. McKenney
2018-03-28 16:49 ` Paul E. McKenney
2018-03-28 15:01 ` Alan Stern
2018-03-28 15:01 ` Alan Stern
2018-03-28 16:33 ` Paul E. McKenney
2018-03-28 16:33 ` Paul E. McKenney
2018-03-28 18:04 ` Alan Stern
2018-03-28 18:04 ` Alan Stern
2018-03-29 2:18 ` Paul E. McKenney
2018-03-29 2:18 ` Paul E. McKenney
2018-03-29 14:40 ` Alan Stern
2018-03-29 14:40 ` Alan Stern
2018-04-02 19:31 ` Paul E. McKenney
2018-04-02 19:31 ` Paul E. McKenney
2018-04-03 13:50 ` Alan Stern
2018-04-03 13:50 ` Alan Stern
2018-04-03 15:16 ` Paul E. McKenney [this message]
2018-04-03 15:16 ` Paul E. McKenney
2018-03-28 17:51 ` Peter Zijlstra
2018-03-28 17:51 ` Peter Zijlstra
2018-03-29 1:33 ` Paul E. McKenney
2018-03-29 1:33 ` 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=20180403151642.GK3948@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=dhowells@redhat.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=parri.andrea@gmail.com \
--cc=peterz@infradead.org \
--cc=schwidefsky@de.ibm.com \
--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