Re: [Xen-devel] Re: [RFC PATCH 07/35] Make LOAD_OFFSET defined by subarch
- From: Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>
- Date: Fri, 12 May 2006 09:38:40 +0100
On Fri, May 12, 2006 at 08:47:13AM +0200, Jan Beulich wrote:
I've updated our loader to support this now, so that this patch is
no longer necessary. I have at the same time added a new field to
xen_guest which allows specifying the entry point, allowing us to have
a different entry point when running the kernel image on Xen.
Why do you need a separate entry point here? The code should be able to figure out which mode it is run in without
problems...
I think it's the cleanest way to have different startup code for
native and non-native in the same kernel. But even if that's not
needed (for Linux), then you can have it point at the same address.
It is also always pointing to a virtual address, while the elf header
one now points to a physical address which doesn't make much sense
in the environment we start the kernel.
christian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [RFC PATCH 00/35] Xen i386 paravirtualization support
- From: Chris Wright
- [RFC PATCH 07/35] Make LOAD_OFFSET defined by subarch
- From: Chris Wright
- Re: [RFC PATCH 07/35] Make LOAD_OFFSET defined by subarch
- From: Zachary Amsden
- Re: [RFC PATCH 07/35] Make LOAD_OFFSET defined by subarch
- From: Christian Limpach
- [Xen-devel] Re: [RFC PATCH 07/35] Make LOAD_OFFSET defined by subarch
- From: Jan Beulich
- [RFC PATCH 00/35] Xen i386 paravirtualization support
- Prev by Date: [PATCH] Silly bitmap size accounting fix
- Next by Date: Re: rt20 patch question
- Previous by thread: [Xen-devel] Re: [RFC PATCH 07/35] Make LOAD_OFFSET defined by subarch
- Next by thread: [RFC PATCH 34/35] Add the Xen virtual network device driver.
- Index(es):
Relevant Pages
|
