From: Chao Gao <chao.gao@intel.com>
To: Binbin Wu <binbin.wu@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>,
<tony.lindgren@linux.intel.com>, <kishen.maloor@intel.com>,
<dedekind1@gmail.com>, <adrian.hunter@intel.com>
Subject: Re: [PATCH v5 3/5] KVM: TDX: Add CORE_CAPABILITIES to the allowlist
Date: Fri, 23 Oct 2026 11:25:02 +0800 [thread overview]
Message-ID: <atrTjltXoQ6EAyTO@intel.com> (raw)
In-Reply-To: <20261016091422.3182216-4-binbin.wu@linux.intel.com>
On Fri, Oct 16, 2026 at 05:14:20PM +0800, Binbin Wu wrote:
>Add CORE_CAPABILITIES (CPUID.0x7.0.EDX[30]) to KVM's allowlist of TDX
>directly configurable CPUID feature bits to accommodate the legacy TDX
>module definition of the bit, even though KVM doesn't support
>MSR_IA32_CORE_CAPS for TDs.
>
>Older TDX module specs define CORE_CAPABILITIES as fixed-1, so userspace
>may expect the bit to be set for TDs. The bit is redefined as directly
>configurable due to #VE reduction. Leaving it out of the allowlist would
>prevent userspace from setting it once KVM starts validating the CPUID
>input to KVM_TDX_INIT_VM, which would be an unexpected behavior change for
>such userspace.
>
>Reporting CORE_CAPABILITIES as directly configurable also lets userspace
>detect that the bit is no longer fixed-1, and thus update its stale
>knowledge.
>
>Keep MSR_IA32_CORE_CAPS unsupported for TDs, as no existing TDX user needs
>guest access to the MSR.
>
>Note, CORE_CAPABILITIES is the only bit that is both unsupported by KVM
>*and* redefined from fixed-1 to directly configurable due to #VE
>reduction, and no further #VE reductions are expected.
>
>Signed-off-by: Binbin Wu <binbin.wu@linux.intel.com>
>Reviewed-by: Tony Lindgren <tony.lindgren@linux.intel.com>
>Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
Reviewed-by: Chao Gao <chao.gao@intel.com>
next prev parent reply other threads:[~2026-10-23 3:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:14 [PATCH v5 0/5] KVM: TDX: Validate directly configurable CPUID bits Binbin Wu
2026-10-16 9:14 ` [PATCH v5 1/5] KVM: TDX: Check unsupported CPUID bits against the TDX module's subleaf Binbin Wu
2026-10-16 15:25 ` Sean Christopherson
2026-10-16 22:15 ` Binbin Wu
2026-10-16 23:26 ` Sean Christopherson
2026-10-16 9:14 ` [PATCH v5 2/5] KVM: TDX: Track configurable CPUID bits allowed by KVM Binbin Wu
2026-10-23 3:24 ` Chao Gao
2026-10-23 7:35 ` Xiaoyao Li
2026-10-26 7:18 ` Nikolay Borisov
2026-10-16 9:14 ` [PATCH v5 3/5] KVM: TDX: Add CORE_CAPABILITIES to the allowlist Binbin Wu
2026-10-23 3:25 ` Chao Gao [this message]
2026-10-26 7:19 ` Nikolay Borisov
2026-10-16 9:14 ` [PATCH v5 4/5] KVM: TDX: Report only KVM-allowed CPUIDs in KVM_TDX_CAPABILITIES Binbin Wu
2026-10-21 0:39 ` Edgecombe, Rick P
2026-10-21 2:15 ` Binbin Wu
2026-10-21 17:19 ` Edgecombe, Rick P
2026-10-22 2:20 ` Binbin Wu
2026-10-23 7:42 ` Xiaoyao Li
2026-10-23 3:27 ` Chao Gao
2026-10-16 9:14 ` [PATCH v5 5/5] KVM: TDX: Validate userspace CPUID input for KVM_TDX_INIT_VM Binbin Wu
2026-10-16 9:24 ` sashiko-bot
2026-10-20 1:34 ` Binbin Wu
2026-10-23 3:37 ` Chao Gao
2026-10-23 7:46 ` Xiaoyao Li
2026-10-23 7:48 ` Binbin Wu
2026-10-21 0:59 ` [PATCH v5 0/5] KVM: TDX: Validate directly configurable CPUID bits Edgecombe, Rick P
2026-10-21 17:43 ` Nikolay Borisov
2026-10-27 3:17 ` Binbin Wu
2026-10-27 6:46 ` Nikolay Borisov
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=atrTjltXoQ6EAyTO@intel.com \
--to=chao.gao@intel.com \
--cc=adrian.hunter@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=binbin.wu@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dedekind1@gmail.com \
--cc=kas@kernel.org \
--cc=kishen.maloor@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.