From: James Bottomley <jejb@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: thomas.lendacky@amd.com, ashish.kalra@amd.com,
brijesh.singh@amd.com, david.kaplan@amd.com, jejb@linux.ibm.com,
jon.grimm@amd.com, tobin@ibm.com, frankeh@us.ibm.com,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
dovmurik@linux.vnet.ibm.com, Dov.Murik1@il.ibm.com,
pbonzini@redhat.com, berrange@redhat.com
Subject: [PATCH v2 0/2] sev: enable secret injection to a self described area in OVMF
Date: Mon, 14 Dec 2020 07:44:27 -0800 [thread overview]
Message-ID: <20201214154429.11023-1-jejb@linux.ibm.com> (raw)
v2: fix build issues and update comments. Also drop the first patch
which is now merged upstream
The two patches introduce a parser for the optional OVMF description
table which is placed just below the reset vector (the format of the
table is described in the patch itself) and also adds a hook to pull
out the description of the SEV secret area location and use it in
place of the sev-inject-launch-secret gpa.
James
---
James Bottomley (2):
pc: add parser for OVMF reset block
sev: update sev-inject-launch-secret to make gpa optional
hw/i386/pc_sysfw.c | 106 ++++++++++++++++++++++++++++++++++++++++++
include/hw/i386/pc.h | 4 ++
qapi/misc-target.json | 2 +-
target/i386/monitor.c | 27 ++++++++++-
4 files changed, 137 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-12-14 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 15:44 James Bottomley [this message]
2020-12-14 15:44 ` [PATCH v2 1/2] pc: add parser for OVMF reset block James Bottomley
2021-01-26 12:22 ` Dr. David Alan Gilbert
2021-02-02 23:30 ` James Bottomley
2021-02-03 9:14 ` Dr. David Alan Gilbert
2020-12-14 15:44 ` [PATCH v2 2/2] sev: update sev-inject-launch-secret to make gpa optional James Bottomley
2021-01-26 12:32 ` Dr. David Alan Gilbert
2021-02-02 23:35 ` James Bottomley
2021-02-03 9:06 ` Dr. David Alan Gilbert
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=20201214154429.11023-1-jejb@linux.ibm.com \
--to=jejb@linux.ibm.com \
--cc=Dov.Murik1@il.ibm.com \
--cc=ashish.kalra@amd.com \
--cc=berrange@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=david.kaplan@amd.com \
--cc=dgilbert@redhat.com \
--cc=dovmurik@linux.vnet.ibm.com \
--cc=frankeh@us.ibm.com \
--cc=jon.grimm@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.lendacky@amd.com \
--cc=tobin@ibm.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;
as well as URLs for NNTP newsgroup(s).