From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: Re: xentrace: broken by c/s 23050:4ebba54b666f
Date: Wed, 23 Mar 2011 09:33:18 +0100
Message-ID: <20110323083318.GA13361@aepfle.de>
References: <4D87841B.1000102@amd.com>
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: <4D87841B.1000102@amd.com>
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: Christoph Egger <Christoph.Egger@amd.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Mon, Mar 21, Christoph Egger wrote:

> C/s 23050:4ebba54b666f broke xentrace:

Christoph, I sent a series of xentrace patches yesterday. The first one
which checks for t_info_pages becoming zero should fix the issue you are
seeing.

Olaf