From: Tom Lendacky <thomas.lendacky@amd.com>
To: Dionna Glaze <dionnaglaze@google.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Joerg Roedel <jroedel@suse.de>, Ingo Molnar <mingo@redhat.com>,
Andy Lutomirsky <luto@kernel.org>
Subject: Re: [PATCH v4 1/4] ccp: Name -1 return value as SEV_RET_NO_FW_CALL
Date: Fri, 28 Oct 2022 09:35:05 -0500 [thread overview]
Message-ID: <a3379b77-9cf5-dece-191e-60c4e9518b93@amd.com> (raw)
In-Reply-To: <20221024224657.2917482-2-dionnaglaze@google.com>
On 10/24/22 17:46, Dionna Glaze wrote:
> The PSP can return a "firmware error" code of -1 in circumstances where
> the PSP is not actually called. To make this protocol unambiguous, we
> add a constant naming the return value.
>
> From: Peter Gonda <pgonda@google.com>
> Cc: Thomas Lendacky <Thomas.Lendacky@amd.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Joerg Roedel <jroedel@suse.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Andy Lutomirsky <luto@kernel.org>
>
> Signed-off-by: Dionna Glaze <dionnaglaze@google.com>
Just one minor comment below, otherwise...
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> drivers/crypto/ccp/sev-dev.c | 2 +-
> include/uapi/linux/psp-sev.h | 7 +++++++
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-dev.c
> index 06fc7156c04f..97eb3544ab36 100644
> --- a/drivers/crypto/ccp/sev-dev.c
> +++ b/drivers/crypto/ccp/sev-dev.c
> @@ -444,7 +444,7 @@ static int __sev_platform_init_locked(int *error)
> {
> struct psp_device *psp = psp_master;
> struct sev_device *sev;
> - int rc = 0, psp_ret = -1;
> + int rc = 0, psp_ret = SEV_RET_NO_FW_CALL;
> int (*init_function)(int *error);
>
> if (!psp || !psp->sev_data)
> diff --git a/include/uapi/linux/psp-sev.h b/include/uapi/linux/psp-sev.h
> index 91b4c63d5cbf..fb61e083d42e 100644
> --- a/include/uapi/linux/psp-sev.h
> +++ b/include/uapi/linux/psp-sev.h
> @@ -36,6 +36,13 @@ enum {
> * SEV Firmware status code
> */
> typedef enum {
> + /*
> + * This error code is not in the SEV spec but is added to convey that
> + * there was an error that prevented the SEV Firmware from being called.
> + * This is (u32)-1 since the firmware error code part of EXIT_INFO_2 is
> + * the lower 32 bits.
These codes are used for /dev/sev access on the HV side, too, where
EXIT_INFO_2 doesn't exist. I would change this to something like:
This is (u32)-1 since the firwmare error code is represented as a 32-bit
integer.
Thanks,
Tom
> + */
> + SEV_RET_NO_FW_CALL = 0xffffffff,
> SEV_RET_SUCCESS = 0,
> SEV_RET_INVALID_PLATFORM_STATE,
> SEV_RET_INVALID_GUEST_STATE,
next prev parent reply other threads:[~2022-10-28 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 22:46 [PATCH v4 0/4] Add throttling detection to sev-guest Dionna Glaze
2022-10-24 22:46 ` [PATCH v4 1/4] ccp: Name -1 return value as SEV_RET_NO_FW_CALL Dionna Glaze
2022-10-28 14:35 ` Tom Lendacky [this message]
2022-10-24 22:46 ` [PATCH v4 2/4] x86/sev: Change snp_guest_issue_request's fw_err Dionna Glaze
2022-10-27 16:09 ` Peter Gonda
2022-10-27 16:11 ` Dionna Amalie Glaze
2022-10-28 14:45 ` Tom Lendacky
2022-10-24 22:46 ` [PATCH v4 3/4] virt/coco/sev-guest: Remove err in handle_guest_request Dionna Glaze
2022-10-28 14:46 ` Tom Lendacky
2022-10-24 22:46 ` [PATCH v4 4/4] virt/coco/sev-guest: interpret VMM errors from guest request Dionna Glaze
2022-10-28 15:15 ` Tom Lendacky
2022-10-28 15:57 ` Dionna Amalie Glaze
2022-10-27 15:53 ` [PATCH v4 0/4] Add throttling detection to sev-guest Dionna Amalie 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=a3379b77-9cf5-dece-191e-60c4e9518b93@amd.com \
--to=thomas.lendacky@amd.com \
--cc=dionnaglaze@google.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.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