On 10/14/21 1:41 AM, Gerd Hoffmann via groups.io wrote: > On Wed, Oct 13, 2021 at 11:57:03AM -0500, Brijesh Singh wrote: >> BZ: >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.tianocore.org%2Fshow_bug.cgi%3Fid%3D3275&data=04%7C01%7Cbrijesh.singh%40amd.com%7C45efbf71c7bc43fab38408d98eee7260%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637697977052800369%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2M1RTR8HQOAcpxA7tlWs%2B5uF%2Bn1JaLAFvagSn7v4SNw%3D&reserved=0 >> >> Previous commit introduced a generic confidential computing PCD that can >> determine whether AMD SEV-ES is enabled. Update the MpInitLib to drop the >> PcdSevEsIsEnabled in favor of PcdConfidentialComputingAttr. > Is there anything that guarantees MpLib initializes after PlatformPei so > it can depend on the PCD (see discussion in tdx thread) ? At least in the current Ovmf implementation the PlatformPei must initialize some of the PCDs used by the MpLibInit such as PcdCpuBootLogicalProcessorNumber and other AP related PCD. PlatformPei uses the Qemu FW_CFG to get the number of APs etc needed by the MpLibInit, so, I believe its safe to say that MpLib initializes after the PlatformPei. > > thanks, > Gerd > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#82055): https://edk2.groups.io/g/devel/message/82055 Mute This Topic: https://groups.io/mt/86292908/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
