[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1802211419350.2032-100000@iolanthe.rowland.org>
Date: Wed, 21 Feb 2018 14:27:04 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
cc: linux-kernel@...r.kernel.org, <linux-arch@...r.kernel.org>,
<mingo@...nel.org>, <parri.andrea@...il.com>,
<will.deacon@....com>, <peterz@...radead.org>,
<boqun.feng@...il.com>, <npiggin@...il.com>, <dhowells@...hat.com>,
<j.alglave@....ac.uk>, <luc.maranget@...ia.fr>, <akiyks@...il.com>,
<nborisov@...e.com>
Subject: Re: [PATCH RFC tools/lkmm 10/12] tools/memory-model: Add a S lock-based
external-view litmus test
On Wed, 21 Feb 2018, Paul E. McKenney wrote:
> > > +ISA2+pooncelock+pooncelock+pombonce.litmus
> > > + Tests whether the ordering provided by a lock-protected S litmus
> >
> > Call it an ISA2 litmus test, not an S litmus test!
>
> Given the structure of the test, the relationship to S is important
> because it helps motivate why anyone might care. But yes, having ISA2
> only in the filename is a bit obtuse. How about the following?
>
> ISA2+pooncelock+pooncelock+pombonce.litmus
> Tests whether the ordering provided by a lock-protected S
> litmus test is visible to an external process whose accesses are
> separated by smp_mb(). This addition of an external process to
> S is otherwise known as ISA2.
Okay, that's somewhat better.
However, I still don't understand why you think of this as a form of S.
In S, the first variable written by P0 is the same as the variable
written by P1. In this test, no variable other than the spinlock gets
written twice. To me that seems like a pretty fundamental difference.
Alan
Powered by blists - more mailing lists