From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: josh@joshtriplett.org, linux-kernel@vger.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>,
Nicholas Miell <nmiell@comcast.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [RFC PATCH v13] sys_membarrier(): system/process-wide memory barrier (x86)
Date: Wed, 18 Mar 2015 07:41:48 -0700 [thread overview]
Message-ID: <20150318144147.GA5312@linux.vnet.ibm.com> (raw)
In-Reply-To: <352367913.22769.1426620435634.JavaMail.zimbra@efficios.com>
On Tue, Mar 17, 2015 at 07:27:15PM +0000, Mathieu Desnoyers wrote:
> ----- Original Message -----
> > ----- Original Message -----
> > > On Tue, Mar 17, 2015 at 01:22:02PM -0400, Mathieu Desnoyers wrote:
> > > > --- a/init/Kconfig
> > > > +++ b/init/Kconfig
> > > > @@ -1568,6 +1568,15 @@ config PCI_QUIRKS
> > > > bugs/quirks. Disable this only if your target machine is
> > > > unaffected by PCI quirks.
> > > >
> > > > +config MEMBARRIER
> > > > + bool "Enable membarrier() system call" if EXPERT
> > > > + default y
> > > > + help
> > > > + Enable the membarrier() system call that allows issuing
> > > > + memory barriers across cores.
> > >
> > > Nit: CPUs, not cores. Nothing here is specific to
> > > packages/cores/threads.
> >
> > Fixed.
> >
> > >
> > > > --- a/kernel/rcu/update.c
> > > > +++ b/kernel/rcu/update.c
> > > > @@ -49,6 +49,8 @@
> > > > #include <linux/module.h>
> > > > #include <linux/kthread.h>
> > > > #include <linux/tick.h>
> > > > +#include <linux/syscalls.h>
> > > > +#include <linux/membarrier.h>
> > > >
> > > > #define CREATE_TRACE_POINTS
> > > >
> > > > @@ -775,3 +777,73 @@ late_initcall(rcu_verify_early_boot_tests);
> > > > #else
> > > > void rcu_early_boot_tests(void) {}
> > > > #endif /* CONFIG_PROVE_RCU */
> > > > +
> > > > +#ifdef CONFIG_MEMBARRIER
> > >
> > > As mentioned in my previous mail, please consider moving this to its own
> > > file, if it doesn't use any of the internals of kernel/rcu/update.c
> > > (which I don't think it does). That then means you can enable/disable
> > > the entire file in the Makefile rather than using an #ifdef in the .c
> > > file.
> >
> > Will do, thanks!
>
> I'm adding include/uapi/linux/membarrier.h and kernel/membarrier.c,
> how should I add them to the MAINTAINERS file ?
I suggest adding them as their own entry, with yourself as maintainer.
I would be willing to be co-maintainer, and perhaps some of the others
in this thread would also be willing.
Thanx, Paul
next prev parent reply other threads:[~2015-03-18 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 17:22 [RFC PATCH v13] sys_membarrier(): system/process-wide memory barrier (x86) Mathieu Desnoyers
2015-03-17 17:30 ` Peter Zijlstra
2015-03-17 17:57 ` josh
2015-03-17 18:08 ` Peter Zijlstra
2015-03-17 19:01 ` Mathieu Desnoyers
2015-03-17 20:28 ` Olaf Titz
2015-03-17 23:36 ` Josh Triplett
2015-03-17 18:00 ` josh
2015-03-17 18:54 ` Mathieu Desnoyers
2015-03-17 19:27 ` Mathieu Desnoyers
2015-03-18 14:41 ` Paul E. McKenney [this message]
2015-03-18 16:22 ` Mathieu Desnoyers
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=20150318144147.GA5312@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=josh@joshtriplett.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=nmiell@comcast.net \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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.