From: Richard Henderson <richard.henderson@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [PULL 0/6 for-6.2] AMD SEV patches
Date: Thu, 18 Nov 2021 17:37:28 +0100 [thread overview]
Message-ID: <14c735d5-9b36-07f7-08f3-268ae05c3a04@linaro.org> (raw)
In-Reply-To: <20211118133532.2029166-1-berrange@redhat.com>
On 11/18/21 2:35 PM, Daniel P. Berrangé wrote:
> The following changes since commit 0055ecca84cb948c935224b4f7ca1ceb26209790:
>
> Merge tag 'vfio-fixes-20211117.0' of git://github.com/awilliam/qemu-vfio into staging (2021-11-18 09:39:47 +0100)
>
> are available in the Git repository at:
>
> https://gitlab.com/berrange/qemu tags/sev-hashes-pull-request
>
> for you to fetch changes up to 58603ba2680fa35eade630e4b040e96953a11021:
>
> target/i386/sev: Replace qemu_map_ram_ptr with address_space_map (2021-11-18 13:28:32 +0000)
>
> ----------------------------------------------------------------
> Add property for requesting AMD SEV measured kernel launch
>
> - The 'sev-guest' object gains a boolean 'kernel-hashes' property
> which must be enabled to request a measured kernel launch.
>
> ----------------------------------------------------------------
>
> Dov Murik (6):
> qapi/qom,target/i386: sev-guest: Introduce kernel-hashes=on|off option
> target/i386/sev: Add kernel hashes only if sev-guest.kernel-hashes=on
> target/i386/sev: Rephrase error message when no hashes table in guest
> firmware
> target/i386/sev: Fail when invalid hashes table area detected
> target/i386/sev: Perform padding calculations at compile-time
> target/i386/sev: Replace qemu_map_ram_ptr with address_space_map
>
> qapi/qom.json | 7 ++++-
> qemu-options.hx | 6 +++-
> target/i386/sev.c | 79 +++++++++++++++++++++++++++++++++++++++--------
> 3 files changed, 77 insertions(+), 15 deletions(-)
Applied, thanks.
r~
prev parent reply other threads:[~2021-11-18 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 13:35 [PULL 0/6 for-6.2] AMD SEV patches Daniel P. Berrangé
2021-11-18 13:35 ` [PULL 1/6] qapi/qom, target/i386: sev-guest: Introduce kernel-hashes=on|off option Daniel P. Berrangé
2021-11-18 13:35 ` [PULL 2/6] target/i386/sev: Add kernel hashes only if sev-guest.kernel-hashes=on Daniel P. Berrangé
2021-11-18 13:35 ` [PULL 3/6] target/i386/sev: Rephrase error message when no hashes table in guest firmware Daniel P. Berrangé
2021-11-18 13:35 ` [PULL 4/6] target/i386/sev: Fail when invalid hashes table area detected Daniel P. Berrangé
2021-11-18 13:35 ` [PULL 5/6] target/i386/sev: Perform padding calculations at compile-time Daniel P. Berrangé
2021-11-18 13:35 ` [PULL 6/6] target/i386/sev: Replace qemu_map_ram_ptr with address_space_map Daniel P. Berrangé
2021-11-18 16:37 ` Richard Henderson [this message]
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=14c735d5-9b36-07f7-08f3-268ae05c3a04@linaro.org \
--to=richard.henderson@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).