Hi Min,<br /><br />
<blockquote>+/**<br />+ Transfer the incoming HobList for the TD to the final HobList for Dxe.<br />+ The Hobs transferred in this function are ResourceDescriptor hob and<br />+ MemoryAllocation hob.<br />+<br />+ @param[in] VmmHobList The Hoblist pass the firmware<br />+<br />+**/<br />+VOID<br />+EFIAPI<br />+TransferTdxHobList (<br />+ VOID<br />+ )<br />+{<br />+ EFI_PEI_HOB_POINTERS Hob;<br />+ EFI_RESOURCE_ATTRIBUTE_TYPE ResourceAttribute;<br />+<br />+ //<br />+ // PcdOvmfSecGhcbBase is used as the TD_HOB in Tdx guest.<br />+ //<br />+ Hob.Raw = (UINT8 *)(UINTN)PcdGet32 (PcdOvmfSecGhcbBase);<br />+ while (!END_OF_HOB_LIST (Hob)) {<br />+ switch (Hob.Header-&gt;HobType) {<br />+ case EFI_HOB_TYPE_RESOURCE_DESCRIPTOR:<br />+ ResourceAttribute = Hob.ResourceDescriptor-&gt;ResourceAttribute;<br />+</blockquote>
I am trying to test TDX functionality with config A patches (Wave1 + Wave2.v4) and with the above function passing the memory attributes of the resources in TD HOB list (Originally populated by VMM) as is to DXE phase,<br />Function CoreInitializeMemoryServices (from ./MdeModulePkg/Core/Dxe/Gcd/Gcd.c) is not able to find any resources with&nbsp;TESTED_MEMORY_ATTRIBUTES&nbsp;set.<br /><br />For config A, Is there an expectation from VMM to set&nbsp;TESTED_MEMORY_ATTRIBUTES for each System Memory resource passed via TD HOB list or should this function<br />be appending&nbsp;TESTED_MEMORY_ATTRIBUTES to existing resource attributes?<br /><br />Regards,<br />Vishal