From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Li <ercli@ucdavis.edu>
Subject: Re: [PATCH] KVM: nVMX: Inject #GP, not #UD, if "generic" VMXON CR0/CR4 check fails
Date: Thu, 6 Oct 2022 00:21:27 +0000 [thread overview]
Message-ID: <Yz4fhz3UBJGwOuvN@google.com> (raw)
In-Reply-To: <20221006001956.329314-1-seanjc@google.com>
On Thu, Oct 06, 2022, Sean Christopherson wrote:
> + * Forwarding the VM-Exit unconditionally, i.e. without performing the
> + * #UD checks (see above), is functionally ok because KVM doesn't allow
> + * L1 to run L2 without CR4.VMXE=0, and because KVM never modifies L2's
> + * CR0 or CR4, i.e. it's L2's responsibility to emulate #UDs that are
Grr, s/L2's/L1's. Fixed the comment locally but didn't commit it before hitting "send".
next prev parent reply other threads:[~2022-10-06 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 0:19 [PATCH] KVM: nVMX: Inject #GP, not #UD, if "generic" VMXON CR0/CR4 check fails Sean Christopherson
2022-10-06 0:21 ` Sean Christopherson [this message]
[not found] ` <783d89e3c98ee933ec789f1bffc6873ac3ac2e7a.camel@ucdavis.edu>
2022-10-06 15:23 ` 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=Yz4fhz3UBJGwOuvN@google.com \
--to=seanjc@google.com \
--cc=ercli@ucdavis.edu \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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