From: "Steven Rostedt (Google)" <rostedt@xxxxxxxxxxx> Add a new command called "analyze" that reads a trace.dat file and will report useful information from it. Such as: Time the CPUs were idle. What tasks ran the most on a CPU. For each task, how long were the wake ups, how long was it blocked, preempted, or just sleeping. And many more to come. See the man page at the last patch for more details. Steven Rostedt (Google) (12): trace-cmd: Add trace-cmd analyze trace-cmd analyze: Show what tasks are running the most trace-cmd analyze: Show how much tasks run on each CPU trace-cmd analyze: Use sched_switch to find comm mappings trace-cmd analyze: Use sched_switch event to update times trace-cmd analyze: Add tracing of tasks and their states trace-cmd analyze: Add "idleness" trace-cmd analyze: Track migration trace-cmd analyze: Add wake up latency timings trace-cmd analyze: Add counting of page faults trace-cmd analyze: Account for dropped events trace-cmd analyze: Add documentation .../trace-cmd/trace-cmd-analyze.1.txt | 290 +++++ tracecmd/Makefile | 1 + tracecmd/include/trace-local.h | 2 + tracecmd/trace-analyze.c | 1046 +++++++++++++++++ tracecmd/trace-cmd.c | 1 + tracecmd/trace-usage.c | 7 + 6 files changed, 1347 insertions(+) create mode 100644 Documentation/trace-cmd/trace-cmd-analyze.1.txt create mode 100644 tracecmd/trace-analyze.c -- 2.35.1
