From: <dan.j.williams@intel.com>
To: Chao Gao <chao.gao@intel.com>, Kiryl Shutsemau <kas@kernel.org>
Cc: <kvm@vger.kernel.org>, <linux-coco@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<vishal.l.verma@intel.com>, <kai.huang@intel.com>,
<dan.j.williams@intel.com>, <yilun.xu@linux.intel.com>,
<vannapurve@google.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2 0/3] Expose TDX Module version
Date: Tue, 6 Jan 2026 16:36:34 -0800 [thread overview]
Message-ID: <695daa92c40fc_4b7a1002f@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <aVywHbHlcRw2tM/X@intel.com>
Chao Gao wrote:
[..]
> And in my opinion, exposing version information to guests is also unnecessary
> since the module version can already be read from the host with this series.
> In debugging scenarios, I'm not sure why the TDX module would be so special
> that guests should know its version but not other host information, such as
> host kernel version, microcode version, etc. None of these are exposed to guest
> kernel (not to mention guest userspace).
Agree, and note that the guest already has full launch attestation
details available via the common
Documentation/ABI/testing/configfs-tsm-report transport.
I assume the primary need for version information is debug, but if you
are debugging a guest problem might as well get the entire launch
attestation with the version of "all the things" included.
prev parent reply other threads:[~2026-01-07 0:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 7:43 [PATCH v2 0/3] Expose TDX Module version Chao Gao
2026-01-05 7:43 ` [PATCH v2 1/3] x86/virt/tdx: Retrieve " Chao Gao
2026-01-05 7:43 ` [PATCH v2 2/3] coco/tdx-host: Expose " Chao Gao
2026-01-05 7:43 ` [PATCH v2 3/3] x86/virt/tdx: Print TDX Module version during init Chao Gao
2026-01-05 10:38 ` [PATCH v2 0/3] Expose TDX Module version Kiryl Shutsemau
2026-01-05 16:04 ` Dave Hansen
2026-01-05 17:04 ` Kiryl Shutsemau
2026-01-05 17:19 ` Dave Hansen
2026-01-05 18:03 ` Kiryl Shutsemau
2026-01-07 21:34 ` dan.j.williams
2026-01-07 22:26 ` Dave Hansen
2026-01-06 10:23 ` Chao Gao
2026-01-06 16:37 ` Dave Hansen
2026-01-06 6:47 ` Chao Gao
2026-01-06 9:17 ` Nikolay Borisov
2026-01-06 11:19 ` Kiryl Shutsemau
2026-01-06 13:31 ` Chao Gao
2026-01-07 0:36 ` dan.j.williams [this message]
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=695daa92c40fc_4b7a1002f@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=vannapurve@google.com \
--cc=vishal.l.verma@intel.com \
--cc=x86@kernel.org \
--cc=yilun.xu@linux.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