[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0087e5f2-0fb5-4dd0-a3f2-c6e1dc192877@suse.com>
Date: Mon, 10 Mar 2025 17:23:53 +0100
From: Jürgen Groß <jgross@...e.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Alexey Gladkov <legion@...nel.org>, 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 10.03.25 17:06, Borislav Petkov wrote:
> On Mon, Mar 10, 2025 at 05:00:50PM +0100, Juergen Gross wrote:
>> There is work in progress for SEV guests at least.
>
> Nice.
>
>> Shouldn't the coco related information be the same regardless of the
>> hypervisor beneath?
>
> Right, but...
>
>> IOW: do you envision the coding for populating the coco related sysfs guest
>> nodes to be different when running as a KVM or a Hyper-V guest?
>
> ... if you have some coco tools which need to read out HV info - for whatever
> reason - then they'll have to do:
>
> if (HV == KVM)
> read /sys/kvm
> else if (HV == Xen)
> read /sys/xen
> else
> ...
>
> which we might save them upfront...
In case there is the need for such information in a guest (and it can only
be in a guest, as every Linux under Xen is a guest, same applies to Hyper-V
and VMWare), the information should be under /sys/hypervisor.
If Linux supports running as a hypervisor using something different than KVM
then we should add something like /sys/virt-platform for such data.
Juergen
Download attachment "OpenPGP_0xB0DE9DD628BF132F.asc" of type "application/pgp-keys" (3684 bytes)
Download attachment "OpenPGP_signature.asc" of type "application/pgp-signature" (496 bytes)
Powered by blists - more mailing lists