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
* Eric W. Biederman [2008-07-14 11:41]:
>
> "Yinghai Lu" <yhlu.kernel@gmail.com> writes:
>
> > On Mon, Jul 14, 2008 at 10:30 AM, Eric W. Biederman
> > <ebiederm@xmission.com> wrote:
> >> "Yinghai Lu" <yhlu.kernel@gmail.com> writes:
> >>
> >>> for 64bit, kdump can start from address above 4g with bzImage?
> >>
> >> I think the boot protocol was properly updated for that, it was in the
> >> original drafts. A relocatable kernel with a 64bit entry point.
> >>
> >> I do know that the 64bit code is ready to do that.
> >
> > but bzImage for 64bit still use 32bit entries, except kexec could
> > uncompress the bzImage like xen domain builder.
>
> From the standpoint of the crashdump option it doesn't matter.
> As the vmlinux supports it, and bzImage could easily support it,
> the decompresser is 64bit code.
>
> If bzImage doesn't support it that is a bug we will have to
> correct one of these years when it actually matters.

But such checks belong into kexec itself, not into the kernel.


Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development


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