From: Chao Gao <chao.gao@intel.com>
To: Xin Li <xin3.li@intel.com>
Cc: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
<seanjc@google.com>, <pbonzini@redhat.com>, <tglx@linutronix.de>,
<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
<x86@kernel.org>, <hpa@zytor.com>, <weijiang.yang@intel.com>,
<kai.huang@intel.com>
Subject: Re: [PATCH v4 1/2] KVM: VMX: Cleanup VMX basic information defines and usages
Date: Tue, 16 Jan 2024 15:46:25 +0800 [thread overview]
Message-ID: <ZaY0UbFjwCYh4u/r@chao-email> (raw)
In-Reply-To: <20240112093449.88583-1-xin3.li@intel.com>
On Fri, Jan 12, 2024 at 01:34:48AM -0800, Xin Li wrote:
>
>+#define VMX_BASIC_DUAL_MONITOR_TREATMENT BIT_ULL(49)
>+#define VMX_BASIC_TRUE_CTLS BIT_ULL(55)
>+
>+#define VMX_BASIC_FEATURES_MASK \
>+ (VMX_BASIC_DUAL_MONITOR_TREATMENT | \
>+ VMX_BASIC_INOUT | \
>+ VMX_BASIC_TRUE_CTLS)
>+
>+#define VMX_BASIC_RESERVED_BITS \
>+ (GENMASK_ULL(63, 56) | GENMASK_ULL(47, 45) | BIT_ULL(31))
When we add a new feature (e.g., in CET series, bit 56 is added), the above
two macros need to be modified.
Would it be better to use a macro for bits exempt from the bitwise check below
e.g.,
#define VMX_BASIC_MULTI_BITS_FEATURES_MASK
(GENMASK_ULL(53, 50) | GENMASK_ULL(44, 32) | GENMASK_ULL(30, 0))
and do
if (!is_bitwise_subset(vmx_basic, data,
~VMX_BASIC_MULTI_BITS_FEATURES_MASK)
then we don't need to change the macro when adding new features.
>+
> static int vmx_restore_vmx_basic(struct vcpu_vmx *vmx, u64 data)
> {
>- const u64 feature_and_reserved =
>- /* feature (except bit 48; see below) */
>- BIT_ULL(49) | BIT_ULL(54) | BIT_ULL(55) |
>- /* reserved */
>- BIT_ULL(31) | GENMASK_ULL(47, 45) | GENMASK_ULL(63, 56);
> u64 vmx_basic = vmcs_config.nested.basic;
>
>- if (!is_bitwise_subset(vmx_basic, data, feature_and_reserved))
>+ static_assert(!(VMX_BASIC_FEATURES_MASK & VMX_BASIC_RESERVED_BITS));
>+
>+ if (!is_bitwise_subset(vmx_basic, data,
>+ VMX_BASIC_FEATURES_MASK | VMX_BASIC_RESERVED_BITS))
> return -EINVAL;
>
> /*
> * KVM does not emulate a version of VMX that constrains physical
> * addresses of VMX structures (e.g. VMCS) to 32-bits.
> */
>- if (data & BIT_ULL(48))
>+ if (data & VMX_BASIC_32BIT_PHYS_ADDR_ONLY)
> return -EINVAL;
Side topic:
Actually, there is no need to handle bit 48 as a special case. If we add bit 48
to VMX_BASIC_FEATURES_MASK, the bitwise check will fail if bit 48 of @data is 1.
next prev parent reply other threads:[~2024-01-16 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 9:34 [PATCH v4 1/2] KVM: VMX: Cleanup VMX basic information defines and usages Xin Li
2024-01-12 9:34 ` [PATCH v4 2/2] KVM: VMX: Cleanup VMX misc " Xin Li
2024-01-15 11:46 ` [PATCH v4 1/2] KVM: VMX: Cleanup VMX basic " Huang, Kai
2024-01-16 4:13 ` Li, Xin3
2024-01-16 7:46 ` Chao Gao [this message]
2024-01-17 16:34 ` Li, Xin3
2024-01-18 3:08 ` Huang, Kai
2024-01-18 5:15 ` Li, Xin3
2024-01-18 3:13 ` Huang, Kai
2024-01-18 5:16 ` 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=ZaY0UbFjwCYh4u/r@chao-email \
--to=chao.gao@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=weijiang.yang@intel.com \
--cc=x86@kernel.org \
--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