[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5f4ae919-6283-43f4-b8fb-8ff43d1de645@suse.com>
Date: Tue, 11 Mar 2025 12:14:27 +0100
From: Juergen Gross <jgross@...e.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Joerg Roedel <jroedel@...e.de>, 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>, 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 11.03.25 12:07, Borislav Petkov wrote:
> On Tue, Mar 11, 2025 at 11:22:23AM +0100, Jürgen Groß wrote:
>> I can live with that, as long as we make it possible to make e.g.
>> /sys/guest/xen a link to /sys/hypervisor (if xen is the hypervisor
>> the guest is directly running on). This means that /sys/guest/*/type
>> should not conflict with /sys/hypervisor/type.
>
> Yeah, so Joerg and I came up with this on IRC:
>
> /sys/hypervisor/{sev,tdx}
>
> * It should not disturb the current hierarchy there
>
> * No need for a new hierarchy like /sys/guest - we haz enough and besides,
> /sys/hypervisor sounds like the right place already
>
> * ...
>
> So yeah, I guess we can try this.
Full ack for this plan.
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