From: "Min Xu" <min.m.xu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"kraxel@redhat.com" <kraxel@redhat.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Brijesh Singh <brijesh.singh@amd.com>,
"Aktas, Erdem" <erdemaktas@google.com>,
"James Bottomley" <jejb@linux.ibm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH V4 03/10] OvmfPkg: Update EFI_HOB_PLATFORM_INFO with more platform settings
Date: Wed, 2 Mar 2022 00:42:07 +0000 [thread overview]
Message-ID: <PH0PR11MB50644A09969328D7F73B4BFBC5039@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220301132652.mfdms3yevnnhpvp6@sirius.home.kraxel.org>
On March 1, 2022 9:27 PM, Gerd Hoffmann wrote:
>
> > @@ -15,6 +15,22 @@
> > typedef struct {
> > EFI_HOB_GUID_TYPE GuidHeader;
> > UINT16 HostBridgePciDevId;
> > + BOOLEAN PcdSetNxForStack;
> > +
> > + UINT64 PcdConfidentialComputingGuestAttr;
> > + BOOLEAN PcdIa32EferChangeAllowed;
> > + UINT64 PcdTdxSharedBitMask;
> > +
> > + UINT64 PcdPciMmio64Base;
> > + UINT64 PcdPciMmio64Size;
> > + UINT32 PcdPciMmio32Base;
> > + UINT32 PcdPciMmio32Size;
> > + UINT64 PcdPciIoBase;
> > + UINT64 PcdPciIoSize;
>
> Ah, here you add some of them to PLATFORM_INFO already ...
>
Actually there are 2 stages of EFI_HOB_PLATFORM_INFO.
The first stage is in Config-A (see https://github.com/mxu9/edk2/commit/30bdad7da340cb390c4a3ce0f49fc4324b72e60f). In this patch the EFI_HOB_PLATFORM_INFO is very simple. There are only 2 fields (GuidHeader + HostBridgePciDevId). Because Config-A boots with PEI and PCDs are set in OvmfPkg/PlatformPei. So we don't need to ask EFI_HOB_PLATFORM_INFO to carry other information.
Then we come to Config-B (the Pei-less boot). PCDs cannot be set in SEC phase. So we have to make EFI_HOB_PLATFORM_INFO to carry more information. See https://github.com/mxu9/edk2/commit/a1779386899369eb9c27517d72cc49870fd78b45
Since you're asking to simply pass around a EFI_HOB_PLATFORM_INFO pointer to the functions in PlatformInitLib, I am ok to define the complete EFI_HOB_PLATFORM_INFO structure in one patch.
Thanks
Min
next prev parent reply other threads:[~2022-03-02 0:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 8:16 [PATCH V4 00/10] Introduce TDVF Config-B (basic) in OvmfPkg Min Xu
2022-02-28 8:16 ` [PATCH V4 01/10] OvmfPkg: Add TdxWorkArea definition Min Xu
2022-02-28 8:16 ` [PATCH V4 02/10] OvmfPkg: Add PrePiHobListPointerLibTdx Min Xu
2022-02-28 8:16 ` [PATCH V4 03/10] OvmfPkg: Update EFI_HOB_PLATFORM_INFO with more platform settings Min Xu
2022-03-01 13:26 ` Gerd Hoffmann
2022-03-02 0:42 ` Min Xu [this message]
2022-02-28 8:16 ` [PATCH V4 04/10] OvmfPkg: Add PeilessStartupLib Min Xu
2022-03-01 13:31 ` Gerd Hoffmann
2022-03-02 1:20 ` Min Xu
2022-02-28 8:16 ` [PATCH V4 05/10] OvmfPkg/IntelTdx: Add Sec to bring up both Legacy and Tdx guest Min Xu
2022-02-28 8:16 ` [PATCH V4 06/10] OvmfPkg: Update TdxDxe to set TDX PCDs Min Xu
2022-02-28 8:16 ` [PATCH V4 07/10] OvmfPkg: Update DxeAcpiTimerLib to read HostBridgeDevId in PlatformInfoHob Min Xu
2022-02-28 8:16 ` [PATCH V4 08/10] OvmfPkg/IncompatiblePciDeviceSupportDxe: Ignore OptionRom in Td guest Min Xu
2022-03-01 13:44 ` Gerd Hoffmann
2022-03-02 1:21 ` Min Xu
2022-02-28 8:16 ` [PATCH V4 09/10] MdeModulePkg: Update PciEnumeratorSupport to ignore OptionRom if needed Min Xu
2022-03-18 13:41 ` Ni, Ray
2022-02-28 8:16 ` [PATCH V4 10/10] OvmfPkg: Introduce IntelTdxX64 for TDVF Config-B 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=PH0PR11MB50644A09969328D7F73B4BFBC5039@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