From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@lists.ozlabs.org, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH] powerpc: Invalidate ERAT on powersave wakeup for POWER9
Date: Fri, 23 Jun 2017 05:45:36 -0500 [thread overview]
Message-ID: <1498214736.31581.77.camel@kernel.crashing.org> (raw)
In-Reply-To: <87mv8zoxp8.fsf@concordia.ellerman.id.au>
On Fri, 2017-06-23 at 19:33 +1000, Michael Ellerman wrote:
> Michael Neuling <mikey@neuling.org> writes:
>
> > On POWER9 the ERAT may be incorrect on wakeup from some stop states
> > that lose state. This causes random segvs and illegal instructions
> > when these stop states are enabled.
>
> Incorrect how?
As in stale. Not sure about the details.
> Because with the ERAT flush where you've put it, there's still a good
> amount of code executed prior to the flush isn't there?
In real mode, should be ok.
> ie. we come in at 0x100, do some of the prolog, do IDLE_TEST which takes
> us to pnv_powersave_wakeup, which then restores state from the paca
> (memory), that returns and then we check KVM ... and then finally we end
> up at pnv_wakeup_loss.
>
> Or is there some other path? Or is the ERAT incorrect in some specific
> way which means we only need to flush there?
I think real mode translations are ok but I'll ask around.
Cheers,
Ben.
> cheers
>
> > diff --git a/arch/powerpc/kernel/idle_book3s.S b/arch/powerpc/kernel/idle_book3s.S
> > index 1ea14b96f1..ace2ad50c8 100644
> > --- a/arch/powerpc/kernel/idle_book3s.S
> > +++ b/arch/powerpc/kernel/idle_book3s.S
> > @@ -793,6 +793,9 @@ fastsleep_workaround_at_exit:
> > */
> > .global pnv_wakeup_loss
> > pnv_wakeup_loss:
> > +BEGIN_FTR_SECTION
> > + PPC_INVALIDATE_ERAT
> > +END_FTR_SECTION_IFSET(CPU_FTR_ARCH_300)
> > ld r1,PACAR1(r13)
> > BEGIN_FTR_SECTION
> > CHECK_HMI_INTERRUPT
> > --
> > 2.11.0
next prev parent reply other threads:[~2017-06-23 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 17:26 [PATCH] powerpc: Invalidate ERAT on powersave wakeup for POWER9 Michael Neuling
2017-06-23 0:50 ` Stewart Smith
2017-06-23 2:12 ` Michael Neuling
2017-06-23 3:09 ` Michael Neuling
2017-06-23 9:33 ` Michael Ellerman
2017-06-23 10:24 ` Nicholas Piggin
2017-06-23 10:45 ` Benjamin Herrenschmidt [this message]
2017-06-23 10:22 ` Anshuman Khandual
2017-06-24 17:29 ` [PATCH v2] " Benjamin Herrenschmidt
2017-06-25 5:18 ` Nicholas Piggin
2017-06-29 12:21 ` [v2] " 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=1498214736.31581.77.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).