- Original Message -
[...]
> > 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 t
On Tue, Mar 17, 2015 at 07:27:15PM +, 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
On Tue, Mar 17, 2015 at 07:01:23PM +, Mathieu Desnoyers wrote:
> - Original Message -
> > On Tue, Mar 17, 2015 at 10:57:50AM -0700, j...@joshtriplett.org wrote:
> > > On Tue, Mar 17, 2015 at 06:30:35PM +0100, Peter Zijlstra wrote:
> > > > On Tue, Mar 17, 2015 at 01:22:02PM -0400, Mathie
> I am tempted to leave the "flags" argument in place though, along
> with the "MEMBARRIER_QUERY" flag. Thoughts ?
http://lwn.net/Articles/585415/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
- 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
> >
- Original Message -
> On Tue, Mar 17, 2015 at 10:57:50AM -0700, j...@joshtriplett.org wrote:
> > On Tue, Mar 17, 2015 at 06:30:35PM +0100, Peter Zijlstra wrote:
> > > On Tue, Mar 17, 2015 at 01:22:02PM -0400, Mathieu Desnoyers wrote:
> > > > Here is an implementation of a new system call,
- 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.
> >
>
On Tue, Mar 17, 2015 at 10:57:50AM -0700, j...@joshtriplett.org wrote:
> On Tue, Mar 17, 2015 at 06:30:35PM +0100, Peter Zijlstra wrote:
> > On Tue, Mar 17, 2015 at 01:22:02PM -0400, Mathieu Desnoyers wrote:
> > > Here is an implementation of a new system call, sys_membarrier(), which
> > > execute
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 "Enabl
On Tue, Mar 17, 2015 at 06:30:35PM +0100, Peter Zijlstra wrote:
> On Tue, Mar 17, 2015 at 01:22:02PM -0400, Mathieu Desnoyers wrote:
> > Here is an implementation of a new system call, sys_membarrier(), which
> > executes a memory barrier on either all running threads of the current
> > process (ME
On Tue, Mar 17, 2015 at 01:22:02PM -0400, Mathieu Desnoyers wrote:
> Here is an implementation of a new system call, sys_membarrier(), which
> executes a memory barrier on either all running threads of the current
> process (MEMBARRIER_PRIVATE) issues a memory barrier on all threads
> running on th
Here is an implementation of a new system call, sys_membarrier(), which
executes a memory barrier on either all running threads of the current
process (MEMBARRIER_PRIVATE) issues a memory barrier on all threads
running on the system (~MEMBARRIER_PRIVATE). Both are currently
implemented by calling s
12 matches
Mail list logo
