From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: Re: [PATCH 0 of 5] xentrace: non-contiguous allocation
	of per-cpu buffer
Date: Sun, 8 May 2011 17:07:51 +0200
Message-ID: <20110508150751.GA4882@aepfle.de>
References: <patchbomb.1304706331@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <patchbomb.1304706331@localhost>
List-Unsubscribe: <http://lists.xensource.com/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/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: xen-devel@lists.xensource.com
Cc: George Dunlap <george.dunlap@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Fri, May 06, Olaf Hering wrote:

> For some reason its not possible to allocate more than 128MB with repeated
> calls to alloc_xen_heappage(). Any ideas how to reach the theoretical limit of
> 256MB per cpu?

The dom0 needs to be ballooned down to make room for the tracebuffers.

> Also the error path in alloc_trace_bufs() needs a fix, I always run into the
> assert there.

Beside this issue, the checks in the bogus() function trigger with a
256MB per-cpu buffer.

I will revisit the series and post a new version once I have fixes for
these issues.

Olaf