From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arun Sharma <arun.sharma@intel.com>
Subject: Are linker scripts needed?
Date: Sun, 22 May 2005 23:00:24 -0700
Message-ID: <42917178.8080502@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

In alt.bk.changesets.1.1508 Keir wrote:

> Some more ioemu config hardcoding. Our 'target arch' is always i386.
> Do we really need linker scripts??
> Signed-off-by: Keir Fraser <keir@xensource.com>

Yes, we do need linker scripts to support VMX guests with large memory 
(> 256MB). Without the linker scripts, we found instabilities with a 
512MB guest.

The reason for this is, qemu is mapping all of guest physical in it's 
address space. The linker script moves all of the qemu text/data/stack 
to the upper part of the user virtual to leave a large enough hole for 
mapping guest physical using xc_map_foreign.

Our intention is to use qemu for i386, x86-64 and ia64. The 
"target-i386-dm" is a misnomer and inherited from upstream. I should 
probably kill the concept of a "target architecture" since ioemu is cpu 
architecture independent right now.

	-Arun