From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19PGef-0005O1-0I for qemu-devel@nongnu.org; Mon, 09 Jun 2003 03:01:21 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19PGeL-0004qm-3U for qemu-devel@nongnu.org; Mon, 09 Jun 2003 03:01:04 -0400 Received: from pizda.ninka.net ([216.101.162.242]) by monty-python.gnu.org with esmtp (Exim 4.20) id 19PGeE-0004XP-07 for qemu-devel@nongnu.org; Mon, 09 Jun 2003 03:00:54 -0400 Date: Sun, 08 Jun 2003 22:28:43 -0700 (PDT) Message-Id: <20030608.222843.41649210.davem@redhat.com> Subject: Re: [Qemu-devel] Sparc port From: "David S. Miller" In-Reply-To: <3EE362A6.6020103@free.fr> References: <3EE3158B.5090901@free.fr> <20030608.041917.21922788.davem@redhat.com> <3EE362A6.6020103@free.fr> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , To: qemu-devel@nongnu.org, fabrice.bellard@free.fr From: Fabrice Bellard Date: Sun, 08 Jun 2003 18:21:58 +0200 Is there any advantages in using QEMU as a sparc64 executable ? Do you think it would allow to let the full lower 32 bit address space to the x86 process ? Yes, but we need to use the correct code model so that the qemu executable and linked in libraries sits at or above 4GB. Even though I coded all of the sparc GCC support for all these code models, I have no idea how to foce the final executable to be force linked to use addresses > 4GB. Someone will need to experiment here.