Re: [Xen-devel] [PATCH] x86/xen: Do not clip xen_e820_map to xen_e820_map_entries when sanitizing map

2015-09-28 Thread David Vrabel
On 28/09/15 11:36, Malcolm Crossley wrote: > Sanitizing the e820 map may produce extra E820 entries which would result in > the topmost E820 entries being removed. The removed entries would typically > include the top E820 usable RAM region and thus result in the domain having > signicantly less

Re: [Xen-devel] [PATCH] x86/xen: Do not clip xen_e820_map to xen_e820_map_entries when sanitizing map

2015-09-28 Thread Boris Ostrovsky
On 09/28/2015 06:36 AM, Malcolm Crossley wrote: Sanitizing the e820 map may produce extra E820 entries which would result in the topmost E820 entries being removed. The removed entries would typically include the top E820 usable RAM region and thus result in the domain having signicantly less

[Xen-devel] [PATCH] x86/xen: Do not clip xen_e820_map to xen_e820_map_entries when sanitizing map

2015-09-28 Thread Malcolm Crossley
Sanitizing the e820 map may produce extra E820 entries which would result in the topmost E820 entries being removed. The removed entries would typically include the top E820 usable RAM region and thus result in the domain having signicantly less RAM available to it. Fix by allowing