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] Does xentrace write into buffers by default?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Does xentrace write into buffers by default?
From: Parissa Heidari <parisa.heidari@xxxxxxxxxx>
Date: Thu, 5 Apr 2007 18:43:02 -0400
Delivery-date: Thu, 05 Apr 2007 15:40:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.1
Hello,
I have a question about the way Xentrace takes a trace.
In previous versions of Xen, I took a trace by setting the size of buffers, 
activating them and writing the information into a file (optional).
setsize 20
tbctl 1
xentrace /tmp/xentrace.dat

Now I'm using xen-unstable and I see that setsize is already integrated in 
xentrace command.

My question is: does start/stop buffer is integrated into the xentrace too?
I mean, does xen write trace information into buffers by default or it starts 
writing them after the command "xentrace /tmp/xentrace.dat".

If it writes into buffers by default, how can I control it (turn on/off 
buffers).

Best regards,
Parissa. 

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

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