KVM: SVM: immediately inject INTR vmexit
We can immediately leave SVM guest mode in svm_check_nested_events now that we have the nested_run_pending mechanism. This makes things easier because we can run the rest of inject_pending_event with GIF=0, and KVM will naturally end up requesting the next interrupt window. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
parent
38c0b192bd
commit
6e085cbfb0
@ -801,13 +801,13 @@ int nested_svm_check_exception(struct vcpu_svm *svm, unsigned nr,
|
||||
|
||||
static void nested_svm_intr(struct vcpu_svm *svm)
|
||||
{
|
||||
trace_kvm_nested_intr_vmexit(svm->vmcb->save.rip);
|
||||
|
||||
svm->vmcb->control.exit_code = SVM_EXIT_INTR;
|
||||
svm->vmcb->control.exit_info_1 = 0;
|
||||
svm->vmcb->control.exit_info_2 = 0;
|
||||
|
||||
/* nested_svm_vmexit this gets called afterwards from handle_exit */
|
||||
svm->nested.exit_required = true;
|
||||
trace_kvm_nested_intr_vmexit(svm->vmcb->save.rip);
|
||||
nested_svm_vmexit(svm);
|
||||
}
|
||||
|
||||
static bool nested_exit_on_intr(struct vcpu_svm *svm)
|
||||
|
Loading…
x
Reference in New Issue
Block a user