[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D0BCF32.8060400@zytor.com>
Date: Fri, 17 Dec 2010 12:59:30 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Vivek Goyal <vgoyal@...hat.com>
CC: Yinghai Lu <yinghai@...nel.org>,
Stanislaw Gruszka <sgruszka@...hat.com>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Maxim Uvarov <muvarov@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Neil Horman <nhorman@...hat.com>
Subject: Re: kdump broken on 2.6.37-rc4
On 12/17/2010 12:11 PM, Vivek Goyal wrote:
>>
>> Can we do this in the meantime, just so we fix the immediate problem?
>
> Peter, kexec-tools on 64bit currently seems to be allowing loding bzImage
> till 896MB. So I am not too keen it to reduce it to 768MB in kernel just
> because x86_64 could be booted from even higher addresses and somebody
> first has to do some auditing and experiments.
>
> IMHO, we should have 768MB limit for 32bit and continue with 896MB limit for
> 64bit and once somebody makes x86_64 boot from even higher address reliably
> then we can change both kernel and kexec-tools.
>
If we're splitting by architectures anyway, why not leave 32 bits at 512
MiB and thus making older crashkernels usable just in case someone has a
frozen toolset?
-hpa
--
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