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

Borislav Petkov
2025-03-10T15:12:17Z

On Mon, Mar 10, 2025 at 03:50:09PM +0100, Alexey Gladkov wrote:
> 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 ?

Hmm, so we can do

/sys/guest

and extend

/sys/hypervisor

Or we can do what you're suggesting.

If we do /sys/coco/host, then we'll have two different places to read HV info.

Or we can stick *everything* coco needs in

/sys/coco/{sev,tdx}

but then it is coco-specific and if other guest types want to put stuff in
sysfs, it'll get ugly.

So I guess having

/sys/guest
and
/sys/hypervisor

kinda keeps it all clean, hierarchy-wise...

Right?

--
Regards/Gruss,
Boris.