From: David Gibson <david@gibson.dropbear.id.au>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: linuxram@us.ibm.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-4.2 v2 0/2] spapr: Implement H_TPM_COMM for accessing host TPM device
Date: Thu, 18 Jul 2019 14:37:43 +1000 [thread overview]
Message-ID: <20190718043743.GJ8468@umbus.fritz.box> (raw)
In-Reply-To: <20190717205842.17827-1-mdroth@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]
On Wed, Jul 17, 2019 at 03:58:40PM -0500, Michael Roth wrote:
> These patches are based on ppc-for-4.2 and are also available at:
>
> https://github.com/mdroth/qemu/commits/spapr-tpm-hcall-v2
>
> This patchset implements the H_TPM_COMM hypercall, which provides a way
> for an Ultravisor to pass raw TPM commands on to a host's TPM device,
> either directly or through a TPM Resource Manager (needed to support
> multiple guests).
>
> Secure VMs running on an Ultravisor have a symmetric key that is
> encrypted using a public key that is bound to a trusted host's TPM
> hardware. This hypercall provides a means to decrypt the symmetric
> key on behalf of a Secure VMs using the host's TPM hardware.
>
> More details are provided in the spec summary introduced in patch 1.
LGTM, applied to ppc-for-4.2.
>
> Changes since v1:
> - use separate hcall table for SVM hcall range (David)
> - document reserved hcall range in ppc-spapr-uv-hcalls.txt
>
> Changes since RFC/v0:
> - configure TPM path via -device spapr-tpm-proxy instead of -machine (David)
> - return H_FUNCTION (not H_RESOURCE) if TPM has not been configured (David)
> - drop use of global for storing TPM FD (David)
> - fix checkpatch errors relating to case statement indents, newlines in
> error_report(), and lines over 80.
> - fix some minor typos in documentation
> - rebased on ppc-for-4.2
>
> docs/specs/ppc-spapr-uv-hcalls.txt | 76 +++++++++++++++++++++++++++
> hw/ppc/Makefile.objs | 1 +
> hw/ppc/spapr.c | 33 +++++++++++-
> hw/ppc/spapr_hcall.c | 13 +++++
> hw/ppc/spapr_tpm_proxy.c | 176 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/ppc/trace-events | 4 ++
> include/hw/ppc/spapr.h | 11 ++++
> include/hw/ppc/spapr_tpm_proxy.h | 31 +++++++++++
> 8 files changed, 344 insertions(+), 1 deletion(-)
>
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-07-18 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 20:58 [Qemu-devel] [PATCH for-4.2 v2 0/2] spapr: Implement H_TPM_COMM for accessing host TPM device Michael Roth
2019-07-17 20:58 ` [Qemu-devel] [PATCH for-4.2 v2 1/2] docs/specs: initial spec summary for Ultravisor-related hcalls Michael Roth
2019-07-17 20:58 ` [Qemu-devel] [PATCH for-4.2 v2 2/2] spapr: initial implementation for H_TPM_COMM/spapr-tpm-proxy Michael Roth
2019-07-18 4:37 ` David Gibson [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=20190718043743.GJ8468@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=linuxram@us.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).