[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080714204748.07b06e30@halley.suse.de>
Date: Mon, 14 Jul 2008 20:47:48 +0200
From: Bernhard Walle <bwalle@...e.de>
To: ebiederm@...ssion.com (Eric W. Biederman)
Cc: "Yinghai Lu" <yhlu.kernel@...il.com>,
"Vivek Goyal" <vgoyal@...hat.com>, kexec@...ts.infradead.org,
x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Find offset for crashkernel reservation
automatically
* Eric W. Biederman [2008-07-14 11:41]:
>
> "Yinghai Lu" <yhlu.kernel@...il.com> writes:
>
> > On Mon, Jul 14, 2008 at 10:30 AM, Eric W. Biederman
> > <ebiederm@...ssion.com> wrote:
> >> "Yinghai Lu" <yhlu.kernel@...il.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
--
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