[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <463918CF.4000202@goop.org>
Date: Wed, 02 May 2007 16:03:43 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Gerd Hoffmann <kraxel@...hat.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Jeff Garzik <jeff@...zik.org>, patches@...-64.org,
linux-kernel@...r.kernel.org, Vivek Goyal <vgoyal@...ibm.com>,
virtualization <virtualization@...ts.linux-foundation.org>
Subject: Re: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for
relocatable bzImage
H. Peter Anvin wrote:
> I don't know if that would break any programs that are currently
> bypassing the setup. The existing setup protocol definitely allows
> invoking an entry point which isn't 0x100000 (rather, the 32-bit
> entrypoint is defined by code32_start); I'm not sure how Eric's
> relocatable kernel patches (2.05 protocol) affect that, mostly because I
> haven't seen any boot loaders which actually use it so I can't comment
> on what their code looks like.
Yes, I'd expect that code32_start would point into the ELF text
segment. You could align things so that the entrypoint is still
actually 0x100000, or bump it up a bit to fit the ELF headers. I have
to admit I don't quite understand how all that fits together at the moment.
J
-
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