summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2020-01-18 22:29:46 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2020-01-27 19:59:46 +0100
commit3911b65ee1d3e3fc5e3786b1f309dcad0e33f7fd (patch)
treedbb4c2c3538ee0f71a621f0439359fe5e96b6912
parent3ce4dc17e0c1e7280d53abeb85ce851a88868c63 (diff)
Revert "KVM: x86: Add a WARN on TIF_NEED_FPU_LOAD in kvm_load_guest_fpu()"
This reverts commit 95145c25a78cc0a9d3cbc75708abde432310c5a1. The next few patches will fix the issue so the warning is not needed anymore; revert it separately to simplify application to stable kernels. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
-rw-r--r--arch/x86/kvm/x86.c7
1 files changed, 0 insertions, 7 deletions
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 2b26400a3410..603a1f778dbe 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -8563,13 +8563,6 @@ static void kvm_load_guest_fpu(struct kvm_vcpu *vcpu)
{
fpregs_lock();
- /*
- * Reloading userspace's FPU is handled by kvm_arch_vcpu_load(), both
- * for direct calls from userspace (via vcpu_load()) and if this task
- * is preempted (via kvm_sched_in()) between vcpu_load() and now.
- */
- WARN_ON_ONCE(test_thread_flag(TIF_NEED_FPU_LOAD));
-
copy_fpregs_to_fpstate(vcpu->arch.user_fpu);
/* PKRU is separately restored in kvm_x86_ops->run. */
__copy_kernel_to_fpregs(&vcpu->arch.guest_fpu->state,