Re: [PATCH] x86/sev: Make SEV_STATUS available via SYSFS

Kirill A. Shutemov
2025-03-12T07:19:35Z

On Tue, Mar 11, 2025 at 07:40:13PM +0100, Joerg Roedel wrote:
> On Tue, Mar 11, 2025 at 07:24:09PM +0100, Alexey Gladkov wrote:
> > On Tue, Mar 11, 2025 at 12:07:48PM +0100, Borislav Petkov wrote:
> > > On Tue, Mar 11, 2025 at 11:22:23AM +0100, Jürgen Groß wrote:
> > > > I can live with that, as long as we make it possible to make e.g.
> > > > /sys/guest/xen a link to /sys/hypervisor (if xen is the hypervisor
> > > > the guest is directly running on). This means that /sys/guest/*/type
> > > > should not conflict with /sys/hypervisor/type.
> > >
> > > Yeah, so Joerg and I came up with this on IRC:
> > >
> > > /sys/hypervisor/{sev,tdx}
> >
> > This directory is for guest-side information, right ?
> >
> > >
> > > * It should not disturb the current hierarchy there
> > >
> > > * No need for a new hierarchy like /sys/guest - we haz enough and besides,
> > > /sys/hypervisor sounds like the right place already
> >
> > The /sys/hypervisor is for host-side information ?
>
> No, all under /sys/hypervisor is for guest-side information. There is
> not directory for host-side information yet. The question is whether a
> directory in SYSFS is needed, or whether there are other means to expose
> the same information.

TDX module information (version, supported features, etc) is crucial for
bug reporting. I think it makes sense to present it in sysfs.

--
Kiryl Shutsemau / Kirill A. Shutemov