From: Sean Christopherson <seanjc@google.com>
To: Robert Hoo <robert.hu@linux.intel.com>
Cc: pbonzini@redhat.com, vkuznets@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org, kvm@vger.kernel.org,
yu.c.zhang@linux.intel.com
Subject: Re: [PATCH v1 3/5] KVM: x86: nVMX: VMCS12 field's read/write respects field existence bitmap
Date: Tue, 5 Oct 2021 16:15:53 +0000 [thread overview]
Message-ID: <YVx6Oesi7X3jfnaM@google.com> (raw)
In-Reply-To: <64aad01b6bffd70fa3170cf262fe5d7c66f6b2d4.camel@linux.intel.com>
On Tue, Sep 28, 2021, Robert Hoo wrote:
> On Fri, 2021-09-03 at 15:11 +0000, Sean Christopherson wrote:
> You also said, "This is quite the complicated mess for
> something I'm guessing no one actually cares about. At what point do
> we chalk this up as a virtualization hole and sweep it under the rug?"
> -- I couldn't agree more.
...
> So, Sean, can you help converge our discussion and settle next step?
Any objection to simply keeping KVM's current behavior, i.e. sweeping this under
the proverbial rug?
next prev parent reply other threads:[~2021-10-05 16:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 9:31 [PATCH v1 0/5] KVM/x86/nVMX: Add field existence support in VMCS12 Robert Hoo
2021-08-17 9:31 ` [PATCH v1 1/5] KVM: x86: nVMX: Add vmcs12 field existence bitmap in nested_vmx Robert Hoo
2021-10-20 15:10 ` Paolo Bonzini
2021-10-21 12:41 ` Robert Hoo
2021-08-17 9:31 ` [PATCH v1 2/5] KVM: x86: nVMX: Update VMCS12 fields existence when nVMX MSRs are set Robert Hoo
2021-10-20 15:11 ` Paolo Bonzini
2021-10-21 13:08 ` Robert Hoo
2021-08-17 9:31 ` [PATCH v1 3/5] KVM: x86: nVMX: VMCS12 field's read/write respects field existence bitmap Robert Hoo
2021-08-17 15:54 ` Sean Christopherson
2021-08-18 5:50 ` Robert Hoo
2021-08-18 23:10 ` Sean Christopherson
2021-08-18 23:45 ` Jim Mattson
2021-08-18 23:49 ` Sean Christopherson
2021-08-19 9:58 ` Robert Hoo
2021-09-01 20:42 ` Sean Christopherson
2021-09-03 8:51 ` Robert Hoo
2021-09-03 15:11 ` Sean Christopherson
2021-09-28 10:05 ` Robert Hoo
2021-10-05 16:15 ` Sean Christopherson [this message]
2021-10-05 17:32 ` Jim Mattson
2021-10-05 17:59 ` Sean Christopherson
2021-10-05 20:42 ` Jim Mattson
2021-10-05 20:50 ` Sean Christopherson
2021-10-05 22:40 ` Jim Mattson
2021-10-05 23:22 ` Sean Christopherson
2021-10-08 8:23 ` Yu Zhang
2021-10-08 15:09 ` Robert Hoo
2021-10-08 23:49 ` Jim Mattson
2021-10-09 0:05 ` Robert Hoo
2021-10-29 19:53 ` Jim Mattson
2021-11-03 1:31 ` Robert Hoo
2021-11-09 22:33 ` Sean Christopherson
2021-11-10 5:35 ` Yu Zhang
2021-11-18 1:19 ` Sean Christopherson
2021-11-19 7:32 ` Robert Hoo
2021-08-17 9:31 ` [PATCH v1 4/5] KVM: x86: nVMX: Respect vmcs12 field existence when calc vmx_vmcs_enum_msr Robert Hoo
2021-08-17 9:31 ` [PATCH v1 5/5] KVM: x86: nVMX: Ignore user space set value to MSR_IA32_VMX_VMCS_ENUM Robert Hoo
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=YVx6Oesi7X3jfnaM@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=robert.hu@linux.intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=yu.c.zhang@linux.intel.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.