From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [PATCH] Elf loader fixes Date: Wed, 22 Feb 2006 17:10:42 +0100 Message-ID: <43FC8D02.5020908@suse.de> References: <43FC4CF6.2010603@suse.de> <43FC6C62.76F0.0078.0@novell.com> <43FC7F59.7030503@suse.de> <43FC919C.76F0.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <43FC919C.76F0.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: Xen devel list List-Id: xen-devel@lists.xenproject.org >> The elf kernel loader certainly doesn't look like it cares much >> about virtual address (other than VIRT_BASE) ... > > Correct. And the same applies to boot loaders. Well, the difference between xen and other boot loaders is that xen boots the kernel with paging already enabled ... Right now it's completely broken: the loader works only with virtual addresses in the paddr header field. It can't stay that way, especially if we'll want to have kexec working with xenlinux kernels some day ;) As I see things there are basically two ways to fixup this: Either create a simple linear mapping using paddr + VIRT_BASE, which would be pretty close to the current behaviour (and other boot loaders). Or do a complete virtual memory setup, which probably can't be done without major changes in the domain builder ... cheers, Gerd -- Gerd 'just married' Hoffmann I'm the hacker formerly known as Gerd Knorr. http://www.suse.de/~kraxel/just-married.jpeg