Hi all Currently OVMF determines memory size by consulting CMOS, then it makes up memory map of its own.
Consulting memory size by reading CMOS limits the RAM size to 1TB as there's only 3 bytes from 0x5b-0x5d in CMOS, where the upper memory size is stored. And from Xen's point of view, OVMF should use the memory mapped passed by hypervisor (from hvmloader) instead of making up its own. To solve the above two problems all in one go, I plan to pass necessary information (io resource, mmio resource) to OVMF from Xen. I will construct the table / structure in hvmloader then hook up platform pei code when OVMF is running on Xen. The first thing that comes in mind is to reuse E820 table for memory map plus some extra fields for io / mmio resources. But I guess UEFI is the new world so stuffs like E820 from old world will be less popular. Any suggestion on existing table / data structure I can use? Thanks Wei. ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
