From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH] Make ballooning work with maxmem > mem
	(i386 version)
Date: Sat, 11 Nov 2006 00:08:27 +0000
Message-ID: <C17AC4FB.42AD%keir@xensource.com>
References: <20061110202739.GA3050@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20061110202739.GA3050@redhat.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Glauber de Oliveira Costa <gcosta@redhat.com>, Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 10/11/06 8:27 pm, "Glauber de Oliveira Costa" <gcosta@redhat.com> wrote:

>> 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.
> 
> Do we have any specification on how should this look like, and what kind
> of behaviour it should provide?

XENMEM_set_memory_map taking a struct { domain, range_list }. This can
initialise a small array embedded in the domain structure.

Plumb through libxc and python xc.so. Probably make the call from
LinuxImageHandler (or whatever it's called) in image.py.

Done. 

Most of the pain is in the tools plumbing (in particular arg parsing in the
python wrapper).

 -- Keir