[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <pskj4f5fitd5ytb7gq4negloioihl2rfbpfwa47fnw74gxmlvh@vpoijhxcee64>
Date: Wed, 12 Mar 2025 10:48:37 +0200
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: Joerg Roedel <joro@...tes.org>
Cc: Joerg Roedel <jroedel@...e.de>, Alexey Gladkov <legion@...nel.org>,
Borislav Petkov <bp@...en8.de>, Jürgen Groß <jgross@...e.com>,
"Alexey Gladkov (Intel)" <alexey.gladkov@...el.com>, Dave Hansen <dave.hansen@...el.com>,
Ingo Molnar <mingo@...nel.org>, x86@...nel.org, hpa@...or.com,
Tom Lendacky <thomas.lendacky@....com>, Nikunj A Dadhania <nikunj@....com>, linux-kernel@...r.kernel.org,
Larry.Dewey@....com
Subject: Re: [PATCH] x86/sev: Make SEV_STATUS available via SYSFS
On Wed, Mar 12, 2025 at 09:23:13AM +0100, Joerg Roedel wrote:
> On Wed, Mar 12, 2025 at 09:19:30AM +0200, Kirill A. Shutemov wrote:
> > TDX module information (version, supported features, etc) is crucial for
> > bug reporting. I think it makes sense to present it in sysfs.
>
> The SEV side presents this information via dmesg and /dev/sev, we
> can also talk about a place in sysfs for it. But the place to present
> host-side information is a separate discussion.
There might be a value to have consistent structure for host and guest
information in sysfs, even if they are presented in different places under
/sys. There's subset of information that is common for both guest and
host, like version.
--
Kiryl Shutsemau / Kirill A. Shutemov
Powered by blists - more mailing lists