From: Tom Lendacky <thomas.lendacky@amd.com>
To: Dionna Amalie Glaze <dionnaglaze@google.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
John Allen <john.allen@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Ashish Kalra <ashish.kalra@amd.com>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Michael Roth <michael.roth@amd.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Russ Weight <russ.weight@linux.dev>,
Danilo Krummrich <dakr@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Tianfei zhang <tianfei.zhang@intel.com>,
Alexey Kardashevskiy <aik@amd.com>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 3/4] crypto: ccp: Add SNP firmware hotload support
Date: Mon, 4 Nov 2024 14:45:43 -0600 [thread overview]
Message-ID: <b0a5d1a6-39ef-2637-ece0-387582b09fcc@amd.com> (raw)
In-Reply-To: <CAAH4kHYqQAkUO8phdQaE=R0qHZjKBB1uXsKR3Nq5yJxeZS-o=A@mail.gmail.com>
On 11/4/24 13:30, Dionna Amalie Glaze wrote:
> On Mon, Nov 4, 2024 at 9:06 AM Tom Lendacky <thomas.lendacky@amd.com> wrote:
>> On 11/1/24 19:08, Dionna Glaze wrote:
>>
>> This is a big patch. Can you split this up into smaller patches? At a
>> minimum, one patch that adds the context tracking and one that adds the
>> firmware support.
>>
>
> Can do. Would it be appropriate to also add a sysfs attribute group
> for sev that makes the firmware version more easily readable? Or
> should I put that in a follow-up chain?
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?
Thanks,
Tom
> The dmesg log about the firmware version isn't the best for writing
> automation for managing firmware hotloading at scale, and we're better
> set up for working with sysfs generally.
>
>> Also, can the guest context page tracking and new firmware related
>> functions be placed in a new file, sev-fw.c or similar, that is
>> conditionally built based on CONFIG_FW_UPLOAD. Then a header file can be
>> used to provide the different implementations of the new functions
>> removing the #ifdefs from the code.
>>
>> Thanks,
>> Tom
>>
next prev parent reply other threads:[~2024-11-04 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 0:08 [PATCH v3 0/4] Support SEV firmware hotloading Dionna Glaze
2024-11-02 0:08 ` [PATCH v3 1/4] kvm: svm: Fix gctx page leak on invalid inputs Dionna Glaze
2024-11-02 0:08 ` [PATCH v3 2/4] firmware_loader: Move module refcounts to allow unloading Dionna Glaze
2024-11-02 0:08 ` [PATCH v3 3/4] crypto: ccp: Add SNP firmware hotload support Dionna Glaze
2024-11-04 17:06 ` Tom Lendacky
2024-11-04 19:30 ` Dionna Amalie Glaze
2024-11-04 20:45 ` Tom Lendacky [this message]
2024-11-04 21:27 ` Dionna Amalie Glaze
2024-11-07 17:20 ` Tom Lendacky
2024-11-05 2:32 ` Alexey Kardashevskiy
2024-11-02 0:08 ` [PATCH v3 4/4] KVM: SVM: Delay legacy platform initialization on SNP Dionna Glaze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0a5d1a6-39ef-2637-ece0-387582b09fcc@amd.com \
--to=thomas.lendacky@amd.com \
--cc=aik@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dakr@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dionnaglaze@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=tianfei.zhang@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox