From: "Kalra, Ashish" <ashish.kalra@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
John Allen <john.allen@amd.com>
Subject: Re: [PATCH] crypto: ccp: Add additional information about an SEV firmware upgrade
Date: Wed, 14 Aug 2024 17:05:54 -0500 [thread overview]
Message-ID: <5ef62b3f-32c5-47c8-bab1-397dc7084a17@amd.com> (raw)
In-Reply-To: <bba259429fc14c4cac9ee4995dfb05d82065b67b.1723668160.git.thomas.lendacky@amd.com>
On 8/14/2024 3:42 PM, Tom Lendacky wrote:
> Print additional information, in the form of the old and new versions of
> the SEV firmware, so that it can be seen what the base firmware was before
> the upgrade.
>
> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> drivers/crypto/ccp/sev-dev.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-dev.c
> index 9810edbb272d..3b89f23afcd7 100644
> --- a/drivers/crypto/ccp/sev-dev.c
> +++ b/drivers/crypto/ccp/sev-dev.c
> @@ -1629,8 +1629,6 @@ static int sev_update_firmware(struct device *dev)
>
> if (ret)
> dev_dbg(dev, "Failed to update SEV firmware: %#x\n", error);
> - else
> - dev_info(dev, "SEV firmware update successful\n");
>
> __free_pages(p, order);
>
> @@ -2382,6 +2380,7 @@ void sev_pci_init(void)
> {
> struct sev_device *sev = psp_master->sev_data;
> struct sev_platform_init_args args = {0};
> + u8 api_major, api_minor, build;
> int rc;
>
> if (!sev)
> @@ -2392,9 +2391,19 @@ void sev_pci_init(void)
> if (sev_get_api_version())
> goto err;
>
> + api_major = sev->api_major;
> + api_minor = sev->api_minor;
> + build = sev->build;
> +
> if (sev_update_firmware(sev->dev) == 0)
> sev_get_api_version();
>
> + if (api_major != sev->api_major || api_minor != sev->api_minor ||
> + build != sev->build)
> + dev_info(sev->dev, "SEV firmware updated from %d.%d.%d to %d.%d.%d\n",
> + api_major, api_minor, build,
> + sev->api_major, sev->api_minor, sev->build);
> +
> /* Initialize the platform */
> args.probe = true;
> rc = sev_platform_init(&args);
Reviewed-by: Ashish Kalra <ashish.kalra@amd.com>
next prev parent reply other threads:[~2024-08-14 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 20:42 Tom Lendacky
2024-08-14 22:05 ` Kalra, Ashish [this message]
2024-08-24 13:49 ` Herbert Xu
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=5ef62b3f-32c5-47c8-bab1-397dc7084a17@amd.com \
--to=ashish.kalra@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
/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
all inboxes | Powered by JetHome®