From: Christian Limpach Subject: Re: Re: [RFC PATCH 07/35] Make LOAD_OFFSET defined by subarch Date: Fri, 12 May 2006 09:38:40 +0100 Message-ID: <20060512083839.GI7834@cl.cam.ac.uk> References: <20060509084945.373541000@sous-sol.org> <20060509085150.509458000@sous-sol.org> <44627733.4010305@vmware.com> <20060511164300.GA7834@cl.cam.ac.uk> <44644B91.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <44644B91.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: Zachary Amsden , xen-devel@lists.xensource.com, Ian Pratt , linux-kernel@vger.kernel.org, Chris Wright , virtualization@lists.osdl.org List-Id: xen-devel@lists.xenproject.org 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