[svsm-devel] SVSM Development Call April 3rd, 2024

[Yao, Jiewen]

Thank you to confirm that James.

Yes, I will sync internally to understand the process for submitting patch to coconut-svsm.

Thank you
Yao, Jiewen

> -----Original Message-----
> From: James Bottomley <jejb at linux.ibm.com>
> Sent: Wednesday, April 3, 2024 8:19 PM
> To: Yao, Jiewen <jiewen.yao at intel.com>; Jörg Rödel <joro at 8bytes.org>; svsm-
> devel at coconut-svsm.dev; linux-coco at lists.linux.dev
> Subject: Re: SVSM Development Call April 3rd, 2024
> 
> On Wed, 2024-04-03 at 11:59 +0000, Yao, Jiewen wrote:
> > Hi Jorg
> > Probably you already notice that I have raised the question on vTPM
> > interface in coconut-svsm.
> >
> > I have explained how we did the POC in a secure way for TD-
> > partitioning with TPM CRB buffer.
> > Jeremi Piotrowski also explained the mechanism to expose vTPM through
> > TPM CRB MMIO. In Intel, we still don't understand why SVSM must use a
> > specific vTPM protocol, but not use TCG defined TPM2 CRB buffer
> > directly.
> 
> Nobody has said *must*.  The enlightened interface was designed after
> we had all the trouble with the CRB one outlined in the previous email
> thread, so that's what this pull request has.  However, this being open
> source nothing prevents you submitting a pull request for a functioning
> CRB interface if that's what you want.
> 
> James