All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrea Parri <andrea.parri@amarulasolutions.com>,
	LKMM Maintainers -- Akira Yokosawa <akiyks@gmail.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	David Howells <dhowells@redhat.com>,
	Jade Alglave <j.alglave@ucl.ac.uk>,
	Luc Maranget <luc.maranget@inria.fr>,
	Nicholas Piggin <npiggin@gmail.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	dlustig@nvidia.com
Subject: Re: [PATCH 2/2] tools/memory-model: Add write ordering by release-acquire and by locks
Date: Thu, 5 Jul 2018 15:46:57 +0100	[thread overview]
Message-ID: <20180705144656.GF14470@arm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1807051010380.1697-100000@iolanthe.rowland.org>

On Thu, Jul 05, 2018 at 10:21:36AM -0400, Alan Stern wrote:
> On Wed, 4 Jul 2018, Will Deacon wrote:
> > On Tue, Jul 03, 2018 at 01:28:17PM -0400, Alan Stern wrote:
> > > Would this be allowed if smp_load_acquire() was implemented with LDAPR?
> > > If the answer is yes then we will have to remove the rfi-rel-acq and
> > > rel-rf-acq-po relations from the memory model entirely.
> > 
> > I don't understand what you mean by "rfi-rel-acq-po", and I assume you mean
> > rel-rfi-acq-po for the other? Sounds like I'm confused here.
> 
> "rfi-rel-acq" is the relation which was removed by the first of my two
> patches (it is now back in business since Paul reverted the commits),
> and "rel-rf-acq-po" is the relation that was introduced to replace it.

Sorry, yes, I realised this after I'd replied. Curious: but why do you name
the relations this way around, as opposed to e.g. rel-rfi-acq? It's
obviously up to you, but I just couldn't figure out what inspired the
ordering.

> At any rate, it looks like instead of strengthening the relation, I
> should write a patch that removes it entirely.  I also will add new,
> stronger relations for use with locking, essentially making spin_lock
> and spin_unlock be RCsc.

Thanks, Alan. I'll try to review them a bit more quickly this time, too.

Will

  reply	other threads:[~2018-07-05 14:46 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21 17:27 [PATCH 2/2] tools/memory-model: Add write ordering by release-acquire and by locks Alan Stern
2018-06-21 18:04 ` Peter Zijlstra
2018-06-22  3:34   ` Paul E. McKenney
2018-06-22  8:08     ` Peter Zijlstra
2018-06-22  8:09 ` Will Deacon
2018-06-22  9:55   ` Will Deacon
2018-06-22 10:31     ` Peter Zijlstra
2018-06-22 10:38       ` Will Deacon
2018-06-22 11:25         ` Andrea Parri
2018-06-22 16:40       ` Paul E. McKenney
2018-06-22 18:09   ` Alan Stern
2018-06-22 18:30     ` Will Deacon
2018-06-22 19:11       ` Alan Stern
2018-06-22 20:53         ` Paul E. McKenney
2018-07-04 11:53         ` Will Deacon
2018-06-25  8:19       ` Andrea Parri
2018-07-03 17:28         ` Alan Stern
2018-07-04 11:28           ` Paul E. McKenney
2018-07-04 12:13             ` Will Deacon
2018-07-05 14:23               ` Alan Stern
2018-07-05 15:31                 ` Paul E. McKenney
2018-07-04 12:11           ` Will Deacon
2018-07-05 14:00             ` Andrea Parri
2018-07-05 14:44               ` Will Deacon
2018-07-05 15:16                 ` Daniel Lustig
2018-07-05 15:35                   ` Daniel Lustig
2018-07-05 14:21             ` Alan Stern
2018-07-05 14:46               ` Will Deacon [this message]
2018-07-05 14:57                 ` Alan Stern
2018-07-05 15:15                   ` Will Deacon
2018-07-05 15:09               ` Andrea Parri
2018-07-06 20:37                 ` Alan Stern
2018-07-06 21:10                   ` Paul E. McKenney
2018-07-09 16:52                     ` Will Deacon
2018-07-09 17:29                       ` Daniel Lustig
2018-07-09 19:18                         ` Alan Stern
2018-07-05 15:31               ` Paul E. McKenney
2018-07-05 15:39                 ` Andrea Parri
2018-07-05 16:58                   ` Paul E. McKenney
2018-07-05 17:06                     ` Andrea Parri
2018-07-05 15:44                 ` Daniel Lustig
2018-07-05 16:22                   ` Will Deacon
2018-07-05 16:56                     ` Paul E. McKenney
2018-07-05 18:12                       ` Daniel Lustig
2018-07-05 18:38                         ` Andrea Parri
2018-07-05 18:44                           ` Andrea Parri
2018-07-05 23:32                             ` Paul E. McKenney
2018-07-05 23:31                           ` Paul E. McKenney
2018-07-06  9:25                       ` Will Deacon
2018-07-06 14:14                         ` Paul E. McKenney
2018-06-25  7:32     ` Peter Zijlstra
2018-06-25  8:29       ` Andrea Parri
2018-06-25  9:06         ` Peter Zijlstra
2018-06-22  9:06 ` Andrea Parri
2018-06-22 19:23   ` 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=20180705144656.GF14470@arm.com \
    --to=will.deacon@arm.com \
    --cc=akiyks@gmail.com \
    --cc=andrea.parri@amarulasolutions.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dlustig@nvidia.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=npiggin@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.