From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Is volatile always verboten for FSL QE structures?
Date: Sat, 03 Oct 2009 21:20:08 +1000 [thread overview]
Message-ID: <1254568808.7122.21.camel@pasglop> (raw)
In-Reply-To: <20091003095537.GA15992@honey.hogyros.de>
> Making the target of foo volatile properly rechecks the condition on
> each iteration.
>
> OTOH my PPC box runs fine, so I'm probably missing something obvious.
Probably because the IO accessors do -both- volatile casts and
add the barriers :-)
Ben.
prev parent reply other threads:[~2009-10-03 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 14:14 Is volatile always verboten for FSL QE structures? Michael Barkowski
2009-10-02 14:46 ` Timur Tabi
2009-10-02 16:41 ` Kumar Gala
2009-10-02 16:57 ` Michael Barkowski
2009-10-02 18:08 ` Guillaume Knispel
2009-10-03 9:55 ` Simon Richter
2009-10-03 11:20 ` Benjamin Herrenschmidt [this message]
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=1254568808.7122.21.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Simon.Richter@hogyros.de \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).