From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Alexander Potapenko <glider@google.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Dmitriy Vyukov <dvyukov@google.com>,
James Y Knight <jyknight@google.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: Potentially missing "memory" clobbers in bitops.h for x86
Date: Mon, 1 Apr 2019 18:04:06 +0200 [thread overview]
Message-ID: <20190401160406.GE12232@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190401154414.GM4102@linux.ibm.com>
On Mon, Apr 01, 2019 at 08:44:14AM -0700, Paul E. McKenney wrote:
> On Mon, Apr 01, 2019 at 12:53:48PM +0200, Peter Zijlstra wrote:
> > On Fri, Mar 29, 2019 at 03:05:54PM -0700, Paul E. McKenney wrote:
> > > From Documentation/core-api/atomic_ops.rst:
> >
> > We should delete that file.
>
> Only if all of its content is fully present elsewhere. ;-)
Documentation/atomic_t.txt and Documentation/atomic_bitops.txt _should_
cover all of it I _think_. If there's anything mising, please tell and
we'll write more documents.
And I suppose we should ammend atomic_bitops.txt with a reference to
include/asm-generic/bitops/atomic.h which fully implements the atomic
bitops using atomic_t.
next prev parent reply other threads:[~2019-04-01 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 14:14 Potentially missing "memory" clobbers in bitops.h for x86 Alexander Potapenko
2019-03-28 16:22 ` Paul E. McKenney
2019-03-29 15:54 ` Alexander Potapenko
2019-03-29 20:52 ` H. Peter Anvin
2019-03-29 21:09 ` Paul E. McKenney
2019-03-29 21:51 ` H. Peter Anvin
2019-03-29 22:05 ` Paul E. McKenney
2019-03-29 22:30 ` hpa
2019-04-01 10:53 ` Peter Zijlstra
2019-04-01 15:44 ` Paul E. McKenney
2019-04-01 16:04 ` Peter Zijlstra [this message]
2019-04-01 15:00 ` Alexander Potapenko
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=20190401160406.GE12232@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=jyknight@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.ibm.com \
--cc=will.deacon@arm.com \
/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