This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH 0 of 5] xentrace: non-contiguous allocation of pe

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH 0 of 5] xentrace: non-contiguous allocation of per-cpu buffer
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Sun, 8 May 2011 17:07:51 +0200
Cc: George Dunlap <george.dunlap@xxxxxxxxxx>
Delivery-date: Sun, 08 May 2011 08:08:40 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1304867272; l=581; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:Cc:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=aEavYaUigK7gTgtHLEv1YzHg9MU=; b=AjnwE4+7Rc4rZyIWk/qD8xwhPU/fv88fhy2IrnbZERJbu9iprkqyigaOpSy+q7NUeGW qUlHjPbqwAXjBN4z1v//4AvYiarm3xKTGZ6qi4mefZUGkxjTSprSzD8o9y7J1cVRcI0Sl QhrTnaLEEcMKkUvhaoo9JW5UYWtlRXvmtoE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <patchbomb.1304706331@localhost>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <patchbomb.1304706331@localhost>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
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.


Xen-devel mailing list