public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Min Xu" <min.m.xu@intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Aktas, Erdem" <erdemaktas@google.com>,
	James Bottomley <jejb@linux.ibm.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Michael Roth <michael.roth@amd.com>
Subject: Re: [PATCH V4 06/12] OvmfPkg/PeilessStartupLib: Build GuidHob for Tdx measurement
Date: Sat, 28 Jan 2023 11:55:00 +0000	[thread overview]
Message-ID: <PH0PR11MB50640362DEEB1851EBF92C6BC5CD9@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230127075419.72x2sbvn2fcau3jw@sirius.home.kraxel.org>

On January 27, 2023 3:54 PM, Gerd Hoffmann wrote:
> On Fri, Jan 27, 2023 at 08:11:00AM +0800, Min Xu wrote:
> > From: Min M Xu <min.m.xu@intel.com>
> >
> > BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4243
> >
> > 2 new functions are added in PeilessStartupLib/IntelTdx.c.
> >  - BuildTdxMeasurementGuidHob
> >  - InternalBuildGuidHobForTdxMeasurement
> >
> > These 2 functions build GuidHob for Tdx measurement.
> 
> But you don't use them anywhere?  The point of splitting the patches is not
> only to simplify review, but also to simplify testing (and in case a bug shows
> up later finding it with bisecting).
> 
> So, current state of the code is:
> 
> There are MeasureHobList() + MeasureFvImage(), doing measurement and
> logging in one go, using TpmMeasureAndLogData().  Problem is this doesn't
> work in SEC, so you want split.
> 
> So, you add TdxHelperMeasureTdHob (doing the measurement part of
> MeasureHobList) and TdxHelperMeasureCfvImage (likewise doing the
> measurement part of MeasureFvImage) and logging both is handled by
> TdxHelperBuildGuidHobForTdxMeasurement().
> 
> So I think the series should have:
> 
>   (1) One or more patches doing cleanups (like reusing the struct).
>   (2) A patch removing MeasureHobList and adding TdxHelperMeasureTdHob
>       with the first half of TdxHelperBuildGuidHobForTdxMeasurement
>   (3) A patch removing MeasureFvImage and adding
> TdxHelperMeasureCfvImage
>       with the second half of TdxHelperBuildGuidHobForTdxMeasurement
>   (4) A patch moving the code from PlatformInitLib to TdxHelperLib.
>   (5) A patch moving the calls to TdxHelperMeasureTdHob and
>       TdxHelperMeasureCfvImage to SEC.
>   (6) A patch adding the Tdxhelper* calls to OvmfPkgX64.

Thanks for the suggestion. The patches will be re-organized in the next version.

Thanks
Min

  parent reply	other threads:[~2023-01-28 11:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27  0:10 [PATCH V4 00/12] Enable Tdx measurement in OvmfPkgX64 Min Xu
2023-01-27  0:10 ` [PATCH V4 01/12] OvmfPkg: Add Tdx measurement data structure in WorkArea Min Xu
2023-01-27  0:10 ` [PATCH V4 02/12] OvmfPkg/IntelTdx: Add TdxHelperLibNull Min Xu
2023-01-27  0:10 ` [PATCH V4 03/12] OvmfPkg/IntelTdx: Add SecTdxHelperLib Min Xu
2023-01-27  0:10 ` [PATCH V4 04/12] OvmfPkg/IntelTdx: Update tdx measurement in SEC phase Min Xu
2023-01-27  0:10 ` [PATCH V4 05/12] OvmfPkg/PeilessStartupLib: Update the define of FV_HANDOFF_TABLE_POINTERS2 Min Xu
2023-01-27  0:11 ` [PATCH V4 06/12] OvmfPkg/PeilessStartupLib: Build GuidHob for Tdx measurement Min Xu
2023-01-27  7:54   ` Gerd Hoffmann
2023-01-27 11:30     ` Min Xu
2023-01-27 11:49       ` Gerd Hoffmann
2023-01-28 11:55     ` Min Xu [this message]
2023-01-27  0:11 ` [PATCH V4 07/12] OvmfPkg/PeilessStartupLib: Call TdxHelperBuildGuidHobForTdxMeasurement Min Xu
2023-01-27  0:11 ` [PATCH V4 08/12] OvmfPkg/TdxHelperLib: Implement TdxHelperBuildGuidHobForTdxMeasurement Min Xu
2023-01-27  0:11 ` [PATCH V4 09/12] OvmfPkg: Enable Tdx measurement in OvmfPkgX64 Min Xu
2023-01-27  0:11 ` [PATCH V4 10/12] OvmfPkg/IntelTdx: Add PeiTdxHelperLib Min Xu
2023-01-27  0:11 ` [PATCH V4 11/12] OvmfPkg/PlatformPei: Build GuidHob for Tdx measurement Min Xu
2023-01-27  0:11 ` [PATCH V4 12/12] OvmfPkg/TdxHelperLib: Implement TdxHelperProcessTdHob Min Xu

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=PH0PR11MB50640362DEEB1851EBF92C6BC5CD9@PH0PR11MB5064.namprd11.prod.outlook.com \
    --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