[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130114154354.GA27740@liondog.tnic>
Date: Mon, 14 Jan 2013 16:43:54 +0100
From: Borislav Petkov <bp@...en8.de>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jan Kiszka <jan.kiszka@....de>,
Jason Wessel <jason.wessel@...driver.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7u1 27/31] x86, kdump: remove crashkernel range find
limit for 64bit
On Thu, Jan 03, 2013 at 04:48:47PM -0800, Yinghai Lu wrote:
> Now kexeced kernel/ramdisk could be above 4g, so remove 896 limit for
> 64bit.
>
> Signed-off-by: Yinghai Lu <yinghai@...nel.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 c58497e..6adbc45 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.
Does this mean that kexec-tools has been fixed too?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists