From: Peter Zijlstra <peterz@infradead.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Does Itanium permit speculative stores?
Date: Tue, 12 Nov 2013 19:49:07 +0100 [thread overview]
Message-ID: <20131112184907.GD16796@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31D5DF47@ORSMSX106.amr.corp.intel.com>
On Tue, Nov 12, 2013 at 06:46:20PM +0000, Luck, Tony wrote:
> > So the point we're having a discussion on is if any architecture has
> > visible speculative STORES and if there's an architecture that doesn't
> > have control dependencies.
> >
> > On the visible speculative STORES; can, if in the above example we have
> > regular loads/stores:
> >
> > LOAD r1, x LOAD r2, y
> > IF (r1) IF (r2)
> > STORE y, 1 STORE x, 1
> >
> > we observe: r1==1 && r2==1
> >
> > In order for that to be true; we must be able to observe the stores
> > before the loads are complete -- and therefore before the branches are a
> > certainty.
>
> Even without the ".acq" and ".rel" this code is still safe.
>
> Quoting ia64 SDM vol 1, Section 4.4.7 Memory Access Ordering"
> "In addition, memory writes and flushes must observe control dependencies"
>
> which I take to mean that the STORE can't be visible until we are certain of
> the outcome of the conditional.
Awesome!
next prev parent reply other threads:[~2013-11-12 18:49 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 [this message]
2013-11-12 21:29 ` Paul E. McKenney
2013-11-12 21:30 ` Paul E. McKenney
2013-11-12 18:31 ` Paul E. McKenney
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=20131112184907.GD16796@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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 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.