[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z88KNWJ-6SsT4NPZ@example.org>
Date: Mon, 10 Mar 2025 16:50:13 +0100
From: Alexey Gladkov <legion@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Jürgen Groß <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 04:41:52PM +0100, Borislav Petkov wrote:
> On Mon, Mar 10, 2025 at 04:33:08PM +0100, Jürgen Groß wrote:
> > Kind of.
> >
> > /sys/hypervisor is meant to provide data for running under a hypervisor.
> >
> > It is NOT meant to provide data for running as a hypervisor.
>
> Hah.
>
> Which would mean that
>
> /sys/hypervisor == /sys/guest
>
> the way we envision it.
>
> Do we need to dump all the HV levels in it?
Hm. We already have:
/sys/hypervisor/type (Type of hypervisor)
/sys/hypervisor/guest_type (Type of guest)
I don't really understand how you propose to locate the files for host and
guest and what you propose to put in /sys/guest.
> I think Joerg wants to dump the fact that there's an SVSM present. I guess we
> can dump the "stack" of "things" running under Linux as you suggest it.
>
> Hmmm.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
--
Rgrds, legion
Powered by blists - more mailing lists