WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

[Xen-ia64-devel] Re: Question about memory initial interface modificatio

To: "Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>
Subject: [Xen-ia64-devel] Re: Question about memory initial interface modification in Xend?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 09 Nov 2006 08:26:51 +0000
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 09 Nov 2006 00:26:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <58A36151585E4047913F40517D307BAE03C1AA@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccDqXRWvsGnr7FCTrmLhU1ZAt+PVwAL1nR5
Thread-topic: Question about memory initial interface modification in Xend?
User-agent: Microsoft-Entourage/11.2.5.060620
On 9/11/06 2:47 am, "Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx> wrote:

Hi Keir:
         In your patch 12199 you modified memory initial interface in Xend and suggested IA64 not allocating memory by xend. But I noticed IA32 still use this interface, is there any difference?

IA32 now allocates memory in xc_linux_build and xc_hvm_build. The domain_memory_increase_reservation() has been entirely removed from xend.

It should be easy to switch IA64 to the same. Pretty much all it involves is a call to xc_domain_populate_physmap() instead of xc_domain_get_pfn_list(). It ends up being less code.

 -- Keir
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
<Prev in Thread] Current Thread [Next in Thread>