[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D0BBE00.3010602@kernel.org>
Date: Fri, 17 Dec 2010 11:46:08 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Vivek Goyal <vgoyal@...hat.com>,
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 11:39 AM, H. Peter Anvin wrote:
> On 12/17/2010 10:21 AM, Yinghai Lu wrote:
>>>>
>>>> Do we have actual testing for how high the 64-bit kernel will load?
>>>
>>> I will do some experiments on my box today and let you know.
>>
>> if bzImage is used, it is 896M.
>>
>
> Why? 896 MiB is a 32-bit kernel limitation which doesn't have anything
> to do with the bzImage format.
>
> So unless there is something going on here, I suspect you're just plain
> flat wrong.
kexec-tools have some checking when it loads bzImage.
Yinghai
--
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