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

Re: [Xen-devel] trace default?

To: Rob Gardner <rob.gardner@xxxxxx>
Subject: Re: [Xen-devel] trace default?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 7 Sep 2005 10:48:20 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 07 Sep 2005 09:41:32 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <431E1D6C.2070308@xxxxxx>
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: <431E1D6C.2070308@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 6 Sep 2005, at 23:51, Rob Gardner wrote:

The xen trace facility is not enabled by default. I'm working on some tools that use it, and I'm concerned that the tool will not work for customers who buy packaged distro's. What are the arguments for keeping trace disabled? Is it just the memory consumed by the trace buffers? It doesn't appear to me that there would be any impact beyond that. What is the possibility of making tracing enabled by default?

It's up to the distros to decide what options they anable in their default Xen package imo.

 -- Keir


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

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