[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <efbnludlccxde7bwt64faajkmadufyolcetl5at3anmvy5mi36@5q6zdzmwtvae>
Date: Thu, 6 Mar 2025 15:36:02 +0200
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Joerg Roedel <joro@...tes.org>, Dave Hansen <dave.hansen@...el.com>,
Joerg Roedel <jroedel@...e.de>, 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, "Alexey Gladkov (Intel)" <alexey.gladkov@...el.com>
Subject: Re: [PATCH] x86/sev: Make SEV_STATUS available via SYSFS
On Thu, Mar 06, 2025 at 11:31:19AM +0100, Borislav Petkov wrote:
> On Thu, Mar 06, 2025 at 09:38:21AM +0100, Joerg Roedel wrote:
> > On Thu, Mar 06, 2025 at 10:01:17AM +0200, Kirill A. Shutemov wrote:
> > > Alexey looking into exposing TDX module version in sysfs for both guest
> > > and host.
> > >
> > > I think it would be useful for guest to make attributes and TD_CTLS
> > > available via sysfs. So far, we only dump them in dmesg on boot (see
> > > 564ea84c8c14).
> >
> > Okay, do you have ideas already on where to put this information in
> > SYSFS?
>
> Right, I was thinking about it: sysfs does a one-datum-per-file thing and that
> would go nuts very quickly.
I think we should be pretty use to one-datum-per-file thing by now.
I don't see why coco case is special.
--
Kiryl Shutsemau / Kirill A. Shutemov
Powered by blists - more mailing lists