[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151104135431.GS29027@linux.vnet.ibm.com>
Date: Wed, 4 Nov 2015 05:54:31 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Dmitry Vyukov <dvyukov@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] locking changes for v4.4
On Wed, Nov 04, 2015 at 12:48:50PM +0100, Ingo Molnar wrote:
>
> * Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>
> > On Tue, Nov 3, 2015 at 3:58 PM, Linus Torvalds
> > <torvalds@...ux-foundation.org> wrote:
> > >
> > > I think I'll pull this, but then just make a separate commit to remove
>
> Thanks!
>
> > > all the bogus games with "control" dependencies that seem to have no basis is
> > > reality.
> >
> > So the attached is what I committed in my tree. [...]
>
> Acked-by: Ingo Molnar <mingo@...nel.org>
>
> > + dependency into nonexistence. Careful use of READ_ONCE() or
> > + atomic{,64}_read() can help to preserve your control dependency.
> > + Please see the Compiler Barrier section for more information.
>
> So technically it's the "COMPILER BARRIER" section, but this is a pre-existing
> formulation and the document doesn't use such references consistently so I guess
> it doesn't matter much.
I will take a pass through and fix these up. I don't see this as urgent,
so will add it to my patches for the next merge window.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists