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-devel

Re: [Xen-devel] xm mem-max and mem-set

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] xm mem-max and mem-set
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 14 Apr 2006 07:55:28 +0100
Cc: Ky Srinivasan <ksrinivasan@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 13 Apr 2006 23:58:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <443EFF80.7060005@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <443EB5A6.E57C.0030.0@xxxxxxxxxx> <443EFF80.7060005@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 14 Apr 2006, at 02:48, Anthony Liguori wrote:

I'm slightly concerned about the subtle race condition it would introduce. If there's no reason to set max-mem below current reservation (if it causes crashes which I don't really understand why it would) then I think it would be something best enforced within the hypervisor.
Why, exactly, would setting max-mem below the current reservation 
cause problems in the guest?  I guess it may fail because of grant 
transfer ops (in which case, we really ought to enforce it at the 
hypervisor level).
xen_create_contiguous_region() will get *quite* upset if it gives up 
memory pages to Xen in good faith and gets nothing in return. :-)
Not allowing max allocation to be set lower than current allocation  
sounds like a sensible enforcement for the hypervisor, and I think that 
should avoid crashes.
 -- Keir


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

<Prev in Thread] Current Thread [Next in Thread>