On September 1, 2022 11:56 PM, Gerd Hoffmann wrote: > > > Lazy accept page can be controlled in build time like below: > > -D LAZY_ACCEPT_PARTIAL_MEM=512 > > > > The unit is MB. If it is 0 then it means Lazy-accept is turned off. > > > > Lazy-accept is turned off by default in OvmfPkgX64. > > Lazy-accept is turned on with 512MB by default in IntelTdxX64. > > > + > > + > gUefiOvmfPkgTokenSpaceGuid.PcdLazyAcceptPartialMemorySize|$(LAZY_AC > C > > + EPT_PARTIAL_MEM) > > Hmm, cover letter says 0 means accept all memory below 4G > > Care to clarify? Is the commit message outdated? > > Also I think the discussion of the last revision ended with the agreement that > accepting all memory below 4G is a good idea because it simplifies the > workflow (no need to split low memory into accepted and unaccepted ranges > for example). > > So why we are again talking about accepting 512 MB ? > I may mis-understand the discussion of the last revision. So the agreement in first stage is that: 1. Accept all memory below 4G. 2. The PcdLazyAcceptPartialMemorySize is not needed in current stage. 3. The patch of "Pool and page functions accept memory when OOM occurs" is not needed. Because OOM will not occur in the situation of accepting all memory below 4G.
If that is correct, I will update the patches based on above agreements. Thanks Min -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#93075): https://edk2.groups.io/g/devel/message/93075 Mute This Topic: https://groups.io/mt/93285605/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
