WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [Xen-changelog] [xen-unstable] xentrace: fix tracing for

To: John Levon <levon@xxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [Xen-changelog] [xen-unstable] xentrace: fix tracing for 64bit guests
From: Andre Przywara <andre.przywara@xxxxxxx>
Date: Tue, 10 Jun 2008 14:28:05 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Jun 2008 05:31:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080610121054.GB19936@xxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200806101040.m5AAeMPq003313@xxxxxxxxxxxxxxxxxxxxx> <20080610121054.GB19936@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.10 (X11/20070409)
John Levon wrote:
On Tue, Jun 10, 2008 at 03:40:21AM -0700, Xen patchbot-unstable wrote:

# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1213001138 -3600
# Node ID 268a9f8286f3ae259359fb3b31197e674b8c44b8
# Parent  5009f5d093cea2e55a3838bb7e6ee42c12b0f68a
xentrace: fix tracing for 64bit guests

Is this an incompatible change (a brief scan made it seem so) ? If so,
it probably needs a ChangeLog entry
It mostly adds additional tracepoints (marked by bit 8 as 64bit capable) and changing the CPUID trace, which was broken before (so this is more a fix). The user-space end of the traces is xentrace_format with the respective formats file, which I also changed. Otherwise I tried to be compatible. Given the fact that this was broken since at least February or so, I don't think that anyone seriously uses tracing and could be concerned about such changes. There are still some tracepoints logged but not interpreted by xentrace_format, I will send a patch later.

BTW: Has anyone tools for analyzing traces? Does someone use tracing regularly?


Regards,
Andre.

--
Andre Przywara
AMD-OSRC (Dresden)
Tel: x84917


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel