From: Will Deacon <will.deacon@arm.com>
To: bob smith <sfmc68@verizon.net>
Cc: paulmck@linux.vnet.ibm.com, rth@twiddle.net,
ink@jurassic.park.msu.ru, mattst88@gmail.com,
stern@rowland.harvard.edu, j.alglave@ucl.ac.uk,
luc.maranget@inria.fr, parri.andrea@gmail.com,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Question about DEC Alpha memory ordering
Date: Mon, 13 Feb 2017 19:08:39 +0000 [thread overview]
Message-ID: <20170213190839.GI10256@arm.com> (raw)
In-Reply-To: <ee22c179-9020-7101-96df-30f8e2e469b8@verizon.net>
On Mon, Feb 13, 2017 at 01:53:27PM -0500, bob smith wrote:
> On 2/13/17 1:39 PM, Paul E. McKenney wrote:
> > can real DEC Alpha hardware end up with both instances of "r1"
> > having the value 1?
>
> I thought this question reminded me of something, so I found this:
> > https://www.kernel.org/doc/Documentation/memory-barriers.txt
>
> and I pasted in the content - David Howells is one of the authors and
> maybe that is why the question sort of reminded me.
>
> Maybe someone has an update but this is what was said then.
>
> ============================
> LINUX KERNEL MEMORY BARRIERS
> ============================
>
> By: David Howells <dhowells@redhat.com>
> Paul E. McKenney <paulmck@linux.vnet.ibm.com>
^^^^^^^^^^^^^^^^
There's only one Paul E. McKenney.
Will
next prev parent reply other threads:[~2017-02-13 19:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 18:39 Question about DEC Alpha memory ordering Paul E. McKenney
2017-02-13 18:53 ` bob smith
2017-02-13 19:08 ` Will Deacon [this message]
2017-02-13 19:09 ` Paul E. McKenney
2017-02-13 19:14 ` Tobias Klausmann
2017-02-13 20:28 ` Paul E. McKenney
2017-02-13 21:06 ` Alan Stern
2017-02-13 21:06 ` Alan Stern
2017-02-13 21:24 ` Paul E. McKenney
2017-02-14 11:35 ` Andrea Parri
2017-02-14 19:26 ` Michael Cree
2017-02-14 20:12 ` Andrea Parri
2017-02-13 19:23 ` Michael Cree
2017-02-13 20:32 ` 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=20170213190839.GI10256@arm.com \
--to=will.deacon@arm.com \
--cc=ink@jurassic.park.msu.ru \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mattst88@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rth@twiddle.net \
--cc=sfmc68@verizon.net \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.