From: Yu Zhang <yu.c.zhang@linux.intel.com>
To: pbonzini@redhat.com, seanjc@google.com, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Cleanup VMFUNC handling in KVM.
Date: Wed, 9 Nov 2022 15:54:11 +0800 [thread overview]
Message-ID: <20221109075413.1405803-1-yu.c.zhang@linux.intel.com> (raw)
Since VMFUNC is not supported for non-nested guests, and executing VMFUNC
can cause a #UD directly, if the “enable VM functions” VM-execution control
is 0, KVM can just disable it in VM-exectution control, instead of taking
pains to trap it and emulate the #UD for L1 guests.
Also, simplified the process of setting SECONDARY_EXEC_ENABLE_VMFUNC for
nested VMX MSR configurations.
Change log:
==========
v1->v2
- Split the patch into two pieces.
- Use KVM_BUG_ON() for unexpected VM Exits.
- Comments changes.
- Commit message changes, trying to better illustrate the reason.
Yu Zhang (2):
KVM: VMX: Do not trap VMFUNC instructions for L1 guests.
KVM: nVMX: Simplify the setting of SECONDARY_EXEC_ENABLE_VMFUNC for
nested.
arch/x86/kvm/vmx/nested.c | 26 ++++++++++----------------
arch/x86/kvm/vmx/vmx.c | 7 ++++++-
2 files changed, 16 insertions(+), 17 deletions(-)
--
2.17.1
next reply other threads:[~2022-11-09 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 7:54 Yu Zhang [this message]
2022-11-09 7:54 ` [PATCH v2 1/2] KVM: VMX: Do not trap VMFUNC instructions for L1 guests Yu Zhang
2022-11-09 7:54 ` [PATCH v2 2/2] KVM: nVMX: Simplify the setting of SECONDARY_EXEC_ENABLE_VMFUNC for nested Yu Zhang
2022-11-17 9:55 ` [PATCH v2 0/2] Cleanup VMFUNC handling in KVM Yu Zhang
2023-02-08 2:02 ` Sean Christopherson
2023-02-08 6:28 ` 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=20221109075413.1405803-1-yu.c.zhang@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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