All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Add write barrier before enabling DTL flags
Date: Wed, 25 Mar 2009 11:44:42 +1100	[thread overview]
Message-ID: <1237941882.6462.64.camel@localhost> (raw)
In-Reply-To: <200903241659.55302.jk@ozlabs.org>

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

On Tue, 2009-03-24 at 16:59 +1100, Jeremy Kerr wrote:
> Michael,
> 
> > Wouldn't this still be a problem on a UP kernel?
> 
> I don't believe so - stores should be ordered with respect to the 
> current CPU, and in the UP case we still get a barrier().

But what if the CPU decides to do the store to the enable_mask before
the stores to the other fields?

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-03-25  0:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<1236830152.729279.468331899806.3.gpush@pingu>
2009-03-24  2:40 ` [PATCH v2] powerpc: Add virtual processor dispatch trace log Jeremy Kerr
2009-03-24  2:55 ` [PATCH] powerpc: Add write barrier before enabling DTL flags Jeremy Kerr
2009-03-24  5:53   ` Michael Ellerman
2009-03-24  5:59     ` Jeremy Kerr
2009-03-25  0:44       ` Michael Ellerman [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=1237941882.6462.64.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=jk@ozlabs.org \
    --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 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.