The two following timegraph views should be shown by default:
Threads
CPUs
The "CPUs" view should show only CPU states, that means no IRQ entries. IRQ-specific states are much more rarely useful than CPU states, so those could be moved to an eventual separate view.
Since concepts like Threads and CPUs are defined generically in the Scope/Jabberwocky frameworks, those two views could be populated by other things than the kernel analysis. For instance, a UST trace with PID/TID contexts could be used to put simple ticks in the Threads and CPU views indicating where the user-space events are located.
The two following timegraph views should be shown by default:
The "CPUs" view should show only CPU states, that means no IRQ entries. IRQ-specific states are much more rarely useful than CPU states, so those could be moved to an eventual separate view.
Since concepts like Threads and CPUs are defined generically in the Scope/Jabberwocky frameworks, those two views could be populated by other things than the kernel analysis. For instance, a UST trace with PID/TID contexts could be used to put simple ticks in the Threads and CPU views indicating where the user-space events are located.