qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Dov Murik <dovmurik@linux.ibm.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
	Ashish Kalra <ashish.kalra@amd.com>,
	Brijesh Singh <brijesh.singh@amd.com>,
	James Bottomley <jejb@linux.ibm.com>,
	qemu-devel@nongnu.org,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Tobin Feldman-Fitzthum <tobin@linux.ibm.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] [RESEND] docs: Add spec of OVMF GUIDed table for SEV guests
Date: Tue, 4 Jan 2022 18:07:47 +0000	[thread overview]
Message-ID: <YdSM8wFu4xiRcKMt@redhat.com> (raw)
In-Reply-To: <20220103091413.2869-1-dovmurik@linux.ibm.com>

On Mon, Jan 03, 2022 at 11:14:13AM +0200, Dov Murik wrote:
> Add docs/specs/sev-guest-firmware.rst which describes the GUIDed table
> in the end of OVMF's image which is parsed by QEMU, and currently used
> to describe some values for SEV and SEV-ES guests.
> 
> Signed-off-by: Dov Murik <dovmurik@linux.ibm.com>
> ---
>  docs/specs/index.rst              |   1 +
>  docs/specs/sev-guest-firmware.rst | 125 ++++++++++++++++++++++++++++++
>  2 files changed, 126 insertions(+)
>  create mode 100644 docs/specs/sev-guest-firmware.rst

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 :|



  reply	other threads:[~2022-01-04 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  9:14 [PATCH] [RESEND] docs: Add spec of OVMF GUIDed table for SEV guests Dov Murik
2022-01-04 18:07 ` Daniel P. Berrangé [this message]
2022-02-15  6:21   ` Dov Murik
2022-03-07  0:13     ` Philippe Mathieu-Daudé
  -- strict thread matches above, loose matches on Subject: below --
2021-12-20 11:11 Dov Murik

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=YdSM8wFu4xiRcKMt@redhat.com \
    --to=berrange@redhat.com \
    --cc=ashish.kalra@amd.com \
    --cc=brijesh.singh@amd.com \
    --cc=dgilbert@redhat.com \
    --cc=dovmurik@linux.ibm.com \
    --cc=jejb@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thomas.lendacky@amd.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 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).