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
Check if the input file is a valid trace file, created by
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.
Print the header page information, stored in the file.
Print the event header information, stored in the file.
Print formats of ftrace specific events.
Print information of event systems, stored in the file - name
and number of events for each system.
Print formats of all events, stored in the file.
Print information of the mapping of function addresses to the
Print trace_printk() format strings, stored in the file.
Print mapping a PID to a process name.
Print all options, stored in the file.
Print the offset and the size of tracing data per each CPU.
Print all meta data from the file.
Print usage information.
This page is part of the trace-cmd (a front-end for Ftrace)
project. Information about the project can be found at [unknown
-- if you know, please contact email@example.com] If you have a
bug report for this manual page, send it to Steven Rostedt
<firstname.lastname@example.org>. This page was obtained from the project's
upstream Git repository
on 2021-04-01. (At that time, the date of the most recent commit
that was found in the repository was 2021-03-26.) If you
discover any rendering problems in this HTML version of the page,
or you believe there is a better or more up-to-date source for
the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original
manual page), send a mail to email@example.com