Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   14857 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

XENTRACE_FORMAT(1)					    XENTRACE_FORMAT(1)

NAME
       xentrace_format - pretty-print Xen trace data

SYNOPSIS
       xentrace_format [ DEFS-FILE ]

DESCRIPTION
       xentrace_format	parses trace data in xentrace binary format from stan‐
       dard input and reformats it according to the rules in a file of defini‐
       tions (DEFS-FILE), printing to standard output.

       The rules in DEFS-FILE should have the format shown below:

       event_id whitespace format

       Each rule should start on a new line.

       The  format  string  may	 include  format specifiers, such as: %(cpu)d,
       %(tsc)d, %(event)d, %(1)d, %(2)d, %(3)d, %(4)d, %(5)d

       [ the `d' format specifier output in decimal, alternatively `x'
	 will output in hexadecimal and `o' will output in octal ]

       These correspond to the CPU number, event ID, timestamp counter and the
       5 data fields from the trace record.  There should be one such rule for
       each type of event to be pretty-printed (events which do not have  for‐
       matting rules are ignored).

       A  sample format file for Xen's predefined trace events is available in
       the file tools/xentrace/formats in the Xen source tree.

       Depending on your system and the rate at which trace data is  produced,
       this  script  may not be able to keep up with the output of xentrace if
       it is piped directly.  In these circumstances you should have  xentrace
       output to a file for processing off-line.

AUTHOR
       Mark A. Williamson <mark.a.williamson@intel.com>

SEE ALSO
       xentrace(8), xentrace_cpusplit(1)

Xen domain 0 utils		  11 May 2004		    XENTRACE_FORMAT(1)

Vote for polarhome