On Wed, Jul 01, 2020 at 03:53:06PM -0600, Rob Herring wrote:
> If guests don't have certain CPU erratum work-arounds implemented, then
> there is a possibility a guest can deadlock the system. IOW, only trusted
> guests should be used on systems with the erratum.
>
> This is the case for Cortex-A57 erratum 832075.
>
> Cc: Marc Zyngier <m...@kernel.org>
> Cc: James Morse <james.mo...@arm.com>
> Cc: Julien Thierry <julien.thierry.k...@gmail.com>
> Cc: Suzuki K Poulose <suzuki.poul...@arm.com>
> Cc: Catalin Marinas <catalin.mari...@arm.com>
> Cc: Will Deacon <w...@kernel.org>
> Cc: kvmarm@lists.cs.columbia.edu
> Signed-off-by: Rob Herring <r...@kernel.org>
> ---
> arch/arm64/kvm/arm.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
> index 90cb90561446..e2f50fa4d825 100644
> --- a/arch/arm64/kvm/arm.c
> +++ b/arch/arm64/kvm/arm.c
> @@ -1653,6 +1653,10 @@ int kvm_arch_init(void *opaque)
> return -ENODEV;
> }
>
> + if (cpus_have_const_cap(ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE))
> + kvm_info("Guests without required CPU erratum work-arounds can
> deadlock system!\n" \
work-arounds => workarounds
(mainly for consistency, I have no clue if this is a real word or not!).
I'd also probably do erratum => errata given that you're about to add a
second one.
Will
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
