On 03/12/19 at 12:48pm, Kirill A. Shutemov wrote:
> > #ifdef CONFIG_X86_32
> > # define CRASH_ADDR_LOW_MAX(512 << 20)
> > # define CRASH_ADDR_HIGH_MAX (512 << 20)
> > #else
> > # define CRASH_ADDR_LOW_MAX(896UL << 20)
> > -# define CRASH_ADDR_HIGH_MAX MAXMEM
> > +#
On Tue, Mar 12, 2019 at 08:50:04AM +0800, Baoquan He wrote:
> Restrict kdump to only reserve crashkernel below 64TB. Since the kdump
> jumping may be from 5-level to 4-level, and the kdump kernel is put
> above 64TB in 5-level kernel, then the jumping will fail. And the
> crashkernel reservation is
Restrict kdump to only reserve crashkernel below 64TB. Since the kdump
jumping may be from 5-level to 4-level, and the kdump kernel is put
above 64TB in 5-level kernel, then the jumping will fail. And the
crashkernel reservation is done during the 1st kernel bootup, there's
no way to detect the pag
3 matches
Mail list logo
