public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Andrea Parri <andrea.parri@amarulasolutions.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	linux-kernel@vger.kernel.org, akiyks@gmail.com,
	boqun.feng@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
	luc.maranget@inria.fr, npiggin@gmail.com, peterz@infradead.org,
	stern@rowland.harvard.edu, will.deacon@arm.com
Subject: Re: [PATCH 0/2] tools/memory-model: remove ACCESS_ONCE()
Date: Thu, 28 Jun 2018 08:21:40 -0700	[thread overview]
Message-ID: <20180628152140.GK3593@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180628123845.GA14456@andrea>

On Thu, Jun 28, 2018 at 02:38:45PM +0200, Andrea Parri wrote:
> On Thu, Jun 28, 2018 at 01:33:45PM +0100, Mark Rutland wrote:
> > Since commit:
> >     
> >   b899a850431e2dd0 ("compiler.h: Remove ACCESS_ONCE()")
> >     
> > ... there has been no definition of ACCESS_ONCE() in the kernel tree,
> > and it has been necessary to use READ_ONCE() or WRITE_ONCE() instead.
> > 
> > However, since then the kernel memory model was added to the Linux tree,
> > sporting new instances of ACCESS_ONCE() in examples and in the memory
> > model itself.
> > 
> > These patches remove the new instances of ACCESS_ONCE() for consistency
> > with the contemporary codebase.
> > 
> > Thanks,
> > Mark.
> > 
> > Mark Rutland (2):
> >   tools/memory-model: remove ACCESS_ONCE() from recipes
> >   tools/memory-model: remove ACCESS_ONCE() from model
> 
> For the series:
> 
> Acked-by: Andrea Parri <andrea.parri@amarulasolutions.com>

Applied, thank you both!  These both are ready for the upcoming merge
window.

While I am at it, here is the current scorecard:

e9ff68680cd4 tools/memory-model: Add litmus test for full multicopy atomicity
c21fcc6594f1 tools/memory-model: Fix ISA2+pooncelock+pooncelock+pombonce name
aa838e0b70e1 MAINTAINERS: Add Daniel Lustig as an LKMM reviewer
3cb0d7701c4c locking/memory-barriers.txt/kokr: Update Korean translation to fix broken DMA vs. MMIO ordering example
0bde941f3629 tools/memory-model: Remove ACCESS_ONCE() from recipes
80b7b05c3aa0 tools/memory-model: Remove ACCESS_ONCE() from model

	The above patches are ready for the upcoming merge window because
	each has at least one Acked-by or Reviewed-by.

6098ce88bc4d tools/memory-model: Make scripts executable
5bb22d0126f9 tools/memory-model: Rename litmus tests to comply to norm7
1bc179880fba docs: atomic_ops: Describe atomic_set as a write operation

	The above patches need at least one additional Acked-by
	or Reviewed-by.  If any of you gets a chance, please do
	look them over.

51b0a8985c5a EXP tools/memory-model: Add litmus-test naming scheme

	This patch needs me to get Will Deacon's feedback applied.  :-/

06e99a0d9662 EXP tools/memory-model: Add .cfg and .cat files for s390

	This is a placeholder, and probably won't ever go upstream
	into the Linux kernel.  (Maybe someday into herd where the
	other architecture-specific .cat files live.)

							Thanx, Paul

> Cheers,
>   Andrea
> 
> 
> > 
> >  tools/memory-model/Documentation/recipes.txt | 4 ++--
> >  tools/memory-model/linux-kernel.bell         | 2 +-
> >  2 files changed, 3 insertions(+), 3 deletions(-)
> > 
> > -- 
> > 2.11.0
> > 
> 


  reply	other threads:[~2018-06-28 15:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 12:33 [PATCH 0/2] tools/memory-model: remove ACCESS_ONCE() Mark Rutland
2018-06-28 12:33 ` [PATCH 1/2] tools/memory-model: remove ACCESS_ONCE() from recipes Mark Rutland
2018-06-28 12:33 ` [PATCH 2/2] tools/memory-model: remove ACCESS_ONCE() from model Mark Rutland
2018-06-28 12:38 ` [PATCH 0/2] tools/memory-model: remove ACCESS_ONCE() Andrea Parri
2018-06-28 15:21   ` Paul E. McKenney [this message]
2018-06-28 16:51     ` Andrea Parri
2018-07-02 18:54       ` Paul E. McKenney
2018-07-03 10:12         ` Andrea Parri
2018-07-03 15:53           ` Paul E. McKenney
2018-07-03 17:23             ` Andrea Parri
2018-07-06 14:55               ` Paul E. McKenney
2018-06-28 22:22     ` Akira Yokosawa
2018-06-29  3:05       ` Paul E. McKenney
2018-07-07  0:17         ` LKMM patch scorecard for v4.19 merge window Paul E. McKenney
2018-07-09 18:18           ` Alan Stern
2018-07-09 23:01             ` Paul E. McKenney
2018-07-10 20:05             ` 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=20180628152140.GK3593@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akiyks@gmail.com \
    --cc=andrea.parri@amarulasolutions.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=mark.rutland@arm.com \
    --cc=npiggin@gmail.com \
    --cc=peterz@infradead.org \
    --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