From: linmiaohe <linmiaohe@huawei.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Wanpeng Li <wanpengli@tencent.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jim Mattson <jmattson@google.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH RFC 2/2] KVM: nVMX: handle nested posted interrupts when apicv is disabled for L1
Date: Fri, 21 Feb 2020 03:35:14 +0000 [thread overview]
Message-ID: <11a51b369e464e8e92c71cd87708e366@huawei.com> (raw)
Hi:
Vitaly Kuznetsov <vkuznets@redhat.com> write:
>Even when APICv is disabled for L1 it can (and, actually, is) still available for L2, this means we need to always call
>vmx_deliver_nested_posted_interrupt() when attempting an interrupt delivery.
>
>Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
>Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Looks good for me. Thanks.
Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
next reply other threads:[~2020-02-21 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 3:35 linmiaohe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-20 17:22 [PATCH RFC 0/2] KVM: nVMX: fix apicv disablement " Vitaly Kuznetsov
2020-02-20 17:22 ` [PATCH RFC 2/2] KVM: nVMX: handle nested posted interrupts when apicv is disabled " Vitaly Kuznetsov
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=11a51b369e464e8e92c71cd87708e366@huawei.com \
--to=linmiaohe@huawei.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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
Powered by JetHome