linux-kernel - Re: [PATCH] x86: Find offset for crashkernel reservation automatically

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <86802c440807141117q218fdd61w1216dc6ded72252a@mail.gmail.com>
Date:	Mon, 14 Jul 2008 11:17:16 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Bernhard Walle" <bwalle@...e.de>,
	"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

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.

YH
--
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/