From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: Re: xen does not see more than 173800500k of
	memory
Date: Thu, 23 Aug 2007 15:51:36 +0100
Message-ID: <46CDBB18.76E4.0078.0@novell.com>
References: <46CD54BB.76E4.0078.0@novell.com>
	<C2F357D2.14826%keir@xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C2F357D2.14826%keir@xensource.com>
Content-Disposition: inline
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: Susan Krysan <KRYSANS@unisys.com>, Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

>>> Keir Fraser <keir@xensource.com> 23.08.07 16:27 >>>
>This should be easily fixed by properly applying
>domain_clamp_alloc_bitsize() in __alloc_domheap_pages(). Why is it only
>applied when the bitsize is explicitly specified by the caller?
>
>I think that's the only thing to fix to allow the 166GB boot-time
>restriction to be lifted, but am I missing something, Jan?

We had this discussion before - the problem is not restricting the =
allocations
a domain does, but pages getting passed to it from other domains, which =
(if
they happen to lie outside the 166Gb range) the domain then can't control.
And yes, you said page flipping is basically dead, but this isn't being
enforced (and probably can't as long as you want to support older guests
potentially using it).

Jan