Commit 64c98e7f authored by Malcolm Crossley's avatar Malcolm Crossley Committed by David Vrabel
Browse files

x86/xen: Do not clip xen_e820_map to xen_e820_map_entries when sanitizing map



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 sanitize_e820_map to use the full size of the allocated E820
array.
Signed-off-by: default avatarMalcolm Crossley <malcolm.crossley@citrix.com>
Reviewed-by: default avatarBoris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: default avatarDavid Vrabel <david.vrabel@citrix.com>
parent 0b34a166
...@@ -798,7 +798,7 @@ char * __init xen_memory_setup(void) ...@@ -798,7 +798,7 @@ char * __init xen_memory_setup(void)
xen_ignore_unusable(); xen_ignore_unusable();
/* Make sure the Xen-supplied memory map is well-ordered. */ /* Make sure the Xen-supplied memory map is well-ordered. */
sanitize_e820_map(xen_e820_map, xen_e820_map_entries, sanitize_e820_map(xen_e820_map, ARRAY_SIZE(xen_e820_map),
&xen_e820_map_entries); &xen_e820_map_entries);
max_pages = xen_get_max_pages(); max_pages = xen_get_max_pages();
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment