On Mon, Aug 09, 2021 at 10:13:16AM +0800, Baoquan He wrote:
> On 08/06/21 at 07:21pm, Kevin Mitchell wrote:
> > In linux-5.2, the following commit allows the kdump kernel to be loaded
> > at a higher address than 896M
> >
> > 9ca5c8e632ce ("x86/kdump: Hav
additional check for an x86_64 image kexeced by an
x86_64 kernel in the i386 loader and bumps the limit to the maximum
addressable 4G in that case.
Signed-off-by: Kevin Mitchell
---
kexec/arch/i386/kexec-bzImage.c | 41 ++---
1 file changed, 28 insertions(+), 13 deletion
Hi,
As a space-saving strategy for our embedded boot environment, we use an i386
kexec binary to load our x86_64 kdump kernel from an x86_64 system kernel. This
worked great up until linux-5.2, which included the commit
9ca5c8e632ce ("x86/kdump: Have crashkernel=X reserve under 4G by
default")