On Tue, Feb 04, 2025 at 03:20:53PM +0000, Mark Rutland wrote: > There are several problems with the way hyp code lazily saves the host's > FPSIMD/SVE state, including: ... > Avoid these by eagerly saving and "flushing" the host's FPSIMD/SVE/SME > state when loading a vCPU such that KVM does not need to save any of the > host's FPSIMD/SVE/SME state. For clarity, fpsimd_kvm_prepare() is > removed and the necessary call to fpsimd_save_and_flush_cpu_state() is > placed in kvm_arch_vcpu_load_fp(). As 'fpsimd_state' and 'fpmr_ptr' > should not be used, they are set to NULL; all uses of these will be > removed in subsequent patches. This avoid any confusion so Reviewed-by: Mark Brown <broonie@xxxxxxxxxx>
Attachment:
signature.asc
Description: PGP signature
