diff options
author | 2024-03-01 17:42:31 +0000 | |
---|---|---|
committer | 2024-04-12 13:58:59 +0100 | |
commit | 5294afdbf45aced5295fe5941c58b40c41c23800 (patch) | |
tree | b4a85c3bf837fea6eb4ad2214dbf2b90045c5066 /arch/arm64/kvm/hyp/vhe/switch.c | |
parent | KVM: arm64: Exclude host_fpsimd_state pointer from kvm_vcpu_arch (diff) | |
download | wireguard-linux-5294afdbf45aced5295fe5941c58b40c41c23800.tar.xz wireguard-linux-5294afdbf45aced5295fe5941c58b40c41c23800.zip |
KVM: arm64: Exclude FP ownership from kvm_vcpu_arch
In retrospect, it is fairly obvious that the FP state ownership
is only meaningful for a given CPU, and that locating this
information in the vcpu was just a mistake.
Move the ownership tracking into the host data structure, and
rename it from fp_state to fp_owner, which is a better description
(name suggested by Mark Brown).
Reviewed-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to '')
-rw-r--r-- | arch/arm64/kvm/hyp/vhe/switch.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm64/kvm/hyp/vhe/switch.c b/arch/arm64/kvm/hyp/vhe/switch.c index 14b7a6bc5909..b92f9fe2d50e 100644 --- a/arch/arm64/kvm/hyp/vhe/switch.c +++ b/arch/arm64/kvm/hyp/vhe/switch.c @@ -258,7 +258,7 @@ static int __kvm_vcpu_run_vhe(struct kvm_vcpu *vcpu) sysreg_restore_host_state_vhe(host_ctxt); - if (vcpu->arch.fp_state == FP_STATE_GUEST_OWNED) + if (*host_data_ptr(fp_owner) == FP_STATE_GUEST_OWNED) __fpsimd_save_fpexc32(vcpu); __debug_switch_to_host(vcpu); |