From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Jim Mattson <jmattson@google.com>, Chenyi Qiang <chenyi.qiang@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] KVM: VMX: Enable Notify VM exit
Date: Fri, 25 Feb 2022 23:12:12 +0800 [thread overview]
Message-ID: <6a839b88-392d-886d-836d-ca04cf700dce@intel.com> (raw)
In-Reply-To: <88eb9a9a-fbe3-8e2c-02bd-4bdfc855b67f@intel.com>
On 2/25/2022 11:04 PM, Xiaoyao Li wrote:
> On 2/25/2022 10:54 PM, Jim Mattson wrote:
>> On Tue, Feb 22, 2022 at 10:19 PM Chenyi Qiang <chenyi.qiang@intel.com>
>> wrote:
>>> Nested handling
>>> - Nested notify VM exits are not supported yet. Keep the same notify
>>> window control in vmcs02 as vmcs01, so that L1 can't escape the
>>> restriction of notify VM exits through launching L2 VM.
>>> - When L2 VM is context invalid, synthesize a nested
>>> EXIT_REASON_TRIPLE_FAULT to L1 so that L1 won't be killed due to L2's
>>> VM_CONTEXT_INVALID happens.
>>
>> I don't like the idea of making things up without notifying userspace
>> that this is fictional. How is my customer running nested VMs supposed
>> to know that L2 didn't actually shutdown, but L0 killed it because the
>> notify window was exceeded? If this information isn't reported to
>> userspace, I have no way of getting the information to the customer.
>
> Then, maybe a dedicated software define VM exit for it instead of
> reusing triple fault?
>
Second thought, we can even just return Notify VM exit to L1 to tell L2
causes Notify VM exit, even thought Notify VM exit is not exposed to L1.
next prev parent reply other threads:[~2022-02-25 15:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 6:24 [PATCH v3] KVM: VMX: Enable Notify VM exit Chenyi Qiang
2022-02-25 11:54 ` Paolo Bonzini
2022-02-25 12:46 ` Xiaoyao Li
2022-02-25 14:54 ` Jim Mattson
2022-02-25 15:04 ` Xiaoyao Li
2022-02-25 15:12 ` Xiaoyao Li [this message]
2022-02-25 15:13 ` Paolo Bonzini
2022-02-25 18:06 ` Jim Mattson
2022-02-25 18:29 ` Sean Christopherson
2022-02-25 19:15 ` Jim Mattson
2022-02-26 4:07 ` Xiaoyao Li
2022-02-26 4:25 ` Jim Mattson
2022-02-26 4:53 ` Jim Mattson
2022-02-26 6:24 ` Xiaoyao Li
2022-02-26 14:24 ` Jim Mattson
2022-02-28 7:10 ` Xiaoyao Li
2022-02-28 14:30 ` Jim Mattson
2022-03-01 1:40 ` Xiaoyao Li
2022-03-01 4:32 ` Jim Mattson
2022-03-01 5:30 ` Xiaoyao Li
2022-03-01 21:57 ` Jim Mattson
2022-03-02 2:15 ` Chenyi Qiang
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=6a839b88-392d-886d-836d-ca04cf700dce@intel.com \
--to=xiaoyao.li@intel.com \
--cc=chenyi.qiang@intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.