lkml.org 
[lkml]   [2013]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 29/35] x86, kdump: Remove crashkernel range find limit for 64bit
    Date
    Now kexeced kernel/ramdisk could be above 4g, so remove 896 limit for
    64bit.

    Signed-off-by: Yinghai Lu <yinghai@kernel.org>
    ---
    arch/x86/kernel/setup.c | 4 +---
    1 file changed, 1 insertion(+), 3 deletions(-)

    diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
    index 1f1c68f..563c99d 100644
    --- a/arch/x86/kernel/setup.c
    +++ b/arch/x86/kernel/setup.c
    @@ -501,13 +501,11 @@ static void __init memblock_x86_reserve_range_setup_data(void)
    /*
    * Keep the crash kernel below this limit. On 32 bits earlier kernels
    * would limit the kernel to the low 512 MiB due to mapping restrictions.
    - * On 64 bits, kexec-tools currently limits us to 896 MiB; increase this
    - * limit once kexec-tools are fixed.
    */
    #ifdef CONFIG_X86_32
    # define CRASH_KERNEL_ADDR_MAX (512 << 20)
    #else
    -# define CRASH_KERNEL_ADDR_MAX (896 << 20)
    +# define CRASH_KERNEL_ADDR_MAX MAXMEM
    #endif

    static void __init reserve_crashkernel(void)
    --
    1.7.10.4


    \
     
     \ /
      Last update: 2013-01-24 22:43    [W:4.168 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site