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
Hi,
>
> I think we need clearly document what service can be used in
> EFI_ACCEPT_MEMORY.
> For example, can we use memory allocation service, GCD service, or MP
> service?
GCD service is provided by EFI_DXE_SERVICES, it can be used by
EFI_ACCEPT_MEMORY (So updating the GCD memory map in the pr
On Fri, Sep 03, 2021 at 12:31:57AM +, Yao, Jiewen wrote:
> Hi
> It is good idea to have a protocol to abstract TDX and SEV.
>
> I think we need clearly document what service can be used in
> EFI_ACCEPT_MEMORY.
> For example, can we use memory allocation service, GCD service, or MP service?
L
mmer, Vincent ;
> Justen, Jordan L ; Xu, Min M
> Subject: RE: [edk2-devel] [RFC] Design review for Lazy Page Accept in TDVF
>
>
> On Tuesday, August 31, 2021 2:11 PM, Gerd Hoffmann wrote:
> > > Motivation: Intel TDX provides memory encryption and integrity
> > &g
On Tuesday, August 31, 2021 2:11 PM, Gerd Hoffmann wrote:
> > Motivation: Intel TDX provides memory encryption and integrity
> > multi-tenancy for hardware protection. A TD-guest uses TDCALL to
> > accept shared memory as private. However, accept whole system memory
> > may take a long time which
On Mon, Aug 30, 2021 at 07:49:27AM +, Gao, Jiaqi wrote:
> Motivation: Intel TDX provides memory encryption and integrity
> multi-tenancy for hardware protection. A TD-guest uses TDCALL to
> accept shared memory as private. However, accept whole system memory
> may take a long time which will ha
Motivation:
Intel TDX provides memory encryption and integrity multi-tenancy for hardware
protection. A TD-guest uses TDCALL to accept shared memory as private. However,
accept whole system memory may take a long time which will have an adverse
impact on the boot time performance. We introduce L
