From: Maxim Levitsky <mlevitsk@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH RFC] KVM: nSVM: remove useless kvm_clear_*_queue
Date: Mon, 02 Aug 2021 16:10:27 +0300 [thread overview]
Message-ID: <4792fca66e009a5164a178765c6eb32da7d7d3e7.camel@redhat.com> (raw)
In-Reply-To: <20210802125634.309874-1-pbonzini@redhat.com>
On Mon, 2021-08-02 at 08:56 -0400, Paolo Bonzini wrote:
> For an event to be in injected state when nested_svm_vmrun executes,
> it must have come from exitintinfo when svm_complete_interrupts ran:
>
> vcpu_enter_guest
> static_call(kvm_x86_run) -> svm_vcpu_run
> svm_complete_interrupts
> // now the event went from "exitintinfo" to "injected"
> static_call(kvm_x86_handle_exit) -> handle_exit
> svm_invoke_exit_handler
> vmrun_interception
> nested_svm_vmrun
>
> However, no event could have been in exitintinfo before a VMRUN
> vmexit. The code in svm.c is a bit more permissive than the one
> in vmx.c:
>
> if (is_external_interrupt(svm->vmcb->control.exit_int_info) &&
> exit_code != SVM_EXIT_EXCP_BASE + PF_VECTOR &&
> exit_code != SVM_EXIT_NPF && exit_code != SVM_EXIT_TASK_SWITCH &&
> exit_code != SVM_EXIT_INTR && exit_code != SVM_EXIT_NMI)
>
> but in any case, a VMRUN instruction would not even start to execute
> during an attempted event delivery.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> arch/x86/kvm/svm/nested.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/nested.c b/arch/x86/kvm/svm/nested.c
> index 61738ff8ef33..5e13357da21e 100644
> --- a/arch/x86/kvm/svm/nested.c
> +++ b/arch/x86/kvm/svm/nested.c
> @@ -659,11 +659,6 @@ int nested_svm_vmrun(struct kvm_vcpu *vcpu)
> goto out;
> }
>
> -
> - /* Clear internal status */
> - kvm_clear_exception_queue(vcpu);
> - kvm_clear_interrupt_queue(vcpu);
> -
> /*
> * Since vmcb01 is not in use, we can use it to store some of the L1
> * state.
100% agree.
As I say, Intel's architects weren't crazy enough to implement an VM IDT gate
(switch to a VM on interrupt....), and so indeed that this isn't possible.
They do have a task gate... thankfully it is legacy.
I would still keep a WARN_ON_ONCE here just in case.
Note that in theory one can force an injected/queued exception with KVM_SET_VCPU_EVENTS
on RIP that points to VMRUN instruction. Its user fault though.
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2021-08-02 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 12:56 Paolo Bonzini
2021-08-02 13:10 ` Maxim Levitsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4792fca66e009a5164a178765c6eb32da7d7d3e7.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®