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

Re: [Xen-ia64-devel] [PATCH] Fix that guest can not get continuous memor

To: "Zhang, Yang" <yang.zhang@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel] [PATCH] Fix that guest can not get continuous memory for vhpt
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Mon, 2 Mar 2009 20:59:40 +0900
Cc: "xen-ia64-devel@xxxxxxxxxxxxxxxxxxx" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 02 Mar 2009 03:59:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <10C63FAD690C13458F0B32BCED571F1406D087F2@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/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <10C63FAD690C13458F0B32BCED571F1406BFDE2F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090219031203.GE19443%yamahata@xxxxxxxxxxxxx> <10C63FAD690C13458F0B32BCED571F1406BFE692@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090219053236.GG19443%yamahata@xxxxxxxxxxxxx> <10C63FAD690C13458F0B32BCED571F1406D080C5@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090302082135.GH21000%yamahata@xxxxxxxxxxxxx> <10C63FAD690C13458F0B32BCED571F1406D087C4@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090302104748.GK21000%yamahata@xxxxxxxxxxxxx> <10C63FAD690C13458F0B32BCED571F1406D087F2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Mon, Mar 02, 2009 at 07:21:28PM +0800, Zhang, Yang wrote:
> Isaku Yamahata wrote:
> > So you want to account vhpt memory.
> > Then, pass the domain pointer as argument to alloc_domheap_page(d,
> > ...) and leave the hunk in image.py.
> > Maybe the code path which frees domain memory needs twist.
> 
> it doesn't pass the domain pointer as argument. There are separate function 
> free_domain_vhpt() and free_domain_vtlb to frees the memory which is used as 
> vhpt.
> but i also free the saved memory which may not used by vhpt(sometimes this 
> will be true) 
> in vmx_relinquish_guest_resources().

You want to balloon the memory for vhpt from dom0 and don't want to allocate
the memory by alloc_domheap_page() with explicit domain pointer.
Then, IA64_HVM_ImageHandler::getRequiredAvailableMemory() is wrong
place to modify.
Please see _initDomain() in XendDomainInfo.py and memory, maxmem
and xc.domain_set_maxmem(), balloon.free().
Only the argument to balloon.free() should be touched and
the argument to xc.domain_se_maxmem() shouldn't be touched.
-- 
yamahata

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