[lkml]   [2018]   [Mar]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH RFC tools/memory-model] Add s390.{cfg,cat}
On Wed, 28 Mar 2018, Paul E. McKenney wrote:

> > > In the meantime, does the cat file look to you like it correctly
> > > models the combination of TSO and multicopy atomicity? Do the
> > > fences really work, or did I just get lucky with my choice of
> > > litmus tests?
> >
> > You got lucky. Try creating an SB litmus test where, instead of an
> > smp_mb() fence between the write and the read, each thread executes
> > some other kind of fence.
> Ah, it does indeed get "Never" in that case, which I do not believe
> to e correct.
> > The acyclicity condition should have been written more like this:
> >
> > let po_ghb = ([R] ; po ; [M]) | ([M] ; po ; [W])
> >
> > acyclic mfence | po_ghb | rf | fr | co as tso-mca
> >
> > I don't know what the fence instruction is on s390; change the "mfence"
> > above accordingly. The main difference between this and the
> > corresponding expression in is that I replaced rfe with rf.
> The s390 fence instruction is "bcr 14,0" or "bcr 15,0", depending on
> how recent of hardware you are running. The latter works everywhere,
> if I recall correctly. But I do not believe that herd knows about either
> instruction yet.

Herd does not need to understand s390 assembly in order to handle the
things defined in linux.def, such as "smp_mb()". linux.def doesn't
contain any x86 assembly language stuff either (or PPC or ARM).

> Ah, and I need to lose the "empty rmw & (fre;coe)".
> That appears to be where my spurious ordering was coming from, strange
> though that seems to me.

No, don't drop it; it was not the source of your spurious ordering.
The extra ordering came from your "(po \ (W * R))" term, which
unintentionally matches fences as well as memory accesses.

> And your use of "rf" instead of "rfe" makes sense, as that is what makes
> the read-from-write provide ordering, correct? And that should also cover
> the "Uniproc check" that would otherwise be required, right?

I don't think so...

> Except that I get "Sometimes" on CoWR+poonceonce+Once.litmus...


> Which I can fix by unioning po-loc into po-ghb. Or is there some
> better way to do this?

You could just keep the "uniproc" check. These two approaches accept
the same set of litmus tests.

Logically, I think of these as two distinct categories of ordering.
po_ghb and tso-mca have to do with the order in which stores reach the
cache, whereas "uniproc" (AKA sequential consistency per variable) has
to do with enforcement of the cache coherence requirements. Clearly
they are related, but they aren't the same thing.

> > This doesn't account for atomic operations properly; see the "implied"
> > term in
> I will look at this more later, reaching end of both battery and useful
> attention span...


 \ /
  Last update: 2018-03-29 16:40    [W:0.077 / U:4.228 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site