[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] Make ballooning work with maxmem > mem (i386 version)


  • To: Glauber de Oliveira Costa <gcosta@xxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Fri, 10 Nov 2006 15:44:07 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 10 Nov 2006 07:44:26 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccE3w5zTUBROHDSEduDSAAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH] Make ballooning work with maxmem > mem (i386 version)



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?

Oh, and bear in mind you can always use 'memory=' as a boot parameter to
force the p2m size and mem_map size.

 -- Keir


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.