lkml.org 
[lkml]   [2021]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v16 02/11] x86: kdump: make the lower bound of crash kernel reservation consistent
    Date
    From: Chen Zhou <chenzhou10@huawei.com>

    The lower bounds of crash kernel reservation and crash kernel low
    reservation are different, use the consistent value CRASH_ALIGN.

    Suggested-by: Dave Young <dyoung@redhat.com>
    Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
    Tested-by: John Donnelly <John.p.donnelly@oracle.com>
    ---
    arch/x86/kernel/setup.c | 3 ++-
    1 file changed, 2 insertions(+), 1 deletion(-)

    diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
    index b7286d4c389dd33..a31352d8c404f6c 100644
    --- a/arch/x86/kernel/setup.c
    +++ b/arch/x86/kernel/setup.c
    @@ -441,7 +441,8 @@ static int __init reserve_crashkernel_low(void)
    return 0;
    }

    - low_base = memblock_phys_alloc_range(low_size, CRASH_ALIGN, 0, CRASH_ADDR_LOW_MAX);
    + low_base = memblock_phys_alloc_range(low_size, CRASH_ALIGN, CRASH_ALIGN,
    + CRASH_ADDR_LOW_MAX);
    if (!low_base) {
    pr_err("Cannot reserve %ldMB crashkernel low memory, please try smaller size.\n",
    (unsigned long)(low_size >> 20));
    --
    2.25.1
    \
     
     \ /
      Last update: 2021-11-23 13:50    [W:4.259 / U:0.300 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site