From: Alexey Gladkov <legion@kernel.org>
To: x86@kernel.org
Cc: "Alexey Gladkov (Intel)" <legion@kernel.org>,
linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev,
Alexey Gladkov <alexey.gladkov@intel.com>,
"H . Peter Anvin" <hpa@zytor.com>, Joerg Roedel <jroedel@suse.de>,
Juergen Gross <jgross@suse.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Larry.Dewey@amd.com, Nikunj A Dadhania <nikunj@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: [RFC PATCH v1 0/3] Export TDX module information via SYSFS
Date: Fri, 14 Mar 2025 12:56:25 +0100 [thread overview]
Message-ID: <cover.1741952958.git.legion@kernel.org> (raw)
From: "Alexey Gladkov (Intel)" <legion@kernel.org>
TD-Preserving updates depend on a userspace tool to select the appropriate
module to load. To facilitate this decision-making process, expose the
necessary information to userspace.
Also TDX module information (version, supported features, etc) is crucial for
bug reporting. For this purpose, it makes sense to have a consistent structure
for host and guest information in sysfs.
As already discussed [1] in the mailing list for tdx used the directory
/sys/hypervisor/tdx.
[1] https://lore.kernel.org/lkml/20250311110748.GCZ9AZhPYYAz-MXErv@fat_crate.local/
Alexey Gladkov (Intel) (3):
x86/tdx: Make TDX metadata available via SYSFS
x86/tdx: Make TDX metadata available on guest via SYSFS
docs: ABI: testing: Add documentation about TDX
.../ABI/testing/sysfs-hypervisor-tdx | 50 ++++++++++
arch/x86/Kconfig | 2 +
arch/x86/coco/tdx/tdx.c | 92 +++++++++++++++++++
arch/x86/include/asm/shared/tdx.h | 2 +
arch/x86/include/asm/tdx.h | 12 +++
arch/x86/virt/vmx/tdx/tdx.c | 74 +++++++++++++++
6 files changed, 232 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-hypervisor-tdx
--
2.48.1
next reply other threads:[~2025-03-14 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 11:56 Alexey Gladkov [this message]
2025-03-14 11:56 ` [RFC PATCH v1 1/3] x86/tdx: Make TDX metadata available via SYSFS Alexey Gladkov
2025-03-14 23:42 ` Dan Williams
2025-03-17 9:38 ` Kirill A . Shutemov
2025-03-18 1:35 ` Dan Williams
2025-03-18 9:30 ` Kirill A . Shutemov
2025-03-19 16:58 ` Dan Williams
2025-03-14 11:56 ` [RFC PATCH v1 2/3] x86/tdx: Make TDX metadata available on guest " Alexey Gladkov
2025-03-14 11:56 ` [RFC PATCH v1 3/3] docs: ABI: testing: Add documentation about TDX Alexey Gladkov
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=cover.1741952958.git.legion@kernel.org \
--to=legion@kernel.org \
--cc=Larry.Dewey@amd.com \
--cc=alexey.gladkov@intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jroedel@suse.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=nikunj@amd.com \
--cc=thomas.lendacky@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).