Re: Prototype patch for Linux-kernel memory model

[afzal mohammed]

Hi,

On Wed, Dec 20, 2017 at 08:45:38AM -0800, Paul E. McKenney wrote:
> On Wed, Dec 20, 2017 at 05:01:45PM +0530, afzal mohammed wrote:

> > > +It is tempting to assume that CPU0()'s store to x is globally ordered
> > > +before CPU1()'s store to z, but this is not the case:
> > > +
> > > +	/* See Z6.0+pooncerelease+poacquirerelease+mbonceonce.litmus. */
> > > +	void CPU0(void)
> > > +	{
> > > +		WRITE_ONCE(x, 1);
> > > +		smp_store_release(&y, 1);
> > > +	}
> > > +
> > > +	void CPU1(void)
> > > +	{
> > > +		r1 = smp_load_acquire(y);
> > > +		smp_store_release(&z, 1);
> > > +	}
> > > +
> > > +	void CPU2(void)
> > > +	{
> > > +		WRITE_ONCE(z, 2);
> > > +		smp_mb();
> > > +		r2 = READ_ONCE(x);
> > > +	}
> > > +
> > > +One might hope that if the final value of r1 is 1 and the final value
> > > +of z is 2, then the final value of r2 must also be 1, but the opposite
> > > +outcome really is possible.
> > 
> > As there are 3 variables to have the values, perhaps, it might be
> > clearer to have instead of "the opposite.." - "the final value need
> > not be 1" or was that a read between the lines left as an exercise to
> > the idiots ;)
> 
> Heh!  Good catch, thank you!  How about the following for the paragraph
> immediately after that litmus test?
> 
> 	One might hope that if the final value of r0 is 1 and the final
> 	value of z is 2, then the final value of r1 must also be 1,
> 	but it really is possible for r1 to have the final value of 0.
> 	The reason, of course, is that in this version, CPU2() is not
> 	part of the release-acquire chain.  This situation is accounted
> 	for in the rules of thumb below.
> 
> I also fixed r1 and r2 to match the names in the actual litmus test.

Since it is now mentioned that r1 can have final value of 0, though it
is understood, it might make things crystal clear and for the sake of
completeness to also show the non-automatic variable x being
initialized to 0.

Thanks for taking into account my opinion.

afzal