From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org,
ynorov@caviumnetworks.com, rruigrok@codeaurora.org,
linux-arch@vger.kernel.org, akpm@linux-foundation.org,
catalin.marinas@arm.com, rth@twiddle.net,
ink@jurassic.park.msu.ru, mattst88@gmail.com,
linux-alpha@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] arm64: mm: Use READ_ONCE/WRITE_ONCE when accessing page tables
Date: Thu, 28 Sep 2017 09:07:43 -0700 [thread overview]
Message-ID: <20170928160743.GN3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170928154954.GA9892@arm.com>
On Thu, Sep 28, 2017 at 04:49:54PM +0100, Will Deacon wrote:
> On Thu, Sep 28, 2017 at 08:43:54AM -0700, Paul E. McKenney wrote:
> > On Thu, Sep 28, 2017 at 09:45:35AM +0100, Will Deacon wrote:
> > > On Thu, Sep 28, 2017 at 10:38:01AM +0200, Peter Zijlstra wrote:
> > > > On Wed, Sep 27, 2017 at 04:49:28PM +0100, Will Deacon wrote:
> > > > > In many cases, page tables can be accessed concurrently by either another
> > > > > CPU (due to things like fast gup) or by the hardware page table walker
> > > > > itself, which may set access/dirty bits. In such cases, it is important
> > > > > to use READ_ONCE/WRITE_ONCE when accessing page table entries so that
> > > > > entries cannot be torn, merged or subject to apparent loss of coherence.
> > > >
> > > > In fact, we should use lockless_dereference() for many of them. Yes
> > > > Alpha is the only one that cares about the difference between that and
> > > > READ_ONCE() and they do have the extra barrier, but if we're going to do
> > > > this, we might as well do it 'right' :-)
> > >
> > > I know this sounds daft, but I think one of the big reasons why
> > > lockless_dereference() doesn't get an awful lot of use is because it's
> > > such a mouthful! Why don't we just move the smp_read_barrier_depends()
> > > into READ_ONCE? Would anybody actually care about the potential impact on
> > > Alpha (which, frankly, is treading on thin ice given the low adoption of
> > > lockless_dereference())?
> >
> > This is my cue to ask my usual question... ;-)
> >
> > Are people still running mainline kernels on Alpha? (Added Alpha folks.)
> >
> > As always, if anyone is, we must continue to support Alpha, but sounds
> > like time to check again.
>
> I'll be honest and say that I haven't updated mine for a while, but I do
> have a soft spot for those machines :(
Let's see what the Alpha folks say. I myself have had a close
relationship with Alpha for almost 20 years, but I suspect that in
my case it is more a hard spot on my head rather than a soft spot in
my heart. ;-)
Thanx,
Paul
next prev parent reply other threads:[~2017-09-28 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1506527369-19535-1-git-send-email-will.deacon@arm.com>
[not found] ` <1506527369-19535-2-git-send-email-will.deacon@arm.com>
[not found] ` <20170928083801.m6rb4frbbgzgam2o@hirez.programming.kicks-ass.net>
[not found] ` <20170928084535.GA19060@arm.com>
2017-09-28 15:43 ` [RFC PATCH 1/2] arm64: mm: Use READ_ONCE/WRITE_ONCE when accessing page tables Paul E. McKenney
2017-09-28 15:49 ` Will Deacon
2017-09-28 16:07 ` Paul E. McKenney [this message]
2017-09-28 18:59 ` Michael Cree
2017-09-29 0:58 ` Paul E. McKenney
2017-09-29 9:08 ` Will Deacon
2017-09-29 16:29 ` Paul E. McKenney
2017-09-29 16:33 ` Will Deacon
2017-10-03 19:11 ` Paul E. McKenney
2017-10-05 16:31 ` Will Deacon
2017-10-05 19:22 ` Paul E. McKenney
2017-10-05 19:31 ` Andrea Parri
2017-10-05 20:09 ` Paul E. McKenney
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=20170928160743.GN3521@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=ink@jurassic.park.msu.ru \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=peterz@infradead.org \
--cc=rruigrok@codeaurora.org \
--cc=rth@twiddle.net \
--cc=will.deacon@arm.com \
--cc=ynorov@caviumnetworks.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;
as well as URLs for NNTP newsgroup(s).