From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Does Itanium permit speculative stores?
Date: Tue, 12 Nov 2013 10:31:46 -0800 [thread overview]
Message-ID: <20131112183146.GN4138@linux.vnet.ibm.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31D5DB28@ORSMSX106.amr.corp.intel.com>
On Tue, Nov 12, 2013 at 06:00:26PM +0000, Luck, Tony wrote:
> > Does Itanium permit speculative stores? For example, on Itanium what are
> > the permitted outcomes of the following litmus test, where both x and y
> > are initially zero?
>
> We have a complier visible speculative read via the "ld.s" and "chk" instructions. But
> there is no speculative write ("st.s") instruction. I think you are asking "can out of order
> writes become visible in this scenario?"
>
> CPU 0 CPU 1
>
> r1 = ACCESS_ONCE(x); r2 = ACCESS_ONCE(y);
> if (r1) if (r2)
> ACCESS_ONCE(y) = 1; ACCESS_ONCE(x) = 1;
>
> > In particular, is the outcome (r1 == 1 && r2 == 1) possible on Itanium
> > given this litmus test?
>
> The "ACCESS_ONCE" macro casts to volatile - which will make gcc generate
> ordered "ld.acq" and "st.rel" instructions for your code snippets. So I think
> you should be fine.
Excellent!!! Thank you for the information!
If I understand you correctly, this underscores the importance of
using ACCESS_ONCE() -- if you omit them in the above scenario, perhaps
you can see out-of-order stores becoming visible in this scenario?
Also, this resolves our earlier IRC discussion about Itanium's lack of
read-read cache coherence. If you use ACCESS_ONCE properly, then on
Itanium the reads will become ld.acq instructions, ensuring the expected
cache coherence.
Very nice!
Thanx, Paul
next prev parent reply other threads:[~2013-11-12 18:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:13 Does Itanium permit speculative stores? Paul E. McKenney
2013-11-12 18:00 ` Luck, Tony
2013-11-12 18:26 ` Peter Zijlstra
2013-11-12 18:46 ` Luck, Tony
2013-11-12 18:49 ` Peter Zijlstra
2013-11-12 21:29 ` Paul E. McKenney
2013-11-12 21:30 ` Paul E. McKenney
2013-11-12 18:31 ` Paul E. McKenney [this message]
2013-11-12 18:34 ` Peter Zijlstra
2013-11-27 4:55 ` Jon Masters
2013-11-27 17:19 ` 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=20131112183146.GN4138@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tony.luck@intel.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).