From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] Make ballooning work with maxmem > mem (i386 version) Date: Fri, 10 Nov 2006 15:44:07 +0000 Message-ID: References: <20061110153357.GD32562@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20061110153357.GD32562@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Glauber de Oliveira Costa , Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 10/11/06 15:33, "Glauber de Oliveira Costa" 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? Oh, and bear in mind you can always use 'memory=' as a boot parameter to force the p2m size and mem_map size. -- Keir