From: julien.grall@arm.com (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] arm64: KVM: Implement workaround for Cortex-A76 erratum 1165522
Date: Wed, 21 Nov 2018 12:23:31 +0000 [thread overview]
Message-ID: <06743f45-fd39-787d-0c59-12d28d8245bb@arm.com> (raw)
In-Reply-To: <20181105143617.120602-5-marc.zyngier@arm.com>
Hi Marc,
On 05/11/2018 14:36, Marc Zyngier wrote:
> Early versions of Cortex-A76 can end-up with corrupt TLBs if they
> speculate an AT instruction in during a guest switch while the
> S1/S2 system registers are in an inconsistent state.
>
> Work around it by:
> - Mandating VHE
> - Make sure that S1 and S2 system registers are consistent before
> clearing HCR_EL2.TGE, which allows AT to target the EL1 translation
> regime
>
> These two things together ensure that we cannot hit this erratum.
>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> ---
> Documentation/arm64/silicon-errata.txt | 1 +
> arch/arm64/Kconfig | 12 ++++++++++++
> arch/arm64/include/asm/cpucaps.h | 3 ++-
> arch/arm64/include/asm/kvm_host.h | 3 +++
> arch/arm64/include/asm/kvm_hyp.h | 6 ++++++
> arch/arm64/kernel/cpu_errata.c | 8 ++++++++
> arch/arm64/kvm/hyp/switch.c | 14 ++++++++++++++
> 7 files changed, 46 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/arm64/silicon-errata.txt b/Documentation/arm64/silicon-errata.txt
> index 76ccded8b74c..04f0bc4690c6 100644
> --- a/Documentation/arm64/silicon-errata.txt
> +++ b/Documentation/arm64/silicon-errata.txt
> @@ -57,6 +57,7 @@ stable kernels.
> | ARM | Cortex-A73 | #858921 | ARM64_ERRATUM_858921 |
> | ARM | Cortex-A55 | #1024718 | ARM64_ERRATUM_1024718 |
> | ARM | Cortex-A76 | #1188873 | ARM64_ERRATUM_1188873 |
> +| ARM | Cortex-A76 | #1165522 | ARM64_ERRATUM_1165522 |
> | ARM | MMU-500 | #841119,#826419 | N/A |
> | | | | |
> | Cavium | ThunderX ITS | #22375, #24313 | CAVIUM_ERRATUM_22375 |
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 787d7850e064..a68bc6cc2167 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -497,6 +497,18 @@ config ARM64_ERRATUM_1188873
>
> If unsure, say Y.
>
> +config ARM64_ERRATUM_1165522
> + bool "Cortex-A76: Speculative AT instruction using out-of-context translation regime could cause subsequent request to generate an incorrect translation"
> + default y
> + help
> + This option adds work arounds for ARM Cortex-A76 erratum 1165522
> +
> + Affected Cortex-A76 cores (r0p0, r1p0, r2p0) could end-up with
> + corrupted TLBs by speculating an AT instruction during a guest
> + context switch.
> +
> + If unsure, say Y.
Most of the code in the patch is not guarded by #ifdef ARM64_*. So is there any
benefits to add a Kconfig for this option?
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2018-11-21 12:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 14:36 [PATCH 0/4] Workaround for Cortex-A76 erratum 1165522 Marc Zyngier
2018-11-05 14:36 ` [PATCH 1/4] KVM: arm64: Rework detection of SVE, !VHE systems Marc Zyngier
2018-11-06 7:52 ` Christoffer Dall
2018-11-08 19:14 ` Dave Martin
2018-11-05 14:36 ` [PATCH 2/4] KVM: arm64: Allow implementations to be confined to using VHE Marc Zyngier
2018-11-06 7:53 ` Christoffer Dall
2018-11-08 17:51 ` Marc Zyngier
2018-11-08 19:23 ` Dave Martin
2018-11-05 14:36 ` [PATCH 3/4] arm64: KVM: Install stage-2 translation before enabling traps on VHE Marc Zyngier
2018-11-06 8:06 ` Christoffer Dall
2018-11-08 17:54 ` Marc Zyngier
2018-11-05 14:36 ` [PATCH 4/4] arm64: KVM: Implement workaround for Cortex-A76 erratum 1165522 Marc Zyngier
2018-11-05 18:34 ` James Morse
2018-11-08 17:18 ` Marc Zyngier
2018-11-09 11:39 ` James Morse
2018-11-06 8:15 ` Christoffer Dall
2018-11-08 18:05 ` Marc Zyngier
2018-11-08 20:10 ` Christoffer Dall
2018-11-22 16:13 ` Marc Zyngier
2018-11-23 9:57 ` Christoffer Dall
2018-11-21 12:23 ` Julien Grall [this message]
2018-11-21 12:58 ` Marc Zyngier
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=06743f45-fd39-787d-0c59-12d28d8245bb@arm.com \
--to=julien.grall@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).