More good news: the trace-cmd toolset includes a GUI frontend, for more human-friendly interpretation and analysis, called KernelShark (though, in my opinion, it isn't as full-featured as Trace Compass is). Installing it on Ubuntu/Debian is as simple as doing sudo apt install kernelshark.
Below, we run kernelshark, passing the trace data file output from our preceding trace-cmd record session as the parameter to it (adjust the parameter to KernelShark to refer to the location where you've saved the tracing metadata):
$ kernelshark ./trace_ps.dat
A screenshot of KernelShark running with the preceding trace data is shown here:
Interesting; the ps process ran on CPU #2 (as we saw with the CLI version previously). Here, we also see the functions executed in the lower tiled horizontal...
