From: "Singh, Brijesh" <brijesh.singh@amd.com>
To: "Kalra, Ashish" <Ashish.Kalra@amd.com>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"Hook, Gary" <Gary.Hook@amd.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"allison@lohutok.net" <allison@lohutok.net>,
"info@metux.net" <info@metux.net>,
"yamada.masahiro@socionext.com" <yamada.masahiro@socionext.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: "Singh, Brijesh" <brijesh.singh@amd.com>
Subject: Re: [PATCH] crypto: ccp - Retry SEV INIT command in case of integrity check failure.
Date: Wed, 23 Oct 2019 01:36:55 +0000 [thread overview]
Message-ID: <14a4cb7c-5909-189a-c5ba-56df4e4fb65a@amd.com> (raw)
In-Reply-To: <20191017223459.64281-1-Ashish.Kalra@amd.com>
On 10/17/19 3:35 PM, Kalra, Ashish wrote:
> From: Ashish Kalra <ashish.kalra@amd.com>
>
> SEV INIT command loads the SEV related persistent data from NVS
> and initializes the platform context. The firmware validates the
> persistent state. If validation fails, the firmware will reset
> the persisent state and return an integrity check failure status.
>
> At this point, a subsequent INIT command should succeed, so retry
> the command. The INIT command retry is only done during driver
> initialization.
>
> Additional enums along with SEV_RET_SECURE_DATA_INVALID are added
> to sev_ret_code to maintain continuity and relevance of enum values.
>
> Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
Reviewed-by: Brijesh Singh <brijesh.singh@amd.com>
thanks
next prev parent reply other threads:[~2019-10-23 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 22:35 [PATCH] crypto: ccp - Retry SEV INIT command in case of integrity check failure Kalra, Ashish
2019-10-19 8:59 ` David Rientjes
2019-10-21 18:16 ` Singh, Brijesh
2019-10-22 0:57 ` David Rientjes
2019-10-22 13:38 ` Singh, Brijesh
2019-10-23 0:23 ` David Rientjes
2019-10-23 1:36 ` Singh, Brijesh [this message]
2019-10-25 15:25 ` 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=14a4cb7c-5909-189a-c5ba-56df4e4fb65a@amd.com \
--to=brijesh.singh@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=Gary.Hook@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=allison@lohutok.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=info@metux.net \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.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