From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrea Parri <parri.andrea@gmail.com>,
Will Deacon <will.deacon@arm.com>,
peterz@infradead.org, boqun.feng@gmail.com, npiggin@gmail.com,
dhowells@redhat.com, Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
Kernel development list <linux-kernel@vger.kernel.org>,
elena.reshetova@intel.com
Subject: Re: Prototype patch for Linux-kernel memory model
Date: Mon, 13 Nov 2017 20:52:20 -0800 [thread overview]
Message-ID: <20171114045220.GM3624@linux.vnet.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1711131501180.1410-100000@iolanthe.rowland.org>
On Mon, Nov 13, 2017 at 03:09:11PM -0500, Alan Stern wrote:
> On Mon, 13 Nov 2017, Paul E. McKenney wrote:
>
> > Hello!
> >
> > Please see below for the git commit corresponding to a prototype
> > patch for the Linux-kernel memory model. This addresses the feedback
> > we got at Linux Plumbers Conference:
> >
> > 1. There is a Documentation/recipes.txt file giving known-good
> > useful examples, along with corresponding litmus tests.
> >
> > 2. There is a Documentation/explanation.txt file giving an
> > overview of the memory model and its workings.
> >
> > 3. There is a Documentation/references.txt file giving some
> > background reading.
> >
> > I believe that we have something that will be extremely useful and
> > valuable to novices and experts alike.
> >
> > Please note that this version of the memory model does not yet reflect
> > the changes that make DEC Alpha no longer be a special case because
> > those changes have not yet hit mainline. The model will be updated
> > once this happens.
> >
> > Thoughts?
>
> In references.txt, should we add URLs to non-paywalled PDFs? Or should
> we assume that our readers are capable of using Google to find these
> things on their own?
>
> There are a few places where some comments should be resolved/removed
> before submission:
>
> Documentation/references.txt line 98:
> Uncategorized stuff (any of this really needed?)
>
> litmus-tests/README line 92:
> [ Shouldn't we have one with smp_wmb() in the process with both
> writes, and smp_mb() in the other process. ]
I updated these, recategorizing the "Uncategorized stuff" and removing
the note from litmus-tests/README -- we don't seem to use R in recipes
anyway.
> In the files defining the memory model, we should replace the GPL
> boilerplate with SPDX headers.
We can!
I pushed both commits.
Thanx, Paul
next prev parent reply other threads:[~2017-11-14 4:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 18:40 Paul E. McKenney
2017-11-13 20:09 ` Alan Stern
2017-11-14 4:52 ` Paul E. McKenney [this message]
2017-11-14 7:59 ` Peter Zijlstra
2017-11-14 15:19 ` Alan Stern
2017-11-14 17:15 ` Paul E. McKenney
2017-11-15 16:37 ` Paul E. McKenney
2017-11-17 11:27 ` Boqun Feng
2017-11-20 16:35 ` Andrea Parri
2017-11-20 19:30 ` Paul E. McKenney
2017-12-19 8:36 ` afzal mohammed
2017-12-19 16:05 ` Alan Stern
2017-12-20 11:31 ` afzal mohammed
2017-12-20 16:45 ` Paul E. McKenney
2017-12-21 3:30 ` afzal mohammed
2017-12-21 16:15 ` Paul E. McKenney
2017-12-22 4:11 ` afzal mohammed
2017-12-23 6:14 ` afzal mohammed
2018-01-02 20:25 ` 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=20171114045220.GM3624@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=elena.reshetova@intel.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@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
Powered by JetHome