linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dmitry Vyukov <dvyukov@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] locking changes for v4.4
Date: Wed, 4 Nov 2015 12:48:50 +0100	[thread overview]
Message-ID: <20151104114850.GA30862@gmail.com> (raw)
In-Reply-To: <CA+55aFwOgy-_Z64sszX9wUbdj+RBMUNtCu97xOwvHb2w3mnFiA@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Tue, Nov 3, 2015 at 3:58 PM, Linus Torvalds
> <torvalds@linux-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@kernel.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.

Thanks,

	Ingo

  parent reply	other threads:[~2015-11-04 11:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03  9:16 [GIT PULL] locking changes for v4.4 Ingo Molnar
2015-11-03 23:54 ` Linus Torvalds
2015-11-03 23:58   ` Linus Torvalds
2015-11-04  1:30     ` Linus Torvalds
2015-11-04  4:16       ` Paul E. McKenney
2015-11-04 14:51         ` Dmitry Vyukov
2015-11-04 16:01           ` Peter Zijlstra
2015-11-04 16:09             ` Dmitry Vyukov
2015-11-04 11:37       ` Peter Zijlstra
2015-11-04 13:55         ` Paul E. McKenney
2015-11-04 11:48       ` Ingo Molnar [this message]
2015-11-04 13:54         ` Paul E. McKenney
2015-11-04 14:56           ` Ingo Molnar

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=20151104114850.GA30862@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).