RFC Enlightened vTPM support for SVSM on SEV-SNP
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 of 3 patches 7 repliesIn review
2 of 3 patches are in this archive. The cover letter announces 3.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | tpm: add generic platform devicedrivers/ drivers/ drivers/ +1 more | +59 | 2 replies | |
| 3/3 | edk2: Add SVSM based vTPMOvmfPkg/ SecurityPkg/ SecurityPkg/ +7 more | +218 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/3] Enlightened vTPM support for SVSM on SEV-SNP
This is a sketch for how a fully enlightened vTPM driver would work. The idea is that the SVSM responds on function 8 to vTPM requests, so we use that to send down a buffer which is modified on return (the buffer must be big enough, so the agreed protocol is it should be a page in length, which is larger than any possible TPM command or response). The protocol used is the MSSIM one which is self describing in terms of length, so there's no need to transmit sizes (it also leaves room for expansion to localities and cancellation, which is useful in the light of discussions). A NULL in place of the buffer is a probe and the SVSM call simply returns SVSM_SUCCESS without doing anything. This can be used to probe for vTPM support because any other return would indicate no vTPM present.
Hopefully IBM will publish the new svsm-vtpm repo shortly, but we're still working with the old CRB based one at the moment, so it may take some time.
The three following patches are for two different repos. Patch 1 will apply to any upstream Linux kernel, Patch 2 requires the non-upstream sev-snp repo and patch 3 is against the non upstream sev-snp edk repo.
James