Hi,

>
> Likewise the expected behavior.  For example whenever the protocol driver
> or the memory core should update the GCD maps.
>
Yes EFI_DXE_SERVICES can be used by EFI_ACCEPT_MEMORY, which contains CoreAddMemorySpace() & CoreRemoveMemorySpace().
>
> Yes.  Same for booting the OS, the kernel must have enough memory so it
> can boot up to the point where the driver handling the lazy page accept loads.
>
> We should also define how we hand over memory range state from one
> stage to the other (see also my reply to the sev-snp series posted yesterday)
> so ovmf knows which ranges are accepted/validated already.
>
Resource HOB type EFI_RESOURCE_MEMORY_UNACCEPTED is used to indicate unaccepted memory range and is passed from HOB producer to DXE.
And there's a new type EfiUnacceptedMemory in EFI_MEMORY_TYPE to pass information to OS, which has already been updated to UEFI spec.
You can see the details in the Definitions page of slides: https://edk2.groups.io/g/devel/files/Designs/2021/0830/TDVF%20Lazy%20Page%20Accept%28v0.7%29.pptx


Thank you,
Jiaqi