[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d9a1a460-2982-429c-b29d-cf2483e9380a@suse.com>
Date: Wed, 5 Mar 2025 12:35:56 +0100
From: Juergen Gross <jgross@...e.com>
To: Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...nel.org>
Cc: Joerg Roedel <joro@...tes.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,
Joerg Roedel <jroedel@...e.de>
Subject: Re: [PATCH] x86/sev: Make SEV_STATUS available via SYSFS
On 05.03.25 12:31, Borislav Petkov wrote:
> On Wed, Mar 05, 2025 at 12:26:13PM +0100, Ingo Molnar wrote:
>> It's *far* better to expose this via a targeted sysfs entry than
>> polluting /proc/cpuinfo with it that everyone and their dog is parsing
>> all the time ...
>
> Pasting what we're talking on IRC:
>
> - we don't want to expose a naked MSR u64 to userspace. Might as well use
> msr-tools
>
> - the backstory is, there are a bunch of tools which wanna know this so we
> need to agree on how to supply it to them
>
> - I think /proc/cpuinfo is the best option right now
>
> - and then TDX can use the same thing too
>
> - we have a general need to expose what a confidential guest supports
>
> - a .../sev sysfs file clearly doesn't cut it because TDX doesn't have "sev"
> - it is the Intel version of a confidential guest
>
> - and I don't want to have "0xdeadbeef" in some sys file but "SEV SEV-ES TDX
> SecureTSC" and so on user-readable strings
There is /sys/hypervisor/
Why don't put it there? Maybe under /sys/hypervisor/coco.
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