From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] POWER9 PMU interrupt after idle workaround
Date: Mon, 10 Jul 2017 17:50:18 +0530 [thread overview]
Message-ID: <a9de7aa8-6d0c-b910-7a24-6c1bd65fba3d@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170710061938.22513-1-npiggin@gmail.com>
On Monday 10 July 2017 11:49 AM, Nicholas Piggin wrote:
> POWER9 DD2 can see spurious PMU interrupts after state-loss idle in
> some conditions.
>
> A solution is to save and reload MMCR0 over state-loss idle.
Acked-by: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---
> arch/powerpc/kernel/idle_book3s.S | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kernel/idle_book3s.S b/arch/powerpc/kernel/idle_book3s.S
> index 5adb390e773b..516ebef905c0 100644
> --- a/arch/powerpc/kernel/idle_book3s.S
> +++ b/arch/powerpc/kernel/idle_book3s.S
> @@ -30,6 +30,7 @@
> * Use unused space in the interrupt stack to save and restore
> * registers for winkle support.
> */
> +#define _MMCR0 GPR0
> #define _SDR1 GPR3
> #define _PTCR GPR3
> #define _RPR GPR4
> @@ -272,6 +273,14 @@ power_enter_stop:
> b pnv_wakeup_noloss
>
> .Lhandle_esl_ec_set:
> + /*
> + * POWER9 DD2 can incorrectly set PMAO when waking up after a
> + * state-loss idle. Saving and restoring MMCR0 over idle is a
> + * workaround.
> + */
> + mfspr r4,SPRN_MMCR0
> + std r4,_MMCR0(r1)
> +
> /*
> * Check if the requested state is a deep idle state.
> */
> @@ -450,10 +459,14 @@ ALT_FTR_SECTION_END_IFSET(CPU_FTR_ARCH_300)
> pnv_restore_hyp_resource_arch300:
> /*
> * Workaround for POWER9, if we lost resources, the ERAT
> - * might have been mixed up and needs flushing.
> + * might have been mixed up and needs flushing. We also need
> + * to reload MMCR0 (see comment above).
> */
> blt cr3,1f
> PPC_INVALIDATE_ERAT
> + ld r1,PACAR1(r13)
> + ld r4,_MMCR0(r1)
> + mtspr SPRN_MMCR0,r4
> 1:
> /*
> * POWER ISA 3. Use PSSCR to determine if we
next prev parent reply other threads:[~2017-07-10 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 6:19 [PATCH] POWER9 PMU interrupt after idle workaround Nicholas Piggin
2017-07-10 12:20 ` Madhavan Srinivasan [this message]
2017-07-14 11:41 ` Anton Blanchard
2017-07-21 11:13 ` 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=a9de7aa8-6d0c-b910-7a24-6c1bd65fba3d@linux.vnet.ibm.com \
--to=maddy@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.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 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).