[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250310151154.GOZ88BOinZVkbYEx0w@fat_crate.local>
Date: Mon, 10 Mar 2025 16:11:54 +0100
From: Borislav Petkov <bp@...en8.de>
To: Alexey Gladkov <legion@...nel.org>
Cc: Juergen Gross <jgross@...e.com>, Joerg Roedel <joro@...tes.org>,
"Alexey Gladkov (Intel)" <alexey.gladkov@...el.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
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
Subject: Re: [PATCH] x86/sev: Make SEV_STATUS available via SYSFS
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.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists