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

Alexey Gladkov
2025-03-10T14:50:17Z

On Mon, Mar 10, 2025 at 02:38:33PM +0100, Borislav Petkov wrote:
> On Mon, Mar 10, 2025 at 01:49:46PM +0100, Juergen Gross wrote:
> > 1. Only name the hypervisor nearest to the guest (similar to running Xen on
> > top of another hypervisor in nested virtualization, which would still
> > say "xen").
> >
> > 2. Add another entry for naming the outer hypervisor(s) (if possible).
> >
> > 3. Name all known hypervisor levels, like "kvm,svsm" or "svsm,kvm").
>
> /sys/guest it is then.
>
> Let's just keep /sys/hypervisor alone and as Joerg said, we can link to it
> from /sys/guest.
>
> I guess that sounds ok...

Am I understand correctly that you and Joerg are proposing

/sys/guest/tdx/...
/sys/guest/sev/...

?

Which path to use for the host side ?

For guest: /sys/coco/guest/{tdx,sev}/...
For host: /sys/coco/host/{tdx,sev}/...

Maybe it would be better to add the "coco" subdirectory or something like
that ?

--
Rgrds, legion