From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Re: non-contiguous allocations Date: Sat, 07 May 2011 17:31:23 +0100 Message-ID: References: <20110507083919.GA28246@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110507083919.GA28246@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Olaf Hering Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 07/05/2011 09:39, "Olaf Hering" wrote: > On Fri, May 06, Keir Fraser wrote: > >> On 06/05/2011 19:12, "Olaf Hering" wrote: > >>> Is there a way to allocate more than 128mb with repeated calls to >>> alloc_xenheap_page()? >> >> Yes it should just work. Are you sure you actually have more than 128MB >> available (not all allocated to dom0 for example)? > > Thanks Keir. xm mem-set 0 1024 did the trick. > I was under the impression dom0 would automatically get ballooned down > to make room for the allocation requests. Only when creating new domains in xend, then xend will balloon down dom0. So no, not in this case: we can hardly go run xend while we're in hypervisor context. ;-) This kind of thing is why we normally run dom0 with 'just enough' memory and don't use auto ballooning. -- Keir > Olaf