On Mon, Jan 29, 2018 at 07:57:24AM +0100, Ingo Molnar wrote:
> 
> hi Paul,
> 
> * Paul E. McKenney <[email protected]> wrote:
> 
> > Hello, Ingo,
> > 
> > This pull request contains a single commit that adds a memory model to
> > the tools directory.  This memory model can (roughly speaking) be thought
> > of as an automated version of memory-barriers.txt.  It is written in the
> > "cat" language, which is executable by the externally provided "herd7"
> > simulator, which exhaustively explores the state space of small litmus
> > tests.
> > 
> > This memory model is accompanied by extensive documentation on its use
> > and its design.  Two versions have been sent to LKML and feedback
> > incorporated:
> > 
> > 1.  http://lkml.kernel.org/r/[email protected]
> > 2.  http://lkml.kernel.org/r/[email protected]
> > 
> > This model has been presented and demoed at a number of Linux gatherings,
> > including the 2016 LinuxCon EU, the 2016 Linux Plumbers Conference,
> > the 2016 Linux Kernel Summit, the 2017 linux.conf.au, and the 2017 Linux
> > Plumbers Conference, which featured a workshop helping a number of Linux
> > kernel hackers install and use the tool.
> > 
> > This memory model has matured to the point where it would be good to include
> > it in the Linux kernel, for example, to allow it to track changes as new
> > hardware and use cases are added.  We expect the rate of change to be 
> > similar
> > to that of Documentation/memory-barriers.txt.
> > 
> > This memory model is available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git 
> > 
> > for you to fetch changes up to 1c27b644c0fdbc61e113b8faee14baeb8df32486:
> > 
> >   Automate memory-barriers.txt; provide Linux-kernel memory model 
> > (2018-01-24 20:53:49 -0800)
> 
> Looks good to me, but the commit is not in the master branch of your tree, 
> which 
> branch should I pull?

Oops!!!  The branch is lkmm-for-mingo.

Please accept my apologies for the implicit maintainer treasure hunt!

                                                        Thanx, Paul

Reply via email to