Re: [PATCH v2 2/2] x86/xen: dont add memory above max allowed allocation

2019-02-06 Thread Juergen Gross
On 01/02/2019 19:46, Boris Ostrovsky wrote: > On 1/30/19 3:22 AM, Juergen Gross wrote: >> Don't allow memory to be added above the allowed maximum allocation >> limit set by Xen. >> >> Trying to do so would result in cases like the following: >> >> [ 584.559652] [ cut here

Re: [PATCH v2 2/2] x86/xen: dont add memory above max allowed allocation

2019-02-01 Thread Boris Ostrovsky
On 1/30/19 3:22 AM, Juergen Gross wrote: > Don't allow memory to be added above the allowed maximum allocation > limit set by Xen. > > Trying to do so would result in cases like the following: > > [ 584.559652] [ cut here ] > [ 584.564897] WARNING: CPU: 2 PID: 1 at

Re: [PATCH v2 2/2] x86/xen: dont add memory above max allowed allocation

2019-01-30 Thread William Kucharski
> On Jan 30, 2019, at 1:22 AM, Juergen Gross wrote: > > +#ifdef CONFIG_MEMORY_HOTPLUG > + /* > + * Don't allow adding memory not in E820 map while > + * booting the system. Once the balloon driver is up > + *

[PATCH v2 2/2] x86/xen: dont add memory above max allowed allocation

2019-01-30 Thread Juergen Gross
Don't allow memory to be added above the allowed maximum allocation limit set by Xen. Trying to do so would result in cases like the following: [ 584.559652] [ cut here ] [ 584.564897] WARNING: CPU: 2 PID: 1 at ../arch/x86/xen/multicalls.c:129