[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45233B58.1050208@zytor.com>
Date: Tue, 03 Oct 2006 21:40:56 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: vgoyal@...ibm.com
CC: Andrew Morton <akpm@...l.org>,
linux kernel mailing list <linux-kernel@...r.kernel.org>,
Reloc Kernel List <fastboot@...ts.osdl.org>,
ebiederm@...ssion.com, ak@...e.de, horms@...ge.net.au,
lace@...kratochvil.net, magnus.damm@...il.com, lwang@...hat.com,
dzickus@...hat.com, maneesh@...ibm.com
Subject: Re: [PATCH 12/12] i386 boot: Add an ELF header to bzImage
Vivek Goyal wrote:
>
> Hi Andrew,
>
> Right now I don't have access to my test machine. Tomorrow morning,
> very first thing I am going to try it out with your config file.
>
> This patch just adds and ELF header to bzImage which is not even used
> by grub.
>
Oh yes, it will be. See below.
> So without this patch you are able to boot the kernel on your laptop?
Danger, Will Robinson. GRUB, Etherboot, and a whole bunch of other boot
loaders will recognize an ELF binary and load it as such. They will
typically load it as an executable (not a relocatable object) -- I doubt
many of them check that appropriate part of the ELF header -- so unless
your kernel can be safely loaded *AND RUN* in that mode this is not
going to work.
The entrypoint is going to be a major headache, since the standard
kernel is entered in real mode, whereas an ELF file will typically be
entered in protected mode, quite possibly using the C calling convention
to pass the command line as (argc, argv). God only knows how they're
going to deal with an initrd.
It may very well be that the ELF magic number has to be obfuscated.
-hpa
-
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