Re: [edk2-devel] 回复: [PATCH V4 00/10] Introduce Lazy-accept for Tdx guest

[Ni, Ray]

Can OS call AcceptMemory protocol for those ranges that are not accepted?

> -----Original Message-----
> From: Xu, Min M <min.m.xu at intel.com>
> Sent: Monday, October 10, 2022 11:08 AM
> To: devel at edk2.groups.io; Dionna Amalie Glaze <dionnaglaze at google.com>;
> Gao, Liming <gaoliming at byosoft.com.cn>
> Cc: Gao, Zhichao <zhichao.gao at intel.com>; Ni, Ray <ray.ni at intel.com>;
> Aktas, Erdem <erdemaktas at google.com>; 'Gerd Hoffmann'
> <kraxel at redhat.com>; 'James Bottomley' <jejb at linux.ibm.com>; Yao,
> Jiewen <jiewen.yao at intel.com>; 'Tom Lendacky'
> <thomas.lendacky at amd.com>; Gao, Jiaqi <jiaqi.gao at intel.com>; Wang, Jian
> J <jian.j.wang at intel.com>; Liu, Zhiguang <zhiguang.liu at intel.com>; Kinney,
> Michael D <michael.d.kinney at intel.com>; Xu, Min M <min.m.xu at intel.com>
> Subject: RE: [edk2-devel] 回复: [PATCH V4 00/10] Introduce Lazy-accept for
> Tdx guest
> 
> On October 10, 2022 10:28 AM, Gao Liming wrote:
> >
> > Min:
> >   I have no comments for new unaccepted resource type and unaccepted
> gcd
> > type. In fact, they are mapping to UEFI EfiUnacceptedMemoryType.
> >
> >   For new protocol EfiMemoryAcceptProtocol, I see another patch serial
> > https://edk2.groups.io/g/devel/message/94763 base on it to introduce
> > ACCEPT_ALL_UNACCEPTED_MEMORY_PROTOCOL. Can these two
> protocols
> > be combined into one?
> >
> EfiMemoryAcceptProtocol looks like this:
> typedef
> EFI_STATUS
> (EFIAPI *EDKII_ACCEPT_MEMORY)(
>   IN  EDKII_MEMORY_ACCEPT_PROTOCOL  *This,
>   IN  EFI_PHYSICAL_ADDRESS                          StartAddress,
>   IN  UINTN                                                         Size
>   );
> This protocol is called to accept the memory based on the input start address
> and size.
> 
> While ACCEPT_ALL_UNACCEPTED_MEMORY_PROTOCOL looks like below:
> typedef
> EFI_STATUS
> (EFIAPI *BZ3987_DISABLE_ACCEPT_ALL_UNACCEPTED_MEMORY)(
>   IN  BZ3987_ACCEPT_ALL_UNACCEPTED_MEMORY_PROTOCOL  *This
> );
> According to its description (https://edk2.groups.io/g/devel/message/94768)
> this protocol is used to disable the behavior of accepting all unaccepted
> memory. And it is designed to be called by the OS loader, not EDK2 itself.
> 
> I am afraid these 2 protocols cannot be combined into one.
> 
> Dionna what's your thought?
> 
> Thanks
> Min


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#94870): https://edk2.groups.io/g/devel/message/94870
Mute This Topic: https://groups.io/mt/94229046/1813853
Group Owner: devel+owner at edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [edk2-devel-archive at redhat.com]
-=-=-=-=-=-=-=-=-=-=-=-