From: "Daniel P. Berrangé" <berrange@redhat.com>
To: tobin@linux.ibm.com
Cc: thomas.lendacky@amd.com, brijesh.singh@amd.com,
jejb@linux.ibm.com, tobin@ibm.com, qemu-devel@nongnu.org,
dgilbert@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH v4] sev: add sev-inject-launch-secret
Date: Wed, 14 Oct 2020 16:30:15 +0100 [thread overview]
Message-ID: <20201014153015.GH115189@redhat.com> (raw)
In-Reply-To: <20201014151739.4722-1-tobin@linux.ibm.com>
On Wed, Oct 14, 2020 at 11:17:39AM -0400, tobin@linux.ibm.com wrote:
> From: Tobin Feldman-Fitzthum <tobin@linux.ibm.com>
>
> AMD SEV allows a guest owner to inject a secret blob
> into the memory of a virtual machine. The secret is
> encrypted with the SEV Transport Encryption Key and
> integrity is guaranteed with the Transport Integrity
> Key. Although QEMU facilitates the injection of the
> launch secret, it cannot access the secret.
>
> Signed-off-by: Tobin Feldman-Fitzthum <tobin@linux.ibm.com>
> ---
> include/monitor/monitor.h | 3 ++
> include/sysemu/sev.h | 2 ++
> monitor/misc.c | 8 +++---
> qapi/misc-target.json | 18 ++++++++++++
> target/i386/monitor.c | 7 +++++
> target/i386/sev-stub.c | 5 ++++
> target/i386/sev.c | 60 +++++++++++++++++++++++++++++++++++++++
> target/i386/trace-events | 1 +
> 8 files changed, 100 insertions(+), 4 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-10-14 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 15:17 [PATCH v4] sev: add sev-inject-launch-secret tobin
2020-10-14 15:30 ` Daniel P. Berrangé [this message]
2020-10-14 15:42 ` Brijesh Singh
2020-10-14 17:06 ` Tobin Feldman-Fitzthum
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=20201014153015.GH115189@redhat.com \
--to=berrange@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=dgilbert@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.lendacky@amd.com \
--cc=tobin@ibm.com \
--cc=tobin@linux.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 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.