Re: [PATCH 2/3] X86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

2017-11-14 Thread Dave Young
On 11/15/17 at 01:47pm, Baoquan He wrote: > Hi Dave, > > Thanks for your effort to push this into upstream. While I have one > concern, please see the inline comments. > > On 10/24/17 at 01:31pm, Dave Young wrote: > > Now crashkernel=X will fail if there's not enough memory at low region > > (bel

Re: [PATCH 2/3] X86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

2017-11-14 Thread Baoquan He
Hi Dave, Thanks for your effort to push this into upstream. While I have one concern, please see the inline comments. On 10/24/17 at 01:31pm, Dave Young wrote: > Now crashkernel=X will fail if there's not enough memory at low region > (below 896M) when trying to reserve large memory size. One ca

Re: [PATCH 2/3] X86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

2017-11-12 Thread Dave Young
On 10/24/17 at 01:31pm, Dave Young wrote: > Now crashkernel=X will fail if there's not enough memory at low region > (below 896M) when trying to reserve large memory size. One can use > crashkernel=xM,high to reserve it at high region (>4G) but it is more > convinient to improve crashkernel=X to:

[PATCH 2/3] X86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

2017-10-23 Thread dyoung
Now crashkernel=X will fail if there's not enough memory at low region (below 896M) when trying to reserve large memory size. One can use crashkernel=xM,high to reserve it at high region (>4G) but it is more convinient to improve crashkernel=X to: - First try to reserve X below 896M (for being

Re: x86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

2017-10-23 Thread Dave Young
On 10/20/17 at 01:52pm, Dave Young wrote: > Now crashkernel=X will fail if there's not enough memory at low region > (below 896M) when trying to reserve large memory size. One can use > crashkernel=xM,high to reserve it at high region (>4G) but it is more > convinient to improve crashkernel=X to:

Re: x86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

2017-10-22 Thread Dave Young
On 10/21/17 at 12:20am, Yinghai Lu wrote: > On Thu, Oct 19, 2017 at 10:52 PM, Dave Young wrote: > > Now crashkernel=X will fail if there's not enough memory at low region > > (below 896M) when trying to reserve large memory size. One can use > > crashkernel=xM,high to reserve it at high region (>

Re: x86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

2017-10-21 Thread Yinghai Lu
On Thu, Oct 19, 2017 at 10:52 PM, Dave Young wrote: > Now crashkernel=X will fail if there's not enough memory at low region > (below 896M) when trying to reserve large memory size. One can use > crashkernel=xM,high to reserve it at high region (>4G) but it is more > convinient to improve crashke

x86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

2017-10-19 Thread Dave Young
Now crashkernel=X will fail if there's not enough memory at low region (below 896M) when trying to reserve large memory size. One can use crashkernel=xM,high to reserve it at high region (>4G) but it is more convinient to improve crashkernel=X to: - First try to reserve X below 896M (for being