The trace-cmd(1) stop is a complement to trace-cmd-start(1). This
will disable Ftrace from writing to the ring buffer. This does not
stop the overhead that the tracing may incur. Only the updating of
the ring buffer is disabled, the Ftrace tracing may still be inducing
After stopping the trace, the trace-cmd-extract(1) may strip out the
data from the ring buffer and create a trace.dat file. The Ftrace
pseudo file system may also be examined.
To disable the tracing completely to remove the overhead it causes,
use trace-cmd-reset(1). But after a reset is performed, the data that
has been recorded is lost.
If the kernel supports multiple buffers, this will stop the trace
for only the given buffer. It does not affect any other buffer.
This may be used multiple times to specify different buffers.
When this option is used, the top level instance will not be
stopped unless -t is given.
Stop the trace for all existing buffer instances. When this
option is used, the top level instance will not be stopped unless
-t is given.
Stops the top level instance buffer. Without the -B or -a option
this is the same as the default. But if -B or -a is used, this is
required if the top level instance buffer should also be stopped.
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 firstname.lastname@example.org] If you have a bug report for
this manual page, send it to Steven Rostedt <email@example.com>.
This page was obtained from the project's upstream Git repository
on 2017-03-13. 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 firstname.lastname@example.org