From: James Bottomley <jejb@linux.ibm.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
"Jörg Rödel" <joro@8bytes.org>,
"svsm-devel@coconut-svsm.dev" <svsm-devel@coconut-svsm.dev>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>
Subject: Re: SVSM Development Call April 3rd, 2024
Date: Wed, 03 Apr 2024 08:18:46 -0400 [thread overview]
Message-ID: <74ff4091f24370033a349b72ba222a30ed039b6f.camel@linux.ibm.com> (raw)
In-Reply-To: <PH0PR11MB5879CA2156D964F9A3808E038C3D2@PH0PR11MB5879.namprd11.prod.outlook.com>
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
next prev parent reply other threads:[~2024-04-03 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 11:20 SVSM Development Call April 3rd, 2024 Jörg Rödel
2024-04-03 11:59 ` Yao, Jiewen
2024-04-03 12:18 ` James Bottomley [this message]
2024-04-03 13:11 ` Yao, Jiewen
2024-04-03 17:06 ` [svsm-devel] " Stefano Garzarella
2024-04-04 8:04 ` Jörg Rödel
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=74ff4091f24370033a349b72ba222a30ed039b6f.camel@linux.ibm.com \
--to=jejb@linux.ibm.com \
--cc=jiewen.yao@intel.com \
--cc=joro@8bytes.org \
--cc=linux-coco@lists.linux.dev \
--cc=svsm-devel@coconut-svsm.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.