search for: e820_sanitize

Displaying 4 results from an estimated 4 matches for "e820_sanitize".

2011 Dec 08
4
memory map issues with PV PCI passthrough
...00000000c9c00000 (usable) (XEN) 00000000c9f00000 - 00000000ca000000 (reserved) (XEN) 00000000cb000000 - 00000000cf200000 (reserved) (XEN) 00000000fed1c000 - 00000000fed30000 (reserved) (XEN) 00000000ffc00000 - 00000000ffc20000 (reserved) (XEN) 0000000100000000 - 000000042e000000 (usable) When e820_sanitize is called on this memory map to create a PV domain, the resulting map has only one usable region (0-0xf00000) below 4GB, and Linux will not boot with this memory map. I have a patch that reworks e820_sanitize to include later RAM regions as valid RAM, which works as long as the domain being booted...
2012 Mar 27
1
[PATCH] libxl: Handle non-ballooned, zero slackmem properly for pci passthru
The e820_sanitize() function in libxl_pci.c expects one of its arguments to be non-zero; but since a recent changeset, it can typically expect *to be* zero. Since the zero case is handled properly, just remove the check. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> diff -r d35a117afa2f -r f9ce...
2013 Dec 01
70
[PATCH 00/13] Coverity fixes for libxl
Matthew Daley (13): libxl: fix unsigned less-than-0 comparison in e820_sanitize libxl: check for xc_domain_setmaxmem failure in libxl__build_pre libxl: correct file open success check in libxl__device_pci_reset libxl: don''t leak p in libxl__wait_for_backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s l...
2013 Jul 23
73
Bug: Limitation of <=2GB RAM in domU persists with 4.3.0
I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB