ia64/xen-unstable

view tools/xentrace/xentrace_format.1 @ 6946:e703abaf6e3d

Add behaviour to the remove methods to remove the transaction's path itself. This allows us to write Remove(path) to remove the specified path rather than having to slice the path ourselves.
author emellor@ewan
date Sun Sep 18 14:42:13 2005 +0100 (2005-09-18)
parents 6cf25fb7eebd
children
line source
1 .TH XENTRACE_FORMAT 1 "11 May 2004" "Xen domain 0 utils"
2 .SH NAME
3 xentrace_format \- pretty-print Xen trace data
4 .SH SYNOPSIS
5 .B xentrace_format
6 [
7 .I DEFS-FILE
8 ]
9 .SH DESCRIPTION
10 .B xentrace_format
11 parses trace data in \fBxentrace\fP binary format from standard input
12 and reformats it according to the rules in a file of definitions
13 (\fIDEFS-FILE\fP), printing to standard output.
15 The rules in \fIDEFS-FILE\fP should have the format shown below:
17 \fIevent_id\fP \fIwhitespace\fP \fIformat\fP
19 Each rule should start on a new line.
21 The format string may include format specifiers, such as:
22 %(cpu)d, %(tsc)d, %(event)d, %(1)d, %(2)d, %(3)d, %(4)d, %(5)d
24 [ the `d' format specifier output in decimal, alternatively `x'
25 will output in hexadecimal and `o' will output in octal ]
27 These correspond to the CPU number, event ID, timestamp counter and
28 the 5 data fields from the trace record. There should be one such
29 rule for each type of event to be pretty-printed (events which do not
30 have formatting rules are ignored).
32 A sample format file for Xen's predefined trace events is available
33 in the file tools/xentrace/formats in the Xen source tree.
35 Depending on your system and the rate at which trace data is produced,
36 this script may not be able to keep up with the output of
37 \fBxentrace\fP if it is piped directly. In these circumstances you
38 should have \fBxentrace\fP output to a file for processing off-line.
40 .SH AUTHOR
41 Mark A. Williamson <mark.a.williamson@intel.com>
43 .SH "SEE ALSO"
44 xentrace(8), xentrace_cpusplit(1)