The trace-cmd(1) stream will start tracing just like
trace-cmd-record(1), except it will not record to a file and instead
it will read the binary buffer as it is happening, convert it to a
human readable format and write it to stdout.
This is basically the same as trace-cmd-start(1) and then doing a
trace-cmd-show(1) with the -p option. trace-cmd-stream is not as
efficient as reading from the pipe file as most of the stream work is
done in userspace. This is useful if it is needed to do the work
mostly in userspace instead of the kernel, and stream also helps to
debug trace-cmd-profile(1) which uses the stream code to perform the
live data analysis for the profile.
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 2020-08-13. (At that time, the date of the most recent commit
that was found in the repository was 2020-07-22.) 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