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] Fix that makes xend tracing thread safe

To: Magnus Carlsson <magnus@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Fix that makes xend tracing thread safe
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Thu, 29 Mar 2007 23:33:22 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 29 Mar 2007 23:34:34 +0100
Envelope-to: Keir.Fraser@xxxxxxxxxxxx
In-reply-to: <460C3534.8020002@xxxxxxxxxx>
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: <460C3534.8020002@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Thu, Mar 29, 2007 at 02:52:52PM -0700, Magnus Carlsson wrote:

> Currently, the output in xend.trace is sometimes garbled since multiple
> threads write to it simultaneously.  The following patch fixes that.
> It also adds an initial field with the thread name on each traced line,
> which makes it easier to follow the trace.  (If this is considered a new
> feature which shouldn't be included due to the feature freeze, it can be
> disabled by removing the first line in print_trace.)

Applied, thanks Magnus.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>