From: sathnaga <sathnaga@linux.vnet.ibm.com>
To: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org
Cc: mpe@ellerman.id.au, kvm-ppc@vger.kernel.org, paulus@ozlabs.org,
sjitindarsingh@gmail.com, mikey@neuling.org
Subject: Re: KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM workarounds
Date: Fri, 14 Sep 2018 22:34:39 +0530 [thread overview]
Message-ID: <b3c1442f7afc59d70fa813e29254f8f7@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180914165657.GB6306@MiWiFi-R3L-srv>
On 2018-09-14 22:26, sathnaga@linux.vnet.ibm.com wrote:
> Date: Thu, 13 Sep 2018 15:33:47 +1000
> From: Michael Neuling <mikey@neuling.org>
> To: mpe@ellerman.id.au
> Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org,
> paulus@ozlabs.org, sjitindarsingh@gmail.com, mikey@neuling.org
> Subject: KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM
> workarounds
>
> When we come into the softpatch handler (0x1500), we use r11 to store
> the HSRR0 for later use by the denorm handler.
>
> We also use the softpatch handler for the TM workarounds for
> POWER9. Unfortunately, in kvmppc_interrupt_hv we later store r11 out
> to the vcpu assuming it's still what we got from userspace.
>
> This causes r11 to be corrupted in the VCPU and hence when we restore
> the guest, we get a corrupted r11. We've seen this when running TM
> tests inside guests on P9.
>
> This fixes the problem by only touching r11 in the denorm case.
>
> Fixes: 4bb3c7a020 ("KVM: PPC: Book3S HV: Work around transactional
> memory bugs in POWER9")
> Cc: <stable@vger.kernel.org> # 4.17+
> Test-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
> Reviewed-by: Paul Mackerras <paulus@ozlabs.org>
> Signed-off-by: Michael Neuling <mikey@neuling.org>
> ---
> arch/powerpc/kernel/exceptions-64s.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Tested-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
Test details:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792501
Regards,
-Satheesh.
> diff --git a/arch/powerpc/kernel/exceptions-64s.S
> b/arch/powerpc/kernel/exceptions-64s.S
> index ea04dfb8c0..2d8fc8c9da 100644
> --- a/arch/powerpc/kernel/exceptions-64s.S
> +++ b/arch/powerpc/kernel/exceptions-64s.S
> @@ -1314,9 +1314,7 @@ EXC_REAL_BEGIN(denorm_exception_hv, 0x1500,
> 0x100)
>
> #ifdef CONFIG_PPC_DENORMALISATION
> mfspr r10,SPRN_HSRR1
> - mfspr r11,SPRN_HSRR0 /* save HSRR0 */
> andis. r10,r10,(HSRR1_DENORM)@h /* denorm? */
> - addi r11,r11,-4 /* HSRR0 is next instruction */
> bne+ denorm_assist
> #endif
>
> @@ -1382,6 +1380,8 @@ END_FTR_SECTION_IFCLR(CPU_FTR_ARCH_207S)
> */
> XVCPSGNDP32(32)
> denorm_done:
> + mfspr r11,SPRN_HSRR0
> + subi r11,r11,4
> mtspr SPRN_HSRR0,r11
> mtcrf 0x80,r9
> ld r9,PACA_EXGEN+EX_R9(r13)
>
next parent reply other threads:[~2018-09-14 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180914165657.GB6306@MiWiFi-R3L-srv>
2018-09-14 17:04 ` sathnaga [this message]
2018-09-13 5:33 [PATCH] KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM workarounds Michael Neuling
2018-09-21 11:59 ` 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=b3c1442f7afc59d70fa813e29254f8f7@linux.vnet.ibm.com \
--to=sathnaga@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.org \
--cc=sjitindarsingh@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).