diff options
| author | Thomas Gleixner <[email protected]> | 2017-02-10 16:41:15 +0100 |
|---|---|---|
| committer | Steven Rostedt (VMware) <[email protected]> | 2017-02-15 09:02:24 -0500 |
| commit | 8a58a34ba479d42b3ef28f8ffd9e245a81a7786f (patch) | |
| tree | 39b701b37b8f050d2c54dcf73ccb797db3105dd0 /scripts/gdb | |
| parent | 1f9b3546cf4c273b6d809003244d05cf0460a5e9 (diff) | |
timers: Make flags output in the timer_start tracepoint useful
The timer flags in the timer_start trace event contain lots of useful
information, but the meaning is not clear in the trace output. Making tools
rely on the bit positions is bad as they might change over time.
Decode the flags in the print out. Tools can retrieve the bits and their
meaning from the trace format file.
Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1702101639290.4036@nanos
Requested-by: Arjan van de Ven <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Signed-off-by: Steven Rostedt (VMware) <[email protected]>
Diffstat (limited to 'scripts/gdb')
0 files changed, 0 insertions, 0 deletions