RFC spapr: Implement H_TPM_COMM for accessing host TPM device
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 12 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | docs/specs: initial spec summary for Ultravisor-related hcallsdocs/ | +74 | 4 replies | |
| 2/2 | spapr: initial implementation for H_TPM_COMM hcallhw/ hw/ hw/ +2 more | +173 | 7 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Qemu-devel] [RFC PATCH 0/2] spapr: Implement H_TPM_COMM for accessing host TPM device
These patches are also available at:
https://github.com/mdroth/qemu/commits/spapr-tpm-hcall-v0
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 Guests 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 Guest using the host's TPM hardware.
More details are provided in the spec summary introduced in patch 1.
docs/specs/ppc-spapr-uv-hcalls.txt | 74 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/ppc/Makefile.objs | 1 + hw/ppc/spapr.c | 27 +++++++++++++++++++++++++++ hw/ppc/spapr_hcall_tpm.c | 135 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/ppc/trace-events | 4 ++++ include/hw/ppc/spapr.h | 7 ++++++- 6 files changed, 247 insertions(+), 1 deletion(-)