From: Dave Hansen <dave.hansen@intel.com>
To: dan.j.williams@intel.com, Kiryl Shutsemau <kas@kernel.org>
Cc: Chao Gao <chao.gao@intel.com>,
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,
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: Wed, 7 Jan 2026 14:26:03 -0800 [thread overview]
Message-ID: <aa3f026b-ad69-4070-8433-8950e5250edb@intel.com> (raw)
In-Reply-To: <695ed1604db38_4b7a10028@dwillia2-mobl4.notmuch>
On 1/7/26 13:34, dan.j.williams@intel.com wrote:
> For sake of argument, I assume you have no fundamental objection to
> module version information in sysfs in general? I.e. is the question
> more on the where and how for TDX sysfs?
For reference, and so the next poster can write an excellent and focused
changelog wherever this goes, the context I was yearning for in the
changelog was:
1. AMD has a PCI device for the PSP for SEV which provides an existing
place to hang their equivalent metadata. TDX has no PCI device.
2. ARM CCA will likely have a faux device (although it isn't obvious if
they have a need to export version information there)
3. The TDX faux device will drive TDX module updates. The version number
is obviously deeply important to entities doing updates.
So, no, I don't have a fundamental objection to having TDX module
version information in sysfs. But, in the context of this series, I
don't see any incremental value for doing it in addition to dmesg _now_.
If the module updater userspace needs it, then I'd rather defer the
sysfs export (and faux device creation) until the time that there's an
actual concrete user.
next prev parent reply other threads:[~2026-01-07 22:26 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 [this message]
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
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=aa3f026b-ad69-4070-8433-8950e5250edb@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dan.j.williams@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