[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <778ca56b-7731-736e-1d0a-84ee2b2c261c@amd.com>
Date: Mon, 10 Mar 2025 09:39:42 -0500
From: Tom Lendacky <thomas.lendacky@....com>
To: Borislav Petkov <bp@...en8.de>, Juergen Gross <jgross@...e.com>
Cc: Joerg Roedel <joro@...tes.org>, Alexey Gladkov <legion@...nel.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,
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 3/10/25 08:38, 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...
And we should link the VMPL setting currently under
/sys/devices/system/cpu/sev/
Thanks,
Tom
>
> Thx.
>
Powered by blists - more mailing lists