From: Paolo Bonzini <pbonzini@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>,
Sean Christopherson <seanjc@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, vkuznets@redhat.com
Subject: Re: [PATCH v2 8/9] KVM: x86: lapic does not have to process INIT if it is blocked
Date: Wed, 17 Aug 2022 17:33:16 +0200 [thread overview]
Message-ID: <20a1384f-3e05-15a0-1f27-ae7488e5d34f@redhat.com> (raw)
In-Reply-To: <226aca0a2cc95f57364f330793a2f13446fcf7a0.camel@redhat.com>
On 8/17/22 16:11, Maxim Levitsky wrote:
>
> While reviwing this, I noticed that we have this code:
>
>
> static bool svm_apic_init_signal_blocked(struct kvm_vcpu *vcpu)
> {
> struct vcpu_svm *svm = to_svm(vcpu);
>
> /*
> * TODO: Last condition latch INIT signals on vCPU when
> * vCPU is in guest-mode and vmcb12 defines intercept on INIT.
> * To properly emulate the INIT intercept,
> * svm_check_nested_events() should call nested_svm_vmexit()
> * if an INIT signal is pending.
> */
> return !gif_set(svm) ||
> (vmcb_is_intercept(&svm->vmcb->control, INTERCEPT_INIT));
> }
>
> Is this workaround still needed? svm_check_nested_events does check
> the apic's INIT/SIPI status.
>
> Currently the '.apic_init_signal_blocked' is called from
> kvm_vcpu_latch_init which itself is currently called from
> kvm_vcpu_latch_init which happens after we would vmexit if INIT is
> intercepted by nested hypervisor.
No, it shouldn't be needed anymore.
Paolo
next prev parent reply other threads:[~2022-08-17 15:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 21:05 [PATCH v2 0/9] KVM: x86: never write to memory from kvm_vcpu_check_block Paolo Bonzini
2022-08-11 21:05 ` [PATCH v2 1/9] KVM: x86: check validity of argument to KVM_SET_MP_STATE Paolo Bonzini
2022-08-15 13:31 ` Maxim Levitsky
2022-08-16 22:50 ` Sean Christopherson
2022-08-11 21:05 ` [PATCH v2 2/9] KVM: x86: remove return value of kvm_vcpu_block Paolo Bonzini
2022-08-16 23:34 ` Sean Christopherson
2022-08-17 14:10 ` Maxim Levitsky
2022-08-17 15:31 ` Paolo Bonzini
2022-08-17 16:41 ` Sean Christopherson
2022-08-17 16:49 ` Paolo Bonzini
2022-09-20 0:42 ` Sean Christopherson
2022-08-11 21:05 ` [PATCH v2 3/9] KVM: x86: make kvm_vcpu_{block,halt} return whether vCPU is runnable Paolo Bonzini
2022-08-11 21:06 ` [PATCH v2 4/9] KVM: mips, x86: do not rely on KVM_REQ_UNHALT Paolo Bonzini
2022-08-11 21:06 ` [PATCH v2 5/9] KVM: remove KVM_REQ_UNHALT Paolo Bonzini
2022-08-11 21:06 ` [PATCH v2 6/9] KVM: x86: make vendor code check for all nested events Paolo Bonzini
2022-08-16 23:47 ` Sean Christopherson
2022-08-17 14:10 ` Maxim Levitsky
2022-08-11 21:06 ` [PATCH v2 7/9] KVM: nVMX: Make an event request when pending an MTF nested VM-Exit Paolo Bonzini
2022-08-17 14:11 ` Maxim Levitsky
2022-08-11 21:06 ` [PATCH v2 8/9] KVM: x86: lapic does not have to process INIT if it is blocked Paolo Bonzini
2022-08-17 0:07 ` Sean Christopherson
2022-08-17 14:11 ` Maxim Levitsky
2022-08-17 15:33 ` Paolo Bonzini [this message]
2022-08-11 21:06 ` [PATCH v2 9/9] KVM: x86: never write to memory from kvm_vcpu_check_block Paolo Bonzini
2022-08-16 23:45 ` Sean Christopherson
2022-08-17 14:11 ` Maxim Levitsky
2022-09-20 0:32 ` Sean Christopherson
2022-09-20 0:55 ` Sean Christopherson
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=20a1384f-3e05-15a0-1f27-ae7488e5d34f@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@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®