diff options
author | Marc Zyngier <maz@kernel.org> | 2021-10-10 16:09:06 +0100 |
---|---|---|
committer | Marc Zyngier <maz@kernel.org> | 2021-10-17 11:06:36 +0100 |
commit | 562e530fd7707aad7fed953692d1835612238966 (patch) | |
tree | c5c826ecc1cd23f3a57467f128c5e91caa3aa393 /lib/test_fortify/write_overflow-strncpy.c | |
parent | 9e1ff307c779ce1f0f810c7ecce3d95bbae40896 (diff) |
KVM: arm64: Force ID_AA64PFR0_EL1.GIC=1 when exposing a virtual GICv3
Until now, we always let ID_AA64PFR0_EL1.GIC reflect the value
visible on the host, even if we were running a GICv2-enabled VM
on a GICv3+compat host.
That's fine, but we also now have the case of a host that does not
expose ID_AA64PFR0_EL1.GIC==1 despite having a vGIC. Yes, this is
confusing. Thank you M1.
Let's go back to first principles and expose ID_AA64PFR0_EL1.GIC=1
when a GICv3 is exposed to the guest. This also hides a GICv4.1
CPU interface from the guest which has no business knowing about
the v4.1 extension.
Reviewed-by: Alexandru Elisei <alexandru.elisei@arm.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20211010150910.2911495-2-maz@kernel.org
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy.c')
0 files changed, 0 insertions, 0 deletions