From: Connor Kuehl <ckuehl@redhat.com>
To: qemu-devel@nongnu.org
Cc: thomas.lendacky@amd.com, brijesh.singh@amd.com,
ehabkost@redhat.com, richard.henderson@linaro.org,
pbonzini@redhat.com, "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH 2/2] [RESEND] sev: add missing firmware error conditions
Date: Fri, 30 Apr 2021 08:48:30 -0500 [thread overview]
Message-ID: <20210430134830.254741-3-ckuehl@redhat.com> (raw)
In-Reply-To: <20210430134830.254741-1-ckuehl@redhat.com>
The SEV userspace header[1] exports a couple of other error conditions that
aren't listed in QEMU's SEV implementation, so let's just round out the
list.
[1] linux-headers/linux/psp-sev.h
Signed-off-by: Connor Kuehl <ckuehl@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
---
target/i386/sev.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/target/i386/sev.c b/target/i386/sev.c
index 9e2e47012f..dfafd3b543 100644
--- a/target/i386/sev.c
+++ b/target/i386/sev.c
@@ -111,6 +111,8 @@ static const char *const sev_fw_errlist[] = {
[SEV_RET_HWSEV_RET_UNSAFE] = "Hardware unsafe",
[SEV_RET_UNSUPPORTED] = "Feature not supported",
[SEV_RET_INVALID_PARAM] = "Invalid parameter",
+ [SEV_RET_RESOURCE_LIMIT] = "Required firmware resource depleted",
+ [SEV_RET_SECURE_DATA_INVALID] = "Part-specific integrity check failure",
};
#define SEV_FW_MAX_ERROR ARRAY_SIZE(sev_fw_errlist)
--
2.30.2
next prev parent reply other threads:[~2021-04-30 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 13:48 [PATCH 0/2] [RESEND] SEV firmware error list touchups Connor Kuehl
2021-04-30 13:48 ` [PATCH 1/2] [RESEND] sev: use explicit indices for mapping firmware error codes to strings Connor Kuehl
2021-04-30 13:48 ` Connor Kuehl [this message]
2021-05-11 7:35 ` [PATCH 0/2] [RESEND] SEV firmware error list touchups Philippe Mathieu-Daudé
2021-05-27 21:36 ` Philippe Mathieu-Daudé
2021-05-31 20:09 ` Eduardo Habkost
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=20210430134830.254741-3-ckuehl@redhat.com \
--to=ckuehl@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.