>>> On 01.12.14 at 10:24, <tiejun.c...@intel.com> wrote: > We need to check to reserve all reserved device memory maps in e820 > to avoid any potential guest memory conflict. > > Currently, if we can't insert RDM entries directly, we may need to handle > several ranges as follows: > a. Fixed Ranges --> BUG() > lowmem_reserved_base-0xA0000: reserved by BIOS implementation, > BIOS region, > RESERVED_MEMBASE ~ 0x100000000, > b. RAM or RAM:Hole -> Try to reserve
I continue to be unconvinced of the overall approach: The domain builder continues to populate these regions when it shouldn't. Yet once it doesn't, it would be most natural to simply communicate the RAM regions to hvmloader, and hvmloader would use just that to build the E820 table (and subsequently assign BARs). Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
