From: ebiederm@xmission.com (Eric W. Biederman)
To: vgoyal@in.ibm.com
Cc: Etienne Lorrain <etienne_lorrain@yahoo.fr>,
       "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Re : [PATCH] Compressed ia32 ELF file generation for loading by Gujin 1/3
References: <20070208094831.56920.qmail@web26908.mail.ukl.yahoo.com>
	<20070208113706.GB14039@in.ibm.com>
Date: Thu, 08 Feb 2007 05:10:43 -0700
In-Reply-To: <20070208113706.GB14039@in.ibm.com> (Vivek Goyal's message of
	"Thu, 8 Feb 2007 17:07:06 +0530")
Message-ID: <m1bqk4alz0.fsf@ebiederm.dsl.xmission.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 954
Lines: 23

Vivek Goyal <vgoyal@in.ibm.com> writes:

> Kexec as a boot loader allows to load both ELF vmlinux file or bzImage.
> Hence for kdump, a user got the flexibility to either use vmlinux or 
> bzImage for dump captruing purposes. Hence I am concerned about both. 
>
> If real mode code is linked with vmlinux, then kdump will be broken.
>
> bzImage is relocatable. If a new kernel image format is introduced
> (compressed ELF), then I will prefer it to be a relocatable one
> (if possible).

If we do make the real mode code findable from a set of ELF headers
instead of a weird program header it should be an ELF note in the note
segment that tells us where to find or possibly contains the real mode
code.

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/