From: Binbin Wu <binbin.wu@linux.intel.com>
To: Tony Lindgren <tony.lindgren@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
seanjc@google.com, pbonzini@redhat.com,
dave.hansen@linux.intel.com, andrew.cooper3@citrix.com,
nik.borisov@suse.com, kas@kernel.org, rick.p.edgecombe@intel.com,
xiaoyao.li@intel.com, chao.gao@intel.com
Subject: Re: [PATCH v3 3/4] KVM: TDX: Filter configurable CPUID bits
Date: Tue, 1 Sep 2026 16:42:20 +0800 [thread overview]
Message-ID: <09c2f755-d822-4aac-993a-878d58c3b47b@linux.intel.com> (raw)
In-Reply-To: <apZ0X8J31bVCoc9E@tlindgre-MOBL1>
On 9/1/2026 2:44 PM, Tony Lindgren wrote:
> On Thu, Aug 27, 2026 at 11:18:36AM +0800, Binbin Wu wrote:
>> --- a/arch/x86/kvm/vmx/tdx.c
>> +++ b/arch/x86/kvm/vmx/tdx.c
> ...
>> +static u32 tdx_cfg_non_feature_mask(u32 function, u32 index, int reg)
>> {
>> - if (has_tsx(entry))
>> - clear_tsx(entry);
>> + /*
>> + * For a leaf/subleaf/register that will never be repurposed to hold
>> + * feature bits, it's safe to return TDX_CPUID_ALL_ALLOWED_MASK, i.e.
>> + * leave the TDX module's CPUID config mask intact.
>> + */
>> + switch (function) {
>> + case 1:
>> + if (reg == CPUID_EAX || reg == CPUID_EBX)
>> + return TDX_CPUID_ALL_ALLOWED_MASK;
>> + return 0;
>> + case 4:
>> + case 0x18:
>> + case 0x1f:
>> + return TDX_CPUID_ALL_ALLOWED_MASK;
>> + case 0x24:
>> + if (index == 0 && reg == CPUID_EBX)
>> + return GENMASK_U32(7, 0);
>> + return 0;
>> + case 0x80000008:
>> + if (reg == CPUID_EAX)
>> + return TDX_CPUID_ALL_ALLOWED_MASK;
>> + return 0;
>> + default:
>> + return 0;
>> + }
>> +}
>
> How about rename the above to something simpler like tdx_get_cpuid_bits()?
> Sorry I don't have anything better to suggest for naming.
>
>> +static u32 tdx_cfg_feature_mask(u32 function, u32 index, int reg)
>> +{
>> + for (int i = 0; i < NR_KVM_CPU_CAPS; i++) {
>> + const struct cpuid_reg *cpuid = &reverse_cpuid[i];
>> +
>> + if (!cpuid->function)
>> + continue;
>> +
>> + if (cpuid->function == function && cpuid->index == index &&
>> + cpuid->reg == reg)
>> + return tdx_cpu_cfg_caps[i];
>> + }
>> +
>> + return 0;
>> }
>
> And then the above to tdx_get_cpuid_feature_bits()?
>
>> -static bool tdx_unsupported_cpuid(const struct kvm_cpuid_entry2 *entry)
>> +static u32 tdx_get_allowed_cfg_cpuid_mask(u32 function, u32 index, int reg)
>> {
>> - return has_tsx(entry) || has_waitpkg(entry);
>> + u32 non_feature_mask = tdx_cfg_non_feature_mask(function, index, reg);
>> +
>> + if (non_feature_mask == TDX_CPUID_ALL_ALLOWED_MASK)
>> + return TDX_CPUID_ALL_ALLOWED_MASK;
>> +
>> + /*
>> + * It's possible that a CPUID register contains both feature and
>> + * non-feature bits.
>> + */
>> + return non_feature_mask | tdx_cfg_feature_mask(function, index, reg);
>> }
>
> And then tdx_get_cpuid_mask()?
How about:
tdx_get_cpuid_cfg_non_feature_mask()
tdx_get_cpuid_cfg_feature_mask()
tdx_get_cpuid_cfg_mask()
next prev parent reply other threads:[~2026-09-01 8:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 3:18 [PATCH v3 0/4] KVM: TDX: Validate directly configurable CPUID bits Binbin Wu
2026-08-27 3:18 ` [PATCH v3 1/4] KVM: TDX: Track configurable CPUID bits allowed by KVM Binbin Wu
2026-09-01 6:29 ` Tony Lindgren
2026-09-01 8:23 ` Binbin Wu
2026-09-01 8:27 ` Tony Lindgren
2026-08-27 3:18 ` [PATCH v3 2/4] KVM: TDX: Report CORE_CAPABILITIES as configurable Binbin Wu
2026-09-01 6:45 ` Tony Lindgren
2026-08-27 3:18 ` [PATCH v3 3/4] KVM: TDX: Filter configurable CPUID bits Binbin Wu
2026-09-01 6:44 ` Tony Lindgren
2026-09-01 8:42 ` Binbin Wu [this message]
2026-09-01 9:09 ` Tony Lindgren
2026-08-27 3:18 ` [PATCH v3 4/4] KVM: TDX: Validate userspace CPUID input for KVM_TDX_INIT_VM Binbin Wu
2026-08-27 3:24 ` sashiko-bot
2026-08-27 7:25 ` Binbin Wu
2026-09-01 6:47 ` Tony Lindgren
2026-08-27 19:33 ` [PATCH v3 0/4] KVM: TDX: Validate directly configurable CPUID bits Edgecombe, Rick P
2026-08-28 3:19 ` Binbin Wu
2026-08-28 16:58 ` Edgecombe, Rick P
2026-08-31 5:01 ` Binbin Wu
2026-09-01 9:42 ` Xiaoyao Li
2026-09-01 10:21 ` Xiaoyao Li
2026-09-01 9:38 ` Xiaoyao Li
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=09c2f755-d822-4aac-993a-878d58c3b47b@linux.intel.com \
--to=binbin.wu@linux.intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tony.lindgren@linux.intel.com \
--cc=xiaoyao.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