trace-cmd-dump - Man Page

show a meta data from a trace file, created by trace-cmd record

Synopsis

trace-cmd dump [Options] [input-file]

Description

The trace-cmd(1) dump command will display the meta data from a trace file created by trace-cmd record.

Options

-i input-file: By default, trace-cmd dump will read the file trace.dat. But the -i option open up the given input-file instead. Note, the input file may also be specified as the last item on the command line.
-v, --validate: Check if the input file is a valid trace file, created by trace-cmd.
--summary: Print a meta data summary - initial format and a short description of each file section. This is the default action, if no arguments are specified.
--head-page: Print the header page information, stored in the file.
--head-event: Print the event header information, stored in the file.
--ftrace-events: Print formats of ftrace specific events.
--systems: Print information of event systems, stored in the file - name and number of events for each system.
--events: Print formats of all events, stored in the file.
--kallsyms: Print information of the mapping of function addresses to the function names.
--printk: Print trace_printk() format strings, stored in the file.
--cmd-lines: Print mapping a PID to a process name.
--options: Print all options, stored in the file.
--flyrecord: Print the offset and the size of tracing data per each CPU.
--all: Print all meta data from the file.
--help: Print usage information.

Examples

# trace-cmd dump --summary -i trace.dat

Tracing meta data in file trace.dat:
       [Initial format]
               6       [Version]
               0       [Little endian]
               8       [Bytes in a long]
               4096    [Page size, bytes]
       [Header info, 205 bytes]
       [Header event, 205 bytes]
       [Ftrace format, 15 events]
       [Events format, 2 systems]
       [Kallsyms, 7144493 bytes]
       [Trace printk, 2131 bytes]
       [Saved command lines, 117 bytes]
       8 [CPUs with tracing data]
       [12 options]
       [Flyrecord tracing data]

# trace-cmd dump --flyrecord -i trace.dat
        [Flyrecord tracing data]
                 7176192 0      [offset, size of cpu 0]
                 7176192 0      [offset, size of cpu 1]
                 7176192 0      [offset, size of cpu 2]
                 7176192 4096   [offset, size of cpu 3]
                 7180288 4096   [offset, size of cpu 4]
                 7184384 0      [offset, size of cpu 5]
                 7184384 0      [offset, size of cpu 6]
                 7184384 0      [offset, size of cpu 7]

# trace-cmd dump --summary --systems -i trace.dat

Tracing meta data in file trace.dat:
       [Initial format]
               6       [Version]
               0       [Little endian]
               8       [Bytes in a long]
               4096    [Page size, bytes]
       [Header info, 205 bytes]
       [Header event, 205 bytes]
       [Ftrace format, 15 events]
       [Events format, 3 systems]
               sched 23 [system, events]
               irq 5 [system, events]
               kvm 70 [system, events]
       [Kallsyms, 7144493 bytes]
       [Trace printk, 2131 bytes]
       [Saved command lines, 157 bytes]
       8 [CPUs with tracing data]
       [11 options]
       [Flyrecord tracing data]

# trace-cmd dump --summary --systems -i trace.dat
File trace.dat is a valid trace-cmd file

Author

Steven Rostedt <rostedt@goodmis.org^[1]>, author of trace-cmd. Tzvetomir Stoyanov <tz.stoyanov@gmail.com^[2]>, author of this man page.