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

Re: [Xen-devel] [PATCH] x86: don't limit dom0's maximum reservation by the available memory



>>> On 23.08.11 at 19:08, David Vrabel <david.vrabel@xxxxxxxxxx> wrote:
> # HG changeset patch
> # User David Vrabel <david.vrabel@xxxxxxxxxx>
> # Date 1314119246 -3600
> # Node ID b0f7a5b68726672c131f0a12a819941b4a56a4df
> # Parent  1ec6c392d40f37032b0c845094c7ee6ba69740fd
> x86: don't limit dom0's maximum reservation by the available memory
> 
> Set dom0's initial maximum reservation using the max value supplied in
> the dom0_mem command line option without limiting it by the available
> memory.
> 
> This allows dom0 to make use of any hotplugged memory without having
> to also adjust the maximum reservation.
> 
> Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx>
> Cc: Jan Beulich <JBeulich@xxxxxxxxxx>

Acked-by: Jan Beulich <jbeulich@xxxxxxxxxx>

> Cc: Keir Fraser <keir@xxxxxxx>
> ---
> Please consider for Xen 4.1.2.
> 
> diff -r 1ec6c392d40f -r b0f7a5b68726 xen/arch/x86/domain_build.c
> --- a/xen/arch/x86/domain_build.c     Mon Aug 15 11:42:37 2011 +0100
> +++ b/xen/arch/x86/domain_build.c     Tue Aug 23 18:07:26 2011 +0100
> @@ -254,7 +254,7 @@ static unsigned long __init compute_dom0
>      }
>  #endif
>  
> -    d->max_pages = min(max_pages, avail);
> +    d->max_pages = min_t(unsigned long, max_pages, UINT_MAX);
>  
>      return nr_pages;
>  }
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx 
> http://lists.xensource.com/xen-devel 




_______________________________________________
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®.