Buildresult: powerpc-next/mvme5100_defconfig/powerpc-gcc4.9 built on Jul 29 2020, 03:43

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Jul 29 2020, 03:43
Duration:	0:00:54.230063
Builder:	ka2
Revision:	ppc64/kexec_file: fix kexec load failure with lack of memory hole (`eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f)`
Target:	powerpc-next/mvme5100_defconfig/powerpc-gcc4.9
Branch:	powerpc-next
Compiler:	powerpc-gcc4.9 (powerpc64-linux-gcc (GCC) 4.9.4 / GNU ld (GNU Binutils) 2.29.1.20170915)
Config:	mvme5100_defconfig (download)
Log:	Download original No warnings found in log. Full Log # git rev-parse -q --verify eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f^{commit} eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f already have revision, skipping fetch # git checkout -q -f -B kisskb eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f # git clean -qxdf # < git log -1 # commit eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f # Author: Hari Bathini <hbathini@linux.ibm.com> # Date: Mon Jul 27 01:10:28 2020 +0530 # # ppc64/kexec_file: fix kexec load failure with lack of memory hole # # The kexec purgatory has to run in real mode. Only the first memory # block maybe accessible in real mode. And, unlike the case with panic # kernel, no memory is set aside for regular kexec load. Another thing # to note is, the memory for crashkernel is reserved at an offset of # 128MB. So, when crashkernel memory is reserved, the memory ranges to # load kexec segments shrink further as the generic code only looks for # memblock free memory ranges and in all likelihood only a tiny bit of # memory from 0 to 128MB would be available to load kexec segments. # # With kdump being used by default in general, kexec file load is likely # to fail almost always. This can be fixed by changing the memory hole # lookup logic for regular kexec to use the same method as kdump. This # would mean that most kexec segments will overlap with crashkernel # memory region. That should still be ok as the pages, whose destination # address isn't available while loading, are placed in an intermediate # location till a flush to the actual destination address happens during # kexec boot sequence. # # Signed-off-by: Hari Bathini <hbathini@linux.ibm.com> # Tested-by: Pingfan Liu <piliu@redhat.com> # Reviewed-by: Thiago Jung Bauermann <bauerman@linux.ibm.com> # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # Link: https://lore.kernel.org/r/159579242226.5790.13933486642004084417.stgit@hbathini # < /opt/cross/kisskb/korg/gcc-4.9.4-nolibc/powerpc64-linux/bin/powerpc64-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-4.9.4-nolibc/powerpc64-linux/bin/powerpc64-linux-ld --version # < git log --format=%s --max-count=1 eaa567ccaf3a2a7b14ffa38af4bd09613aa1830f # < make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_mvme5100_defconfig_powerpc-gcc4.9 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-4.9.4-nolibc/powerpc64-linux/bin/powerpc64-linux- mvme5100_defconfig # < make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_mvme5100_defconfig_powerpc-gcc4.9 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-4.9.4-nolibc/powerpc64-linux/bin/powerpc64-linux- help # make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_mvme5100_defconfig_powerpc-gcc4.9 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-4.9.4-nolibc/powerpc64-linux/bin/powerpc64-linux- olddefconfig # make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_mvme5100_defconfig_powerpc-gcc4.9 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-4.9.4-nolibc/powerpc64-linux/bin/powerpc64-linux- INFO: Uncompressed kernel (size 0x445e0c) overlaps the address of the wrapper(0x400000) INFO: Fixing the link_address of wrapper to (0x500000) Completed OK # rm -rf /kisskb/build/powerpc-next_mvme5100_defconfig_powerpc-gcc4.9 # Build took: 0:00:54.230063

© Michael Ellerman 2006-2018.