On 12/10/13 06:51, Yao, Jiewen wrote: > I am not sure how you did it for Ovmf. > In general, we use below way for real platform, for your information only. > > 1) In code boot, a DXE phase platform driver allocates OS-Reserved Memory > type (EfiReservedType, or EfiAcpiNvs) for S3 PeiCore usage during code boot, > and save address and length.
This looks similar to what we're doing now for individual blocks (individual PCDs). > 2) In S3 boot, MemoryInit module, it looks for this information, and install > pei memory by using the saved information. > Then we can make sure all memory touched in S3 phase be reserved. Ah! Very interesting. So I would make the current PublishSystemMemory() call(s) -- we have two, for different emulators -- dependent on the boot mode. If we're on the S3 code path, then the system memory would correspond to the preallocated AcpiNVS area. Temporary RAM migration, allocations etc. would all be satisfied from that. I'll look into this. Thanks! Laszlo ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
