From: Michael Neuling <mikey@neuling.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, will_schmidt@vnet.ibm.com,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] fixes for the SLB shadow buffer
Date: Thu, 02 Aug 2007 18:56:48 +1000 [thread overview]
Message-ID: <13166.1186045008@neuling.org> (raw)
In-Reply-To: <1186039870.5495.595.camel@localhost.localdomain>
> >
> > But even in the case of a checkpoint restart, the ordering will be
> > preserved as the NIA we get as part of the checkpoint will have all
> > previous instructions complete and none of the following instructions
> > started.
>
> Instruction completion isn't enough to ensure storage ordering. The
> stores may well be complete but the data still in separate store queues.
POWER6 flushes the store queues when we take a checkpoint.
>
> > So I guess the questions is, does PHYP even need to access the shadow
> > buffer of another CPU, while that other CPU is in flight. I'm not
> > sure
> > that they can as they can't read the entire buffer atomically if the
> > target CPU is still active. So PHYP must stop instructions on the
> > target CPU, before it reads it's shadow buffer. Hence no ordering
> > problems.
> >
> > I should probably talk to some PHYP guys to confirm, but i think we
> > can
> > remove all the barriers when writing to the shadow buffer
>
> Bah, just keep then in, eieio's won't hurt much and it doesn't look like
> a critically hot code path.
Ok
Mikey
next prev parent reply other threads:[~2007-08-02 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 4:56 [PATCH] fixes for the SLB shadow buffer Michael Neuling
2007-08-01 5:28 ` Paul Mackerras
2007-08-01 6:02 ` Michael Neuling
2007-08-01 21:48 ` Will Schmidt
2007-08-02 5:56 ` Michael Neuling
2007-08-02 7:31 ` Benjamin Herrenschmidt
2007-08-02 8:56 ` Michael Neuling [this message]
2007-08-02 8:58 ` Benjamin Herrenschmidt
2007-08-02 9:03 ` Michael Neuling
2007-08-02 9:14 ` Benjamin Herrenschmidt
2007-08-02 9:28 ` Michael Neuling
2007-08-03 1:55 ` Michael Neuling
2007-08-03 2:50 ` Benjamin Herrenschmidt
2007-08-01 22:33 ` Benjamin Herrenschmidt
2007-08-01 23:32 ` Michael Neuling
2007-08-02 0:05 ` Benjamin Herrenschmidt
2007-08-02 1:04 ` Benjamin Herrenschmidt
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=13166.1186045008@neuling.org \
--to=mikey@neuling.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=will_schmidt@vnet.ibm.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 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.