From: Paolo Bonzini <pbonzini@redhat.com>
To: Xin Li <xin3.li@intel.com>, qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, seanjc@google.com, chao.gao@intel.com,
hpa@zytor.com, xiaoyao.li@intel.com, weijiang.yang@intel.com
Subject: Re: [PATCH 3/4] target/i386: enumerate VMX nested-exception support
Date: Tue, 26 Sep 2023 17:37:01 +0200 [thread overview]
Message-ID: <09ed554b-ceff-4ab5-68b4-f0aa0234b4b7@redhat.com> (raw)
In-Reply-To: <20230901053022.18672-4-xin3.li@intel.com>
On 9/1/23 07:30, Xin Li wrote:
> Allow VMX nested-exception support to be exposed in KVM guests, thus
> nested KVM guests can enumerate it.
>
> Tested-by: Shan Kang <shan.kang@intel.com>
> Signed-off-by: Xin Li <xin3.li@intel.com>
> ---
> target/i386/cpu.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index 3dba6b46d9..ba579e1fb7 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -1340,6 +1340,7 @@ FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
> .feat_names = {
> [54] = "vmx-ins-outs",
> [55] = "vmx-true-ctls",
> + [58] = "vmx-nested-exception",
> },
> .msr = {
> .index = MSR_IA32_VMX_BASIC,
Please also add it to scripts/kvm/vmxcap, and rebase on top of the
recent introduction of MSR_VMX_BASIC_ANY_ERRCODE.
Paolo
next prev parent reply other threads:[~2023-09-26 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 5:30 [PATCH 0/4] target/i386: add support for FRED Xin Li
2023-09-01 5:30 ` [PATCH 1/4] target/i386: add support for FRED in CPUID enumeration Xin Li
2023-09-01 5:30 ` [PATCH 2/4] target/i386: mark CR4.FRED not reserved Xin Li
2023-09-01 5:30 ` [PATCH 3/4] target/i386: enumerate VMX nested-exception support Xin Li
2023-09-26 15:37 ` Paolo Bonzini [this message]
2023-09-01 5:30 ` [PATCH 4/4] target/i386: add live migration support for FRED Xin Li
2023-09-21 9:03 ` Yang, Weijiang
2023-09-26 6:41 ` Li, Xin3
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=09ed554b-ceff-4ab5-68b4-f0aa0234b4b7@redhat.com \
--to=pbonzini@redhat.com \
--cc=chao.gao@intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seanjc@google.com \
--cc=weijiang.yang@intel.com \
--cc=xiaoyao.li@intel.com \
--cc=xin3.li@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;
as well as URLs for NNTP newsgroup(s).