1TRACE-CMD-DUMP(1) TRACE-CMD-DUMP(1)
2
6 trace-cmd-dump - show a meta data from a trace file, created by
7 trace-cmd record
8
10 trace-cmd dump [OPTIONS] [input-file]
11
13 The trace-cmd(1) dump command will display the meta data from a trace
14 file created by trace-cmd record.
15
17 -i input-file
18 By default, trace-cmd dump will read the file trace.dat. But the -i
19 option open up the given input-file instead. Note, the input file
20 may also be specified as the last item on the command line.
21 -v, --validate
23 Check if the input file is a valid trace file, created by
24 trace-cmd.
25 --summary
27 Print a meta data summary - initial format and a short description
28 of each file section. This is the default action, if no arguments
29 are specified.
30 --head-page
32 Print the header page information, stored in the file.
33 --head-event
35 Print the event header information, stored in the file.
36 --ftrace-events
38 Print formats of ftrace specific events.
39 --systems
41 Print information of event systems, stored in the file - name and
42 number of events for each system.
43 --events
45 Print formats of all events, stored in the file.
46 --kallsyms
48 Print information of the mapping of function addresses to the
49 function names.
50 --printk
52 Print trace_printk() format strings, stored in the file.
53 --cmd-lines
55 Print mapping a PID to a process name.
56 --options
58 Print all options, stored in the file.
59 --flyrecord
61 Print the offset and the size of tracing data per each CPU.
62 --all
64 Print all meta data from the file.
65 --help
67 Print usage information.
68
70 # trace-cmd dump --summary -i trace.dat
71 Tracing meta data in file trace.dat:
73 [Initial format]
74 6 [Version]
75 0 [Little endian]
76 8 [Bytes in a long]
77 4096 [Page size, bytes]
78 [Header info, 205 bytes]
79 [Header event, 205 bytes]
80 [Ftrace format, 15 events]
81 [Events format, 2 systems]
82 [Kallsyms, 7144493 bytes]
83 [Trace printk, 2131 bytes]
84 [Saved command lines, 117 bytes]
85 8 [CPUs with tracing data]
86 [12 options]
87 [Flyrecord tracing data]
88 # trace-cmd dump --flyrecord -i trace.dat
90 [Flyrecord tracing data]
91 7176192 0 [offset, size of cpu 0]
92 7176192 0 [offset, size of cpu 1]
93 7176192 0 [offset, size of cpu 2]
94 7176192 4096 [offset, size of cpu 3]
95 7180288 4096 [offset, size of cpu 4]
96 7184384 0 [offset, size of cpu 5]
97 7184384 0 [offset, size of cpu 6]
98 7184384 0 [offset, size of cpu 7]
99 # trace-cmd dump --summary --systems -i trace.dat
101 Tracing meta data in file trace.dat:
103 [Initial format]
104 6 [Version]
105 0 [Little endian]
106 8 [Bytes in a long]
107 4096 [Page size, bytes]
108 [Header info, 205 bytes]
109 [Header event, 205 bytes]
110 [Ftrace format, 15 events]
111 [Events format, 3 systems]
112 sched 23 [system, events]
113 irq 5 [system, events]
114 kvm 70 [system, events]
115 [Kallsyms, 7144493 bytes]
116 [Trace printk, 2131 bytes]
117 [Saved command lines, 157 bytes]
118 8 [CPUs with tracing data]
119 [11 options]
120 [Flyrecord tracing data]
121 # trace-cmd dump --summary --systems -i trace.dat
123 File trace.dat is a valid trace-cmd file
124
126 trace-cmd(1), trace-cmd.dat(1)
127
129 Steven Rostedt <rostedt@goodmis.org[1]>, author of trace-cmd. Tzvetomir
130 Stoyanov <tz.stoyanov@gmail.com[2]>, author of this man page.
131
133 git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
134
136 Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted
137 under the terms of the GNU Public License (GPL).
138
140 1. rostedt@goodmis.org
141 mailto:rostedt@goodmis.org
142 2. tz.stoyanov@gmail.com
144 mailto:tz.stoyanov@gmail.com
145 12/02/2020 TRACE-CMD-DUMP(1)