KVM: arm64: Remove unused __sve_save_state
Now that we don't have any users left for __sve_save_state, remove it altogether. Should we ever need to save the SVE state from the hypervisor again, we can always re-introduce it. Suggested-by: Zenghui Yu <yuzenghui@huawei.com> Signed-off-by: Marc Zyngier <maz@kernel.org>
This commit is contained in:
parent
8383741ab2
commit
e66425fc9b
|
@ -90,7 +90,6 @@ void __debug_restore_host_buffers_nvhe(struct kvm_vcpu *vcpu);
|
||||||
|
|
||||||
void __fpsimd_save_state(struct user_fpsimd_state *fp_regs);
|
void __fpsimd_save_state(struct user_fpsimd_state *fp_regs);
|
||||||
void __fpsimd_restore_state(struct user_fpsimd_state *fp_regs);
|
void __fpsimd_restore_state(struct user_fpsimd_state *fp_regs);
|
||||||
void __sve_save_state(void *sve_pffr, u32 *fpsr);
|
|
||||||
void __sve_restore_state(void *sve_pffr, u32 *fpsr);
|
void __sve_restore_state(void *sve_pffr, u32 *fpsr);
|
||||||
|
|
||||||
#ifndef __KVM_NVHE_HYPERVISOR__
|
#ifndef __KVM_NVHE_HYPERVISOR__
|
||||||
|
|
|
@ -25,9 +25,3 @@ SYM_FUNC_START(__sve_restore_state)
|
||||||
sve_load 0, x1, x2, 3
|
sve_load 0, x1, x2, 3
|
||||||
ret
|
ret
|
||||||
SYM_FUNC_END(__sve_restore_state)
|
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)
|
|
||||||
|
|
Loading…
Reference in New Issue