public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	Hugh Dickins <hugh@veritas.com>,
	Jan Beulich <jbeulich@novell.com>,
	Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	Pratap Subrahmanyam <pratap@vmware.com>
Subject: Re: [PATCH 2/2] I386 convert pae wmb to non smp
Date: Wed, 26 Apr 2006 18:09:59 -0700	[thread overview]
Message-ID: <445019E7.80900@vmware.com> (raw)
In-Reply-To: <445009A2.3030305@yahoo.com.au>

Nick Piggin wrote:
> Zachary Amsden wrote:
>
>> Similar to the last bug, on set_pte, we don't want the compiler to 
>> re-order
>> the write of the PTE, even in non-SMP configurations, since if the 
>> write of
>> the low word occurs first, the TLB could prefetch a bad highmem 
>> mapping which
>> has been aliased into low memory.
>>
>
> wmb() means that it also orders IO memory. It is no difference for
> i386, but smp_wmb() actually has the right semantics of the abstract
> Linux memory model.

The name is pretty confused.  smp_wmb seems to imply an SMP-only 
barrier, whereas we want here a write barrier on regular memory.  Both 
smp_wmb and wmb() are identical in that they both reduce to barrier 
today, but I confess not to know which one semantically is correct.  
Your call on this patch - it is unecessary, I thought it was more 
semantically correct, but you probably know that better than me.  So, 
drop part 2 of this patch?

Zach

  reply	other threads:[~2006-04-27  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26 22:03 [PATCH 2/2] I386 convert pae wmb to non smp Zachary Amsden
2006-04-27  0:00 ` Nick Piggin
2006-04-27  1:09   ` Zachary Amsden [this message]
2006-04-27  3:30     ` Nick Piggin
2006-04-27  8:21       ` Keir Fraser

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=445019E7.80900@vmware.com \
    --to=zach@vmware.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=akpm@osdl.com \
    --cc=hugh@veritas.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pratap@vmware.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