[RFC PATCH v2 0/3] KVM: arm64: Don't claim MTE_ASYNC if not supported
Marc Zyngier
maz at kernel.org
Fri May 16 05:04:10 PDT 2025
On Mon, 12 May 2025 12:41:09 +0100, Ben Horgan wrote:
> The ID_AA64PFR1_EL1.MTE_frac field is currently hidden from KVM.
> However, when ID_AA64PFR1_EL1.MTE==2, ID_AA64PFR1_EL1.MTE_frac==0
> indicates that MTE_ASYNC is supported. On a host with
> ID_AA64PFR1_EL1.MTE==2 but without MTE_ASYNC support a guest with the
> MTE capability enabled will incorrectly see MTE_ASYNC advertised as
> supported. This series fixes that.
>
> [...]
Applied to next, thanks!
[1/3] arm64/sysreg: Expose MTE_frac so that it is visible to KVM
commit: 5799a2983fea4f22f6aaa291aee3b704db81d29f
[2/3] KVM: arm64: Make MTE_frac masking conditional on MTE capability
commit: fe21ff5d4b46c06c4e43a310fdb781d1e6b5173e
[3/3] KVM: selftests: Confirm exposing MTE_frac does not break migration
commit: 69018866d2baa014413e340744bfb342ec0cdbcd
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
More information about the linux-arm-kernel
mailing list