[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b79ee8b1-768b-4c25-a665-453c23cf9b6f@suse.com>
Date: Mon, 10 Mar 2025 17:00:50 +0100
From: Juergen Gross <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 16:55, Borislav Petkov wrote:
> On Mon, Mar 10, 2025 at 04:52:37PM +0100, Juergen Gross wrote:
>> /sys/kvm/ might be a good fit when using KVM?
>
> What are we going to do when Xen runs coco guests? Or there's no such danger
> in the near future?
There is work in progress for SEV guests at least.
Shouldn't the coco related information be the same regardless of the
hypervisor beneath? 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?
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