forked from Minki/linux
xen: limit memory to architectural maximum
When a pv-domain (including dom0) is started it tries to size it's p2m list according to the maximum possible memory amount it ever can achieve. Limit the initial maximum memory size to the architectural limit of the hardware in order to avoid overflows during remapping of memory. This problem will occur when dom0 is started with an initial memory size being a multiple of 1GB, but without specifying it's maximum memory size. The kernel must be configured without CONFIG_XEN_BALLOON_MEMORY_HOTPLUG for the problem to happen. Reported-by: Roger Pau Monné <roger.pau@citrix.com> Tested-by: Roger Pau Monné <roger.pau@citrix.com> Signed-off-by: Juergen Gross <jgross@suse.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
This commit is contained in:
parent
ab24507cfa
commit
cb9e444b5a
@ -531,7 +531,7 @@ static unsigned long __init xen_get_pages_limit(void)
|
||||
#ifdef CONFIG_X86_32
|
||||
limit = GB(64) / PAGE_SIZE;
|
||||
#else
|
||||
limit = ~0ul;
|
||||
limit = MAXMEM / PAGE_SIZE;
|
||||
if (!xen_initial_domain() && xen_512gb_limit)
|
||||
limit = GB(512) / PAGE_SIZE;
|
||||
#endif
|
||||
|
Loading…
Reference in New Issue
Block a user