From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rob Gardner <rob.gardner@hp.com>
Subject: trace default?
Date: Tue, 06 Sep 2005 16:51:24 -0600
Message-ID: <431E1D6C.2070308@hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/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/cgi-bin/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: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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?

Rob