xen: limit memory to architectural maximum
Subsystems (2)
Juergen Gross
maintainerPATCH 1/1 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.
--- arch/x86/xen/setup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/xen/setup.c +1 -1
@@ -537,7 +537,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
Signature · 1 line
2.1.4
El 04/09/15 a les 14.18, Juergen Gross ha escrit:
Quoted 6 lines
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.
Quoted 7 lines
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_HOTPLUGfor the problem to happen.Reported-by Roger Pau Monné <[email protected]>Signed-off-by Juergen Gross <[email protected]>
David Vrabel
AppliedQuoted 10 lines · Juergen Gross
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_HOTPLUGfor the problem to happen.
Applied to for-linus-4.3, thanks.
David