public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Min Xu <min.m.xu@intel.com>
Cc: devel@edk2.groups.io, Jiewen Yao <jiewen.yao@intel.com>,
	Jian J Wang <jian.j.wang@intel.com>,
	Erdem Aktas <erdemaktas@google.com>,
	James Bottomley <jejb@linux.ibm.com>,
	Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH 0/3] Introduce SecTpmMeasurementLibTdx
Date: Tue, 7 Jun 2022 12:34:43 +0200	[thread overview]
Message-ID: <20220607103443.l2dmwr36ducf4xxx@sirius.home.kraxel.org> (raw)
In-Reply-To: <cover.1654390043.git.min.m.xu@intel.com>

On Sun, Jun 05, 2022 at 09:02:45AM +0800, Min Xu wrote:
> SecTpmMeasurementLibTdx is an instance of TpmMeasurement lib in SEC phase.
> It provides RTMR based measurement functions for Intel Tdx guest.
> 
> Commit a708536dce introduces SecMeasurementLibTdx which provides the same
> functions. But it is not an instance of TpmMeasurementLib.
> We have updated DxeTpmMeasurementLib (which is an instance of
> TpmMeasurementLib) to support RTMR based measurement. To make the design
> consistent, SecTpmMeasurementLibTdx is introduced. After that
> SecMeasurementLibTdx is removed.

So, what is the difference?  Just make the calling convention compatible
with TpmMeasurementLib?

take care,
  Gerd


  parent reply	other threads:[~2022-06-07 10:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05  1:02 [PATCH 0/3] Introduce SecTpmMeasurementLibTdx Min Xu
2022-06-05  1:02 ` [PATCH 1/3] Security: Add SecTpmMeasurementLibTdx Min Xu
2022-06-05  1:02 ` [PATCH 2/3] OvmfPkg: Implement MeasureHobList/MeasureFvImage Min Xu
2022-06-05  1:02 ` [PATCH 3/3] OvmfPkg: Delete SecMeasurementLibTdx Min Xu
2022-06-05  2:09 ` [PATCH 0/3] Introduce SecTpmMeasurementLibTdx Yao, Jiewen
2022-06-07 10:34 ` Gerd Hoffmann [this message]
2022-06-07 11:37   ` Yao, Jiewen
     [not found] ` <16F5977C8286B4B6.24312@groups.io>
2022-06-07 11:33   ` [edk2-devel] " Yao, Jiewen

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-list 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=20220607103443.l2dmwr36ducf4xxx@sirius.home.kraxel.org \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox