diff options
| author | Marc Zyngier | 2021-03-05 18:52:53 +0000 |
|---|---|---|
| committer | Paolo Bonzini | 2021-03-06 04:18:41 -0500 |
| commit | 9739f6ef053f104a997165701c6e15582c4307ee (patch) | |
| tree | 9d587b064d86e522cce5ffb4cdb9183baf908fb4 /crypto/async_tx/raid6test.c | |
| parent | b9d699e2694d032aa8ecc15141f698ccb050dc95 (diff) | |
KVM: arm64: Workaround firmware wrongly advertising GICv2-on-v3 compatibility
It looks like we have broken firmware out there that wrongly advertises
a GICv2 compatibility interface, despite the CPUs not being able to deal
with it.
To work around this, check that the CPU initialising KVM is actually able
to switch to MMIO instead of system registers, and use that as a
precondition to enable GICv2 compatibility in KVM.
Note that the detection happens on a single CPU. If the firmware is
lying *and* that the CPUs are asymetric, all hope is lost anyway.
Reported-by: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Tested-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Message-Id: <20210305185254.3730990-8-maz@kernel.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'crypto/async_tx/raid6test.c')
0 files changed, 0 insertions, 0 deletions