From: Zachary Amsden <zach@vmware.com>
To: "Brunner, Richard" <Richard.Brunner@amd.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
Hugh Dickins <hugh@veritas.com>,
Jan Beulich <jbeulich@novell.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386: PAE entries must have their low word cleared first
Date: Wed, 26 Apr 2006 15:22:52 -0700 [thread overview]
Message-ID: <444FF2BC.5010504@vmware.com> (raw)
In-Reply-To: <99F8FA0D1537DC4EB2A639E8E60D782A6288D0@SAUSEXMB3.amd.com>
Brunner, Richard wrote:
>
>
> Maybe the barrier is needed for other architectures, but two writes
> to WB memory are not going to happen out of order and so no
> barrier is needed on x86 to the best of my knowledge.
>
The barrier here is just a compiler barrier - wmb on x86 is just asm
volatile ("" ::: "memory"); This is needed to stop gcc reordering the
stores - not because the processor does respect them.
Zach
next prev parent reply other threads:[~2006-04-26 22:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 22:11 [PATCH] i386: PAE entries must have their low word cleared first Brunner, Richard
2006-04-26 22:22 ` Zachary Amsden [this message]
2006-04-26 22:27 ` Zachary Amsden
-- strict thread matches above, loose matches on Subject: below --
2006-04-26 13:46 Jan Beulich
2006-04-26 14:46 ` Hugh Dickins
2006-04-26 15:06 ` Keir Fraser
2006-04-26 15:44 ` Zachary Amsden
2006-04-26 15:57 ` Hugh Dickins
2006-04-26 16:12 ` Keir Fraser
2006-04-26 15:45 ` Hugh Dickins
2006-04-26 16:06 ` Nick Piggin
2006-04-26 15:58 ` Nick Piggin
2006-04-27 10:27 ` Sonny Rao
2006-04-27 13:39 ` Nick Piggin
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=444FF2BC.5010504@vmware.com \
--to=zach@vmware.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=Richard.Brunner@amd.com \
--cc=hugh@veritas.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.