From: Chao Gao <chao.gao@intel.com>
To: Xu Yilun <yilun.xu@linux.intel.com>
Cc: <x86@kernel.org>, <linux-coco@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <kas@kernel.org>,
<rick.p.edgecombe@intel.com>, <yilun.xu@intel.com>,
<xiaoyao.li@intel.com>, <sohil.mehta@intel.com>,
<adrian.hunter@intel.com>, <kishen.maloor@intel.com>,
<tony.lindgren@linux.intel.com>, <peter.fang@intel.com>,
<baolu.lu@linux.intel.com>, <zhenzhong.duan@intel.com>,
<artem.bityutskiy@linux.intel.com>, <kvm@vger.kernel.org>,
<nik.borisov@suse.com>
Subject: Re: [PATCH v2 2/5] x86/virt/tdx: Configure add-on features on TDX module init
Date: Wed, 16 Sep 2026 11:23:21 +0800 [thread overview]
Message-ID: <aqoLqXyeXUFkvnxF@intel.com> (raw)
In-Reply-To: <20260915102658.713079-3-yilun.xu@linux.intel.com>
On Tue, Sep 15, 2026 at 06:26:55PM +0800, Xu Yilun wrote:
>The TDX architecture identifies some features that are off by default
>but can be enabled by the host during TDX module initialization. They
>are classified as add-on features because enabling them affects existing
>TDX systems: they may change existing feature behavior, or reserve more
>memory.
>
>The TDX module extends TDH.SYS.CONFIG with a new register argument to
>specify which add-on features to enable. This new argument is a bitmap
>that uses the same feature bits as TDX_FEATURES0. Note that Dynamic PAMT
>is an exception: although it is an add-on feature, it is controlled via
>a legacy, dedicated register argument [1].
>
>The kernel needs to enable these add-on features when it supports them.
>Add a get_tdx_addon_features0() helper to return the bitmap of the add-on
>features that the module & kernel both support. Initially, this helper
>returns 0. It will be updated to return specific feature bits as full
>kernel support lands. Pass this extra bitmap to TDH.SYS.CONFIG wrapper.
The last sentence is stale: the bitmap is no longer passed to the wrapper.
next prev parent reply other threads:[~2026-09-16 3:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 10:26 [PATCH v2 0/5] Enable TDX module extensions Xu Yilun
2026-09-15 10:26 ` [PATCH v2 1/5] x86/virt/tdx: Move TDH.SYS.CONFIG operations into a wrapper Xu Yilun
2026-09-15 20:45 ` Edgecombe, Rick P
2026-09-15 10:26 ` [PATCH v2 2/5] x86/virt/tdx: Configure add-on features on TDX module init Xu Yilun
2026-09-15 20:54 ` Edgecombe, Rick P
2026-09-16 3:23 ` Chao Gao [this message]
2026-09-15 10:26 ` [PATCH v2 3/5] x86/virt/tdx: Detect if the extensions initialization is required Xu Yilun
2026-09-15 21:14 ` Edgecombe, Rick P
2026-09-15 10:26 ` [PATCH v2 4/5] x86/virt/tdx: Add extra memory to TDX module for the extensions Xu Yilun
2026-09-15 21:19 ` Edgecombe, Rick P
2026-09-16 7:40 ` Chao Gao
2026-09-15 10:26 ` [PATCH v2 5/5] x86/virt/tdx: Make TDX module initialize " Xu Yilun
2026-09-15 22:09 ` [PATCH v2 0/5] Enable TDX module extensions Edgecombe, Rick P
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=aqoLqXyeXUFkvnxF@intel.com \
--to=chao.gao@intel.com \
--cc=adrian.hunter@intel.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=kas@kernel.org \
--cc=kishen.maloor@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=peter.fang@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sohil.mehta@intel.com \
--cc=tony.lindgren@linux.intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=yilun.xu@intel.com \
--cc=yilun.xu@linux.intel.com \
--cc=zhenzhong.duan@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
all inboxes | Powered by JetHome®