[PATCH v7 0/7] kexec: put bzImage and ramdisk above 4G for x86 64bit

Simon Horman horms at verge.net.au
Fri Jan 25 04:08:18 EST 2013


On Thu, Jan 24, 2013 at 12:44:17PM -0800, Yinghai Lu wrote:
> Now we have limit kdump reserved under 896M, because kexec has the limitation.
> and also bzImage need to stay under 4g.
> 
> kernel parts changes could be found at:
>         git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-x86-boot
> 
> here patches are for kexec tools to load bzImage and ramdisk above 4G
> acccording to new added boot header fields.
> 
> -v3: address review from Eric to use locate_hole at first.
>      use xloadflags instead.
> -v4: remove the restriction about bzImage not crossing GB boundary.
>      add real-mode fix for bzImage.
>      add --entry-32bit and --real-mode for skip bzImage64.
> -v5: use USE_EXT_BOOT_PARAMS bit in xloadflags.
> -v6: use sentinel instead of USE_EXT_BOOT_PARAMS.
>      add crashkernel_low support
> -v7: Separate bootloader id setting in another patch

Hi Yinghai, Hi All,

my current thinking with regards to this is that I would like to take
these changes into the kexec-tools tree once there is consensus and
kernel portions have been accepted. If that makes sense please let me know
when those conditions have been met. Otherwise lets discuss a different
strategy.



More information about the kexec mailing list