RE: [Xen-ia64-devel] Question about memory initial interfacemodification in Xend?

["Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>]

Sorry, forget my word. I didn’t understand your codes early.

 

Good good study,day day up ! ^_^

-Wing(zhang xin)

 

OTC,Intel Corporation

---

From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Zhang, Xing Z
Sent: 2006年11月9日 10:48
To: Keir.Fraser@xxxxxxxxxxxx
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-ia64-devel] Question about memory initial interfacemodification in Xend?

 

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?

 

Below are your changes:

diff -r 96f51a000ed0 -r cf3d69ba5633 tools/python/xen/xend/XendDomainInfo.py

--- a/tools/python/xen/xend/XendDomainInfo.py   Wed Nov 01 18:32:45 2006 +0000

+++ b/tools/python/xen/xend/XendDomainInfo.py   Wed Nov 01 18:37:23 2006 +0000

@@ -1295,9 +1295,11 @@ class XendDomainInfo:

             shadow_cur = xc.shadow_mem_control(self.domid, shadow / 1024)

             self.info['shadow_memory'] = shadow_cur

 

-            # initial memory reservation

-            xc.domain_memory_increase_reservation(self.domid, reservation, 0,

-                                                  0)

+            # Initial memory reservation

+            if not (self._infoIsSet('image') and

+                    sxp.name(self.info['image']) == "hvm"):

+                xc.domain_memory_increase_reservation(

+                    self.domid, reservation, 0, 0)

 

             self._createChannels()

 

thxJ

 

Good good study,day day up ! ^_^

-Wing(zhang xin)

 

OTC,Intel Corporation

 

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel