From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] spin_unlock() problem
Date: Mon, 07 Apr 2003 22:58:13 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705431@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705414@msgid-missing>
>>>>> On 07 Apr 2003 18:09:44 -0400, Jes Sorensen <jes@wildopensource.com> said:
Jes> Quoting section 4.4.7 "Memory Access Ordering", 2nd paragraph,
Jes> it says " .... Release data accesses guarantee that all
Jes> previous data accesses are made visible prior to being made
Jes> visible themselves."
Oops, sorry, I got it exactly backwards. ;-(
So much for giving a "quick" reply...
Jes> The way I understand that, it is possible that a store
Jes> performed after an st.rel may become visible prior to the
Jes> st.rel, like in this example:
Jes> st [r2] = r32 (1)
Jes> st.rel [r3] = r33 (2)
Jes> st [r4] = r34 (3)
Jes> In other words we are only guarantied that [r2] is valid when
Jes> [r3] appears but have no guarantie that [r4] doesn't show up on
Jes> the bus prior to [r3]?
I wouldn't use the word "valid" here, but yes, (2) and (3) are NOT
ordered.
--david
next prev parent reply other threads:[~2003-04-07 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 4:51 [Linux-ia64] spin_unlock() problem Jes Sorensen
2003-04-04 5:04 ` Jes Sorensen
2003-04-04 14:43 ` Van Maren, Kevin
2003-04-04 14:49 ` Van Maren, Kevin
2003-04-04 15:13 ` Jes Sorensen
2003-04-07 21:09 ` David Mosberger
2003-04-07 21:14 ` David Mosberger
2003-04-07 22:09 ` Jes Sorensen
2003-04-07 22:18 ` Luck, Tony
2003-04-07 22:58 ` David Mosberger [this message]
2003-04-07 23:13 ` Jes Sorensen
2003-04-07 23:30 ` Jim Hull
2003-04-07 23:38 ` Chen, Kenneth W
2003-04-08 0:14 ` David Mosberger
2003-04-08 0:15 ` David Mosberger
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=marc-linux-ia64-105590723705431@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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