[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3b321462-e62f-7d68-340c-fcb23ff3df18@amd.com>
Date: Thu, 7 Nov 2024 11:20:31 -0600
From: Tom Lendacky <thomas.lendacky@....com>
To: Dionna Amalie Glaze <dionnaglaze@...gle.com>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
John Allen <john.allen@....com>, Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>, Ashish Kalra
<ashish.kalra@....com>, Sean Christopherson <seanjc@...gle.com>,
Paolo Bonzini <pbonzini@...hat.com>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Michael Roth <michael.roth@....com>, Luis Chamberlain <mcgrof@...nel.org>,
Russ Weight <russ.weight@...ux.dev>, Danilo Krummrich <dakr@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Tianfei zhang <tianfei.zhang@...el.com>, Alexey Kardashevskiy <aik@....com>,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH v3 3/4] crypto: ccp: Add SNP firmware hotload support
On 11/4/24 15:27, Dionna Amalie Glaze wrote:
> On Mon, Nov 4, 2024 at 12:45 PM Tom Lendacky <thomas.lendacky@....com> wrote:
>>
>>
>> That would be best as a separate patch series. But doesn't the
>> SEV_PLATFORM_STATUS or SNP_PLATFORM_STATUS ioctl() give you all the
>> information you need?
>
> It does, it's just that sysfs is the preferred method of getting this
> kind of information. If it's seen as duplicative for the upstream
> kernel, then I can drop it.
I don't have any issues with exposing via sysfs. We'll just need to
decide how best to expose the attributes.
Thanks,
Tom
>
Powered by blists - more mailing lists