[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-ia64-devel] Re: Question about memory initial interface modification in Xend?


  • To: "Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>
  • 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
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AccDqXRWvsGnr7FCTrmLhU1ZAt+PVwAL1nR5
  • Thread-topic: Question about memory initial interface modification in Xend?

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.