[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] libxl: don't needlessly report "highmem" in use
On Tue, Jan 07, 2020 at 03:58:07PM +0100, Jan Beulich wrote: > Due to the unconditional updating of dom->highmem_end in > libxl__domain_device_construct_rdm() I've observed on a 2Gb HVM guest > with a passed through device (without overly large BARs, and with no RDM > ranges at all) > > (d2) RAM in high memory; setting high_mem resource base to 100000000 > ... > (d2) E820 table: > (d2) [00]: 00000000:00000000 - 00000000:000a0000: RAM > (d2) HOLE: 00000000:000a0000 - 00000000:000d0000 > (d2) [01]: 00000000:000d0000 - 00000000:00100000: RESERVED > (d2) [02]: 00000000:00100000 - 00000000:7f800000: RAM > (d2) HOLE: 00000000:7f800000 - 00000000:fc000000 > (d2) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED > (d2) [04]: 00000001:00000000 - 00000001:00000000: RAM > > both of which aren't really appropriate in this case. Arrange for this > to not happen. Indeed. We shouldn't need to move RAM to high address in this configuration. Acked-by: Wei Liu <wl@xxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |