On Tue, 20 Aug 2024 14:17:54 +0100, Marc Zyngier wrote:
> Although FP8 support was merged in 6.9, the KVM side was dropped, with
> no sign of it being picked up again. Given that its absence is getting
> in the way of NV upstreaming (HCRX_EL2 needs fleshing out), here's a
> small series addressing it.
>
> The support is following the save/restore model established for the
> rest of the FP code, with FPMR being tied to it. The sole additions
> are the handling of traps in a nested context, and the corresponding
> ID registers being made writable. As an extra cleanup, SVCR and FPMR
> are moved into the sysreg array.
>
> [...]
Applied to next, thanks!
[1/8] KVM: arm64: Move SVCR into the sysreg array
commit: b55688943597df06f202c67341da5b9b0ec54e93
[2/8] KVM: arm64: Add predicate for FPMR support in a VM
commit: d4db98791aa5316677a1da9bfa0788068c9863dc
[3/8] KVM: arm64: Move FPMR into the sysreg array
commit: 7d9c1ed6f4bfa8d5fcafad847ac64e2839a04301
[4/8] KVM: arm64: Add save/restore support for FPMR
commit: ef3be86021c3bdf384c36d9d4aa1ee9fe65b95af
[5/8] KVM: arm64: Honor trap routing for FPMR
commit: b8f669b491ec4693d07126b20db0fbe747556d11
[6/8] KVM: arm64: Expose ID_AA64FPFR0_EL1 as a writable ID reg
commit: 6d7307651a8a021e7286e90264676b893cb6032d
[7/8] KVM: arm64: Enable FP8 support when available and configured
commit: c9150a8ad9cdb69584d4ec5af61481df41498eb8
[8/8] KVM: arm64: Expose ID_AA64PFR2_EL1 to userspace and guests
commit: 13c7a51eeb747ec315485ac7b13d4ea03707f53e
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
