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] [PATCH] Make ballooning work with maxmem > mem (i386 ver

To: Glauber de Oliveira Costa <gcosta@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Make ballooning work with maxmem > mem (i386 version)
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 10 Nov 2006 15:43:10 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 10 Nov 2006 07:43:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061110153357.GD32562@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccE3ux5KsBZMnDSEduDSAAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] Make ballooning work with maxmem > mem (i386 version)
User-agent: Microsoft-Entourage/11.2.5.060620
On 10/11/06 15:33, "Glauber de Oliveira Costa" <gcosta@xxxxxxxxxx> wrote:

>> I took both patches and then changed my mind and immediately reverted them.
>> There is a better way: we should support the XENMEM_memory_map hypercall.
>> We should provide a hypercall (domctl) to set a memory_map_limit parameter
>> and then Xen can use that to fake a memory map when XENMEM_memory_map is
>> called. The tools can set that parameter from config['maxmem'].
> 
> And what happens when the hypercall ever returns ENOSYS, like a kernel
> running in a bit old Hypervisor?
> 
> IMHO,If we have to ever fallback into default assumptions, it seems wiser
> to extend the physicall map to maximum_reservation, not current_reservation.

Maxmem will in future be fixed to track tot_pages. That was its original
purpose: to cap what memory the guest is allowed *now*, not to tell it the
max that it will ever be allowed. Also on e.g., dom0 the max is implemented
as ~0UL (no limit). "Fortunately" this looks like a -ve return code from the
max_mem query hypercall, but if it didn't (for example we masked off the
high bit to make sure the return value was +ve; a fix I will probably
implement) then dom0 boot will be broken as it will try to allocate a
much-too-big p2m table.

We have a way to tell the guest its maximum-ever memory allowance, it's just
not implemented on the tools and hypervisor side yet. That should be fixed.

 -- Keir


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