[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aW3nh8n6I8rJxPXl@tlindgre-MOBL1>
Date: Mon, 19 Jan 2026 10:12:55 +0200
From: Tony Lindgren <tony.lindgren@...ux.intel.com>
To: Vishal Verma <vishal.l.verma@...el.com>
Cc: linux-kernel@...r.kernel.org, linux-coco@...ts.linux.dev,
kvm@...r.kernel.org, x86@...nel.org, Chao Gao <chao.gao@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
Kai Huang <kai.huang@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Kiryl Shutsemau <kas@...nel.org>,
Rick Edgecombe <rick.p.edgecombe@...el.com>
Subject: Re: [PATCH v2 2/2] x86/virt/tdx: Print TDX module version during init
On Fri, Jan 09, 2026 at 12:14:31PM -0700, Vishal Verma wrote:
> It is useful to print the TDX module version in dmesg logs. This is
> currently the only way to determine the module version from the host. It
> also creates a record for any future problems being investigated. This
> was also requested in [1].
>
> Include the version in the log messages during init, e.g.:
>
> virt/tdx: TDX module version: 1.5.24
> virt/tdx: 1034220 KB allocated for PAMT
> virt/tdx: module initialized
>
> Print the version in get_tdx_sys_info(), right after the version
> metadata is read, which makes it available even if there are subsequent
> initialization failures.
Reviewed-by: Tony Lindgren <tony.lindgren@...ux.intel.com>
Powered by blists - more mailing lists