On 10/14/21 12:08 AM, Gerd Hoffmann wrote: > On Wed, Oct 13, 2021 at 11:56:45AM -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%7Cee86130b95964399c70b08d98ee17462%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637697921262987036%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=IkLqCEO9p%2FZxx4ryumEZzBvn8DCR%2Byxl%2Fd%2BdS5dqqbs%3D&reserved=0 >> >> The OvmfPkgX86 build reserves memory regions in MEMFD. The memory regions >> get accessed in the SEC phase. AMD SEV-SNP require that the guest's >> private memory be accepted or validated before access. >> >> Introduce a Guided metadata structure that describes the reserved memory >> regions. The VMM can locate the metadata structure by iterating through >> the reset vector guid and process the areas based on the platform >> specific requirements. > Acked-by: Gerd Hoffmann <kra...@redhat.com> > > (does it make sense to migrate over the existing SEV_FW_HASH_BLOCK_BASE > and SEV_LAUNCH_SECRET_BASE blocks?)
I don't see a strong reason t move over unless someone else sees a real need for it. We anyway have to maintain the backward compatibility because older qemu will look for those region through other GUID. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#82050): https://edk2.groups.io/g/devel/message/82050 Mute This Topic: https://groups.io/mt/86292887/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
