From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Tao Xu <tao3.xu@intel.com>, Andy Lutomirski <luto@amacapital.net>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Christopherson, Sean J" <sean.j.christopherson@intel.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, X86 ML <x86@kernel.org>,
kvm list <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: VMX: Enable Notify VM exit
Date: Tue, 3 Nov 2020 15:29:33 +0800 [thread overview]
Message-ID: <a7c8cdeb-c5be-a00f-eb2f-fcc8762c07b2@intel.com> (raw)
In-Reply-To: <a5f500ee-51f8-54a7-d927-0e8eee644e26@intel.com>
On 11/3/2020 2:08 PM, Tao Xu wrote:
>
>
> On 11/3/20 12:43 AM, Andy Lutomirski wrote:
>> On Sun, Nov 1, 2020 at 10:14 PM Tao Xu <tao3.xu@intel.com> wrote:
>>>
...
>>
>>> +static int handle_notify(struct kvm_vcpu *vcpu)
>>> +{
>>> + unsigned long exit_qualification =
>>> vmcs_readl(EXIT_QUALIFICATION);
>>> +
>>> + /*
>>> + * Notify VM exit happened while executing iret from NMI,
>>> + * "blocked by NMI" bit has to be set before next VM entry.
>>> + */
>>> + if (exit_qualification & NOTIFY_VM_CONTEXT_VALID) {
>>> + if (enable_vnmi &&
>>> + (exit_qualification & INTR_INFO_UNBLOCK_NMI))
>>> + vmcs_set_bits(GUEST_INTERRUPTIBILITY_INFO,
>>> + GUEST_INTR_STATE_NMI);
>>
>> This needs actual documentation in the SDM or at least ISE please.
>>
Hi Andy,
Do you mean SDM or ISE should call out it needs to restore "blocked by
NMI" if bit 12 of exit qualification is set and VMM decides to re-enter
the guest?
you can refer to SDM 27.2.3 "Information about NMI unblocking Due to
IRET" in latest SDM 325462-072US
> Notify VM-Exit is defined in ISE, chapter 9.2:
> https://software.intel.com/content/dam/develop/external/us/en/documents/architecture-instruction-set-extensions-programming-reference.pdf
>
>
> I will add this information into commit message. Thank you for reminding
> me.
next prev parent reply other threads:[~2020-11-03 7:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 6:14 [PATCH] KVM: VMX: Enable Notify VM exit Tao Xu
2020-11-02 16:43 ` Andy Lutomirski
2020-11-02 17:31 ` Sean Christopherson
2020-11-02 18:01 ` Andy Lutomirski
2020-11-02 18:25 ` Paolo Bonzini
2020-11-03 6:39 ` Xiaoyao Li
2020-11-02 18:33 ` Sean Christopherson
2021-05-17 7:20 ` Xiaoyao Li
2021-05-17 8:55 ` Xiaoyao Li
2020-11-03 5:35 ` Tao Xu
2020-11-03 6:08 ` Tao Xu
2020-11-03 7:29 ` Xiaoyao Li [this message]
2020-11-02 17:32 ` Sean Christopherson
2020-11-03 5:36 ` Tao Xu
2020-11-02 22:53 ` Jim Mattson
2020-11-03 6:12 ` Tao Xu
2020-11-03 6:24 ` Xiaoyao Li
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=a7c8cdeb-c5be-a00f-eb2f-fcc8762c07b2@intel.com \
--to=xiaoyao.li@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tao3.xu@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).