From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH] Elf loader fixes Date: Wed, 22 Feb 2006 16:30:20 +0100 Message-ID: <43FC919C.76F0.0078.0@novell.com> References: <43FC4CF6.2010603@suse.de> <43FC6C62.76F0.0078.0@novell.com> <43FC7F59.7030503@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <43FC7F59.7030503@suse.de> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Gerd Hoffmann Cc: Xen devel list List-Id: xen-devel@lists.xenproject.org >>> Gerd Hoffmann 22.02.06 16:12:25 >>> >Jan Beulich wrote: >> I'm afraid this won't work for 64-bits, because of the way the vsyscall page gets set up there. If you dump the program >> headers you'll see that the respective segment is at an address close to the top of the address space, which would make >> the image appear to need nearly 2 Gb of memory (making the load fail if there's less than that available to the >> domain). > >Hmm, who sets up the vsyscall mapping right now? The linux kernel I >guess? Yes. >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. Jan