toggle quoted messageShow quoted text
I am not sure if I can understand your comment -
"Some interfaces may need to use an architecture specific library, and some configuration options would need to be defined using PCDs."
Would you please be more specific?
From: Xu, Min M <email@example.com>
Sent: Thursday, October 14, 2021 1:41 PM
To: Sami Mujawar <Sami.Mujawar@arm.com>; firstname.lastname@example.org; Yao,
Cc: Kinney, Michael D <email@example.com>; Liming Gao
<firstname.lastname@example.org>; Liu, Zhiguang <email@example.com>; Wang,
Jian J <firstname.lastname@example.org>; Lu, Ken <email@example.com>; nd <firstname.lastname@example.org>
Subject: RE: [edk2-devel] [PATCH V2 0/3] Introduce TdProtocol into EDK2
On October 12, 2021 11:27 PM, Sami Mujawar wrote:
Hi Min,Thanks for your comments. Let me first discuss your feedback with our
Thank you for this patch.
I think it would greatly help if the EFI_TD_PROTOCOL is changed to something
more architecture neutral. As I understand, this patch series is removing the
dependency on TPM for measurement and is instead providing a lightweight
interface for extending measurements for Confidential Compute Architecture
Considering this, it would be good to generalise EFI_TD_PROTOCOL as a
Confidential Compute Architecture Measurement (CCAM) protocol.
In fact, your v2 series demonstrates this need with the introduction of
MEASURE_BOOT_PROTOCOLS in "[PATCH V2 2/3] SecurityPkg: Support
TdProtocol in DxeTpm2MeasureBootLib
As it stands, I feel most of the code can be reused/common. Some interfaces
may need to use an architecture specific library, and some configuration
options would need to be defined using PCDs.
Kindly let me know your thoughts.
architecture. We will reply to your proposal a bit later.