lkml.org 
[lkml]   [2008]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] x86: Find offset for crashkernel reservation automatically
On Mon, Jul 14, 2008 at 2:44 AM, Eric W. Biederman
<ebiederm@xmission.com> wrote:
> Bernhard Walle <bwalle@suse.de> writes:
>
>> * Yinghai Lu [2008-07-14 00:11]:
>>>
>>> should use min_t(u64, 1ULL<<32, max_low_pfn<<PAGE_SHIFT) replace ULONG_MAX
>>
>> Shouldn't we use min_t(u64, ULLONG_MAX, max_low_pfn<<PAGE_SHIFT), i.e.
>> should we really limit the crashkernel to a 32 bit address on a 64 bit
>> system?
>
> We should use the lowest physical address that meets our size and
> alignment constraints. However there is no reason to make this be <
> 4G or even < 1G. The worst case is that we reserve an area the kdump
> kernel can't run out of. However /sbin/kexec should check for that as
> the kexec on panic code is not necessarily a linux kernel.

for 64bit, kdump can start from address above 4g with bzImage?

YH


\
 
 \ /
  Last update: 2008-07-14 19:09    [W:0.785 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site