Re: [edk2-devel] [PATCH V3 09/12] OvmfPkg: Update ConstructFwHobList for lazy accept

2022-09-08 Thread Gerd Hoffmann
On Thu, Sep 08, 2022 at 12:48:05AM +, Xu, Min M wrote: > On September 7, 2022 1:42 PM, Gerd Hoffmann wrote: > > Hi, > > > > > + // > > > + // This memory region is split into 2 parts. The left part is > > > accepted. > > > + // > > > + PhysicalEnd= Ma

Re: [edk2-devel] [PATCH V3 09/12] OvmfPkg: Update ConstructFwHobList for lazy accept

2022-09-07 Thread Min Xu
On September 7, 2022 1:42 PM, Gerd Hoffmann wrote: > Hi, > > > + // > > + // This memory region is split into 2 parts. The left part is > > accepted. > > + // > > + PhysicalEnd= MaxAcceptedMemoryAddress; > > + ResourceLength = PhysicalEnd - Physi

Re: [edk2-devel] [PATCH V3 09/12] OvmfPkg: Update ConstructFwHobList for lazy accept

2022-09-06 Thread Gerd Hoffmann
Hi, > + // > + // This memory region is split into 2 parts. The left part is > accepted. > + // > + PhysicalEnd= MaxAcceptedMemoryAddress; > + ResourceLength = PhysicalEnd - PhysicalStart; Same comment here. Can't happen when all memory below 4

[edk2-devel] [PATCH V3 09/12] OvmfPkg: Update ConstructFwHobList for lazy accept

2022-09-05 Thread Min Xu
From: Min M Xu RFC: https://bugzilla.tianocore.org/show_bug.cgi?id=3937 In TDVF the hob list is constructed at the memory region which is the largest one below 4GB. After lazy accept is introduced, the MaxAcceptedMemoryAddress (which is tha max accpeted memory address in lazy accept) should be c