From: Chenyi Qiang <chenyi.qiang@intel.com>
To: Kai Huang <kai.huang@intel.com>, <dave.hansen@intel.com>,
<kirill.shutemov@linux.intel.com>, <bp@alien8.de>,
<tglx@linutronix.de>, <peterz@infradead.org>, <mingo@redhat.com>,
<hpa@zytor.com>, <seanjc@google.com>, <pbonzini@redhat.com>,
<dan.j.williams@intel.com>
Cc: <x86@kernel.org>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <rick.p.edgecombe@intel.com>,
<isaku.yamahata@intel.com>, <chao.gao@intel.com>,
<binbin.wu@linux.intel.com>
Subject: Re: [PATCH v2 08/10] x86/virt/tdx: Print TDX module basic information
Date: Thu, 8 Aug 2024 18:31:31 +0800 [thread overview]
Message-ID: <0e36f025-9a8f-4f75-af4b-bc6252c29abe@intel.com> (raw)
In-Reply-To: <1e71406eec47ae7f6a47f8be3beab18c766ff5a7.1721186590.git.kai.huang@intel.com>
On 7/17/2024 11:40 AM, Kai Huang wrote:
> Currently the kernel doesn't print any information regarding the TDX
> module itself, e.g. module version. In practice such information is
> useful, especially to the developers.
>
> For instance, there are a couple of use cases for dumping module basic
> information:
>
> 1) When something goes wrong around using TDX, the information like TDX
> module version, supported features etc could be helpful [1][2].
>
> 2) For Linux, when the user wants to update the TDX module, one needs to
> replace the old module in a specific location in the EFI partition
> with the new one so that after reboot the BIOS can load it. However,
> after kernel boots, currently the user has no way to verify it is
> indeed the new module that gets loaded and initialized (e.g., error
> could happen when replacing the old module). With the module version
> dumped the user can verify this easily.
>
> So dump the basic TDX module information:
>
> - TDX module version, and the build date.
> - TDX module type: Debug or Production.
> - TDX_FEATURES0: Supported TDX features.
>
> And dump the information right after reading global metadata, so that
> this information is printed no matter whether module initialization
> fails or not.
>
> The actual dmesg will look like:
>
> virt/tdx: Initializing TDX module: 1.5.00.00.0481 (build_date 20230323, Production module), TDX_FEATURES0 0xfbf
>
> Link: https://lore.kernel.org/lkml/e2d844ad-182a-4fc0-a06a-d609c9cbef74@suse.com/T/#m352829aedf6680d4628c7e40dc40b332eda93355 [1]
> Link: https://lore.kernel.org/lkml/e2d844ad-182a-4fc0-a06a-d609c9cbef74@suse.com/T/#m351ebcbc006d2e5bc3e7650206a087cb2708d451 [2]
> Signed-off-by: Kai Huang <kai.huang@intel.com>
> ---
>
> v1 -> v2 (Nikolay):
> - Change the format to dump TDX basic info.
> - Slightly improve changelog.
>
> ---
> arch/x86/virt/vmx/tdx/tdx.c | 64 +++++++++++++++++++++++++++++++++++++
> arch/x86/virt/vmx/tdx/tdx.h | 33 ++++++++++++++++++-
> 2 files changed, 96 insertions(+), 1 deletion(-)
>
[...]
> diff --git a/arch/x86/virt/vmx/tdx/tdx.h b/arch/x86/virt/vmx/tdx/tdx.h
> index b5eb7c35f1dc..861ddf2c2e88 100644
> --- a/arch/x86/virt/vmx/tdx/tdx.h
> +++ b/arch/x86/virt/vmx/tdx/tdx.h
> @@ -31,6 +31,15 @@
> *
> * See the "global_metadata.json" in the "TDX 1.5 ABI definitions".
> */
> +#define MD_FIELD_ID_SYS_ATTRIBUTES 0x0A00000200000000ULL
> +#define MD_FIELD_ID_TDX_FEATURES0 0x0A00000300000008ULL
> +#define MD_FIELD_ID_BUILD_DATE 0x8800000200000001ULL
> +#define MD_FIELD_ID_BUILD_NUM 0x8800000100000002ULL
> +#define MD_FIELD_ID_MINOR_VERSION 0x0800000100000003ULL
> +#define MD_FIELD_ID_MAJOR_VERSION 0x0800000100000004ULL
> +#define MD_FIELD_ID_UPDATE_VERSION 0x0800000100000005ULL
> +#define MD_FIELD_ID_INTERNAL_VERSION 0x0800000100000006ULL
> +
> #define MD_FIELD_ID_MAX_TDMRS 0x9100000100000008ULL
> #define MD_FIELD_ID_MAX_RESERVED_PER_TDMR 0x9100000100000009ULL
> #define MD_FIELD_ID_PAMT_4K_ENTRY_SIZE 0x9100000100000010ULL
> @@ -124,8 +133,28 @@ struct tdmr_info_list {
> *
> * Note not all metadata fields in each class are defined, only those
> * used by the kernel are.
> + *
> + * Also note the "bit definitions" are architectural.
> */
>
> +/* Class "TDX Module Info" */
> +struct tdx_sysinfo_module_info {
> + u32 sys_attributes;
> + u64 tdx_features0;
> +};
> +
> +#define TDX_SYS_ATTR_DEBUG_MODULE 0x1
One minor issue, TDX_SYS_ATTR_DEBUG_MODULE is indicated by bit 31 of
sys_attributes.
> +
> +/* Class "TDX Module Version" */
> +struct tdx_sysinfo_module_version {
> + u16 major;
> + u16 minor;
> + u16 update;
> + u16 internal;
> + u16 build_num;
> + u32 build_date;
> +};
> +
> /* Class "TDMR Info" */
> struct tdx_sysinfo_tdmr_info {
> u16 max_tdmrs;
> @@ -134,7 +163,9 @@ struct tdx_sysinfo_tdmr_info {
> };
>
> struct tdx_sysinfo {
> - struct tdx_sysinfo_tdmr_info tdmr_info;
> + struct tdx_sysinfo_module_info module_info;
> + struct tdx_sysinfo_module_version module_version;
> + struct tdx_sysinfo_tdmr_info tdmr_info;
> };
>
> #endif
next prev parent reply other threads:[~2024-08-08 10:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 3:40 [PATCH v2 00/10] TDX host: metadata reading tweaks, bug fix and info dump Kai Huang
2024-07-17 3:40 ` [PATCH v2 01/10] x86/virt/tdx: Rename _offset to _member for TD_SYSINFO_MAP() macro Kai Huang
2024-08-05 22:37 ` Dan Williams
2024-07-17 3:40 ` [PATCH v2 02/10] x86/virt/tdx: Unbind global metadata read with 'struct tdx_tdmr_sysinfo' Kai Huang
2024-08-05 23:32 ` Dan Williams
2024-08-06 0:09 ` Huang, Kai
2024-08-06 1:13 ` Dan Williams
2024-08-07 12:09 ` Huang, Kai
2024-08-26 15:38 ` Adrian Hunter
2024-08-26 22:40 ` Huang, Kai
2024-08-27 4:54 ` Adrian Hunter
2024-08-27 7:22 ` Huang, Kai
2024-07-17 3:40 ` [PATCH v2 03/10] x86/virt/tdx: Support global metadata read for all element sizes Kai Huang
2024-08-05 23:45 ` Dan Williams
2024-07-17 3:40 ` [PATCH v2 04/10] x86/virt/tdx: Abstract reading multiple global metadata fields as a helper Kai Huang
2024-07-17 3:40 ` [PATCH v2 05/10] x86/virt/tdx: Move field mapping table of getting TDMR info to function local Kai Huang
2024-08-05 23:48 ` Dan Williams
2024-07-17 3:40 ` [PATCH v2 06/10] x86/virt/tdx: Refine a comment to reflect the latest TDX spec Kai Huang
2024-08-06 3:43 ` Dan Williams
2024-08-06 11:23 ` Huang, Kai
2024-08-06 19:06 ` Dan Williams
2024-08-06 21:01 ` Huang, Kai
2024-07-17 3:40 ` [PATCH v2 07/10] x86/virt/tdx: Start to track all global metadata in one structure Kai Huang
2024-08-06 3:51 ` Dan Williams
2024-08-06 11:29 ` Huang, Kai
2024-07-17 3:40 ` [PATCH v2 08/10] x86/virt/tdx: Print TDX module basic information Kai Huang
2024-08-06 4:19 ` Dan Williams
2024-08-06 11:51 ` Huang, Kai
2024-08-06 12:48 ` Huang, Kai
2024-08-07 21:56 ` Dan Williams
2024-08-07 22:32 ` Huang, Kai
2024-08-08 10:31 ` Chenyi Qiang [this message]
2024-08-08 23:52 ` Huang, Kai
2024-07-17 3:40 ` [PATCH v2 09/10] x86/virt/tdx: Reduce TDMR's reserved areas by using CMRs to find memory holes Kai Huang
2024-08-06 4:47 ` Dan Williams
2024-08-06 12:17 ` Huang, Kai
2024-08-20 18:38 ` Adrian Hunter
2024-08-27 7:24 ` Huang, Kai
2024-07-17 3:40 ` [PATCH v2 10/10] x86/virt/tdx: Don't initialize module that doesn't support NO_RBP_MOD feature Kai Huang
2024-08-06 4:55 ` Dan Williams
2024-08-06 12:18 ` Huang, Kai
2024-08-05 12:03 ` [PATCH v2 00/10] TDX host: metadata reading tweaks, bug fix and info dump Huang, Kai
2024-08-05 22:36 ` Dan Williams
2024-08-08 0:19 ` Huang, Kai
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=0e36f025-9a8f-4f75-af4b-bc6252c29abe@intel.com \
--to=chenyi.qiang@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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