Command-line operation

Linux Trace Toolkit Reference Manual
<<< Previous Page | Home | Up | Next Page >>>

5. Decoder (visualizer) command-line operation

NAME

tracevisualizer - The data analysis component of the Linux Trace Toolkit (LTT)

SYNOPSIS

tracevisualizer [ -g ] [ -d ] [ { -o | -t } EventTypes ] [ -cCPU-ID ] [ -pPID ] [ -s ] [ -a ] [ -f { t | s | l } ] [ TraceFile ProcFile [ OutFile ]]

DESCRIPTION

The tracevisualizer program is the data analysis component of the Linux Trace Toolkit (LTT). It is used perform data interpretation on the acquired data and display a graphical trace of it if specified. Graphical display of the trace and other GUI tools requires that the toolkit be compiled with the GTK+ library installed. See TraceToolkit/Help/index.html for installation details.

If the program is launched with no command-line arguments, it automatically launches the GUI and waits for the user to specify files to operate on. Otherwise, TraceFile is the file that was produced by the LTT data acquisition component. ProcFile is the system description file and is useful for process analysis calculations. OutFile is the file to which the trace and analysis is written in text format.

OPTIONS

-g Enter graphic mode.

-o Omit event types. Do not include in the data analysis the event types listed in EventTypes, which is a space-separated list of any of the following events:

- "START" - Trace start
- "SYS_ENTRY" - System call entry
- "SYS_EXIT" - System call exit
- "TRAP_ENTRY" - Trap entry
- "TRAP_EXIT" - Trap exit
- "IRQ_ENTRY" - Interrupt entry
- "IRQ_EXIT" - Interrupt exit
- "SCHED" - Schedule change
- "KTIMER" - Kernel timer
- "SIRQ" - Soft IRQ management
- "PROCESS" - Process management
- "FS" - File system management
- "TIMER" - Timer management
- "MEM" - Memory management
- "SOCKET" - Socket communications
- "IPC" - System V IPC communications
- "NET" - Network device management

If you've compile the trace decoder with RTAI support, then the following event types can be configured:

- "RTMNT" - RTAI mount
- "RTUMNT" - RTAI unmount
- "RTGIRQE" - RTAI global IRQ entry
- "RTGIRQX" - RTAI global IRQ exit
- "RTOIRQE" - RTAI CPU own IRQ entry
- "RTOIRQX" - RTAI CPU own IRQ exit
- "RTTRAPE" - RTAI trap entry
- "RTTRAPX" - RTAI trap exit
- "RTSRQE" - RTAI SRQ entry
- "RTSRQX" - RTAI SRQ exit
- "RTSWTCHL" - RTAI switch to Linux
- "RTSWTCHR" - RTAI switch to RT
- "RTSCHED" - RTAI scheduling change
- "RTTASK" - RTAI task management
- "RTTIMER" - RTAI timer management
- "RTSEM" - RTAI semaphore communications
- "RTMSG" - RTAI message communications
- "RTRPC" - RTAI RPC communications
- "RTMBX" - RTAI message box communications
- "RTFIFO" - RTAI FIFO communications
- "RTSHM" - RTAI shared memory management
- "RTPOSIX" - RTAI Posix layer
- "RTLXRT" - RTAI LXRT layer
- "RTLXRTI" - RTAI LXRT-informed layer

-t Trace event types. Only include in the data analysis the event types listed in EventTypes. See -o option for details. Note that -t and -o are mutually exclusive. Specifying both will result in an error.

-c Trace CPU-ID. Only include events that occurred on CPU-ID in data analysis.

-p Trace PID. Only include process number PID in data analysis.

-s Summarize. Do not list all acquired events in data analysis; only the result of the analysis. This has to be used with -a. Otherwise, it has no effect.

-a Analyze the trace and output the results.

-ft Forget time, Do not print event times.

-fs Forget string. Do not print event descriptions.

-fl Forget data entry length. Do not print event data entry length.

-fp Forget PID. Do not print the PID of the process to which the event belongs.

-fc Forget CPU-ID. Do not print the CPU-ID of the CPU where the event occurred.

-d Dump to file. Write out data analysis to file OutFile. If no other option is specified, then it is not necessary to use -d since it's the default behavior of tracevisualizer.

<<< Previous Page | Home | Up | Next Page >>>
Linux trace toolkit | Decoder command-line operation