summaryrefslogtreecommitdiffstats
path: root/arch/arm64/kvm/hyp
diff options
context:
space:
mode:
authorFuad Tabba <tabba@google.com>2024-06-03 13:28:43 +0100
committerMarc Zyngier <maz@kernel.org>2024-06-04 15:06:32 +0100
commit87bb39ed40bdf1596b8820e800226e24eb642677 (patch)
tree0897925b7249ad7d1acc5c6f69846a8fd2ab5f76 /arch/arm64/kvm/hyp
parent47eb2d68d10208e6a9e89d10b66018e8d6ca0623 (diff)
downloadlinux-stable-87bb39ed40bdf1596b8820e800226e24eb642677.tar.gz
linux-stable-87bb39ed40bdf1596b8820e800226e24eb642677.tar.bz2
linux-stable-87bb39ed40bdf1596b8820e800226e24eb642677.zip
KVM: arm64: Reintroduce __sve_save_state
Now that the hypervisor is handling the host sve state in protected mode, it needs to be able to save it. This reverts commit e66425fc9ba3 ("KVM: arm64: Remove unused __sve_save_state"). Reviewed-by: Oliver Upton <oliver.upton@linux.dev> Signed-off-by: Fuad Tabba <tabba@google.com> Link: https://lore.kernel.org/r/20240603122852.3923848-2-tabba@google.com Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'arch/arm64/kvm/hyp')
-rw-r--r--arch/arm64/kvm/hyp/fpsimd.S6
1 files changed, 6 insertions, 0 deletions
diff --git a/arch/arm64/kvm/hyp/fpsimd.S b/arch/arm64/kvm/hyp/fpsimd.S
index 61e6f3ba7b7d..e950875e31ce 100644
--- a/arch/arm64/kvm/hyp/fpsimd.S
+++ b/arch/arm64/kvm/hyp/fpsimd.S
@@ -25,3 +25,9 @@ SYM_FUNC_START(__sve_restore_state)
sve_load 0, x1, x2, 3
ret
SYM_FUNC_END(__sve_restore_state)
+
+SYM_FUNC_START(__sve_save_state)
+ mov x2, #1
+ sve_save 0, x1, x2, 3
+ ret
+SYM_FUNC_END(__sve_save_state)