[Xen-devel] Issue introduced in #Cset 20194

To:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject:	[Xen-devel] Issue introduced in #Cset 20194
From:	"Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
Date:	Fri, 18 Sep 2009 14:53:42 +0800
Accept-language:	en-US
Acceptlanguage:	en-US
Cc:
Delivery-date:	Thu, 17 Sep 2009 23:54:59 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	Aco4LMJyA8F93FjIToKCzA9tGfYhhA==
Thread-topic:	Issue introduced in #Cset 20194

Hi, Keir
   In the #Cset20194, it introduces page check logic for Pod cache, but it also 
brings much more extra cost when create domain.  On my machine,  If create a 
HVM guest with 3G memory,  I have to wait hunderds of seconds for "xm cr" 
command and during this period dom0 can't respond to any operations.  Maybe we 
need to introudce another switch to replace simple NDEBUG macro for the page 
check logic or improve the check logic and make it more efficient.  What's your 
opinion ?   
Xiantao  

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] Issue introduced in #Cset 20194