[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z9Gz9WnQRmLUR73I@8bytes.org>
Date: Wed, 12 Mar 2025 17:19:01 +0100
From: Joerg Roedel <joro@...tes.org>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Joerg Roedel <jroedel@...e.de>, x86@...nel.org, hpa@...or.com,
Tom Lendacky <thomas.lendacky@....com>,
Nikunj A Dadhania <nikunj@....com>, Larry.Dewey@....com,
linux-kernel@...r.kernel.org, linux-coco@...ts.linux.dev,
Juergen Gross <jgross@...e.com>, kirill.shutemov@...ux.intel.com,
alexey.gladkov@...el.com
Subject: Re: [PATCH 2/2] x86/sev: Make SEV_STATUS available via SYSFS
On Wed, Mar 12, 2025 at 09:04:14AM -0700, Dave Hansen wrote:
> Let's draw this out to its natural conclusion. There are also a bunch of
> TDX attributes that tell you about the capabilities of the VM and the
> TDX module.
>
> Should we have:
>
> /sys/devices/system/cpu/tdx/tdx_attributes
>
> which just dumps out the raw register values that come back from the
> TDCALL? Then we'll go write a tdxguest tool to parse those values.
If I remember correctly the goal of the VirTEE project (where the
snpguest tool lives) is to come up with a combined teeguest tool. This
will serve as a vendor- and architecture-independent frontend for the
various kernel interfaces for confidential computing (configfs-tsm,
sysfs-attributes, ...).
So yes, my expectation is that this tool will understand the raw values
returned from the TDCALL, as long as they are architectural.
But let me think a bit more about a solution that takes care of the
tooling and the human requirements.
Regards,
Joerg
Powered by blists - more mailing lists