From: Paolo Bonzini <pbonzini@redhat.com>
To: Yu Zhang <yu.c.zhang@linux.intel.com>,
seanjc@google.com, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: VMX: Do not trap VMFUNC instructions for L1 guests.
Date: Mon, 7 Nov 2022 18:20:23 +0100 [thread overview]
Message-ID: <c8f036f4-6ab1-efbe-dd60-b934c21cb21d@redhat.com> (raw)
In-Reply-To: <20221107082727.1355797-1-yu.c.zhang@linux.intel.com>
On 11/7/22 09:27, Yu Zhang wrote:
> VMFUNC is not supported for L1 guests, and executing VMFUNC in
> L1 shall generate a #UD directly. Just disable it in secondary
> proc-based execution control for L1, instead of intercepting it
> and inject the #UD again.
>
> Signed-off-by: Yu Zhang<yu.c.zhang@linux.intel.com>
Is this for TDX or similar? The reason for a patch should be mentioned
in the commit message.
Paolo
next prev parent reply other threads:[~2022-11-07 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 8:27 Yu Zhang
2022-11-07 17:20 ` Paolo Bonzini [this message]
2022-11-07 17:36 ` Sean Christopherson
2022-11-08 10:23 ` Yu Zhang
2022-11-08 10:41 ` Yu Zhang
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=c8f036f4-6ab1-efbe-dd60-b934c21cb21d@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®