]> git.ipfire.org Git - thirdparty/linux.git/commit
KVM: arm64: Disable fields that KVM doesn't know how to handle in ID_AA64PFR1_EL1
authorShaoqin Huang <shahuang@redhat.com>
Tue, 23 Jul 2024 07:20:00 +0000 (03:20 -0400)
committerMarc Zyngier <maz@kernel.org>
Sun, 25 Aug 2024 16:48:43 +0000 (17:48 +0100)
commitffe68b2d19a5a84440fea99a732cfc3b157559eb
treee40e172c1748c6311b0293cf8a91749ecf1fa3e8
parent980c41f554c3029ce4f99678c0cd95296212775f
KVM: arm64: Disable fields that KVM doesn't know how to handle in ID_AA64PFR1_EL1

For some of the fields in the ID_AA64PFR1_EL1 register, KVM doesn't know
how to handle them right now. So explicitly disable them in the register
accessor, then those fields value will be masked to 0 even if on the
hardware the field value is 1. This is safe because from a UAPI point of
view that read_sanitised_ftr_reg() doesn't yet return a nonzero value
for any of those fields.

This will benifit the migration if the host and VM have different values
when restoring a VM.

Those fields include RNDR_trap, NMI, MTE_frac, GCS, THE, MTEX, DF2, PFAR.

Signed-off-by: Shaoqin Huang <shahuang@redhat.com>
Link: https://lore.kernel.org/r/20240723072004.1470688-2-shahuang@redhat.com
Signed-off-by: Marc Zyngier <maz@kernel.org>
arch/arm64/kvm/sys_regs.c