From: Jeremy Kerr <jk@ozlabs.org>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Add write barrier before enabling DTL flags
Date: Tue, 24 Mar 2009 16:59:54 +1100 [thread overview]
Message-ID: <200903241659.55302.jk@ozlabs.org> (raw)
In-Reply-To: <1237874006.6478.284.camel@localhost>
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().
However, perhaps there are other considerations with the HV that I'm not
aware of. Anyone?
Cheers,
Jeremy
next prev parent reply other threads:[~2009-03-24 6:01 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 [this message]
2009-03-25 0:44 ` Michael Ellerman
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=200903241659.55302.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.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 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).