public inbox for linux-coco@lists.linux.dev
 help / color / mirror / Atom feed
From: Kiryl Shutsemau <kas@kernel.org>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>,
	 dave.hansen@linux.intel.com
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	 "linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	 "Gao, Chao" <chao.gao@intel.com>,
	"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
	 "Huang, Kai" <kai.huang@intel.com>,
	"bp@alien8.de" <bp@alien8.de>,
	 "mingo@redhat.com" <mingo@redhat.com>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	 "tglx@linutronix.de" <tglx@linutronix.de>,
	"hpa@zytor.com" <hpa@zytor.com>,
	 "x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v2 0/2] x86/virt/tdx: Print TDX module version to dmesg
Date: Fri, 6 Feb 2026 11:39:11 +0000	[thread overview]
Message-ID: <aYXSd8B00OtKZcAU@thinkstation> (raw)
In-Reply-To: <6d8d37740459963e6fd7f16a890a837b34ebdf17.camel@intel.com>

On Thu, Feb 05, 2026 at 07:05:39PM +0000, Verma, Vishal L wrote:
> On Fri, 2026-01-09 at 12:14 -0700, Vishal Verma wrote:
> > === Problem & Solution ===
> > 
> > Currently, there is neither an ABI, nor any other way to determine from
> > the host system, what version of the TDX module is running. A sysfs ABI
> > for this has been proposed in [1], but it may need additional discussion.
> > 
> > Many/most TDX developers already carry patches like this in their
> > development branches. It can be tricky to know which TDX module is
> > actually loaded on a system, and so this functionality has been needed
> > regularly for development and processing bug reports. Hence, it is
> > prudent to break out the patches to retrieve and print the TDX module
> > version, as those parts are very straightforward, and get some level of
> > debugability and traceability for TDX host systems.
> > 
> > === Dependencies ===
> > 
> > None. This is based on v6.19-rc4, and applies cleanly to tip.git.
> > 
> > === Patch details ===
> > 
> > Patch 1 is a prerequisite that adds the infrastructure to retrieve the
> > TDX module version from its global metadata. This was originally posted in [2].
> > 
> > Patch 2 is based on a patch from Kai Huang [3], and prints the version to
> > dmesg during init.
> > 
> > === Testing ===
> > 
> > This has passed the usual suite of tests, including successful 0day
> > builds, KVM Unit tests, KVM selftests, a TD creation smoke test, and
> > selected KVM tests from the Avocado test suite.
> > 
> > [1]: https://lore.kernel.org/all/20260105074350.98564-1-chao.gao@intel.com/
> > [2]: https://lore.kernel.org/all/20260105074350.98564-2-chao.gao@intel.com/
> > [3]: https://lore.kernel.org/all/57eaa1b17429315f8b5207774307f3c1dd40cf37.1730118186.git.kai.huang@intel.com/
> > 
> > Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> 
> Hi Kiryl, just wanted to check on the plan for this, I didn't see it
> merged in tip.git x86/tdx (or any other tip branch). Were you planning
> to take it through x86/tdx? Can I help with anything to move it along?

I guess it has to wait after the merge window at this point.

Dave, could you queue this after -rc1 is tagged?

-- 
  Kiryl Shutsemau / Kirill A. Shutemov

  reply	other threads:[~2026-02-06 11:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 19:14 [PATCH v2 0/2] x86/virt/tdx: Print TDX module version to dmesg Vishal Verma
2026-01-09 19:14 ` [PATCH v2 1/2] x86/virt/tdx: Retrieve TDX module version Vishal Verma
2026-01-12  2:25   ` Xiaoyao Li
2026-01-12 14:56     ` Dave Hansen
2026-01-13  2:56       ` Xu Yilun
2026-01-13  3:58         ` Xiaoyao Li
2026-01-12  8:30   ` Binbin Wu
2026-01-19  8:12   ` Tony Lindgren
2026-01-09 19:14 ` [PATCH v2 2/2] x86/virt/tdx: Print TDX module version during init Vishal Verma
2026-01-09 20:00   ` Edgecombe, Rick P
2026-01-12  2:31   ` Xiaoyao Li
2026-01-12  8:32   ` Binbin Wu
2026-01-12 11:23   ` Kiryl Shutsemau
2026-01-19  8:12   ` Tony Lindgren
2026-01-11 22:15 ` [PATCH v2 0/2] x86/virt/tdx: Print TDX module version to dmesg Huang, Kai
2026-02-05 19:05 ` Verma, Vishal L
2026-02-06 11:39   ` Kiryl Shutsemau [this message]
2026-02-06 15:10     ` Dave Hansen
2026-02-06 18:35       ` Edgecombe, Rick P
2026-02-09 10:46       ` Kiryl Shutsemau

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=aYXSd8B00OtKZcAU@thinkstation \
    --to=kas@kernel.org \
    --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=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=vishal.l.verma@intel.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