Messages in this thread | | | From | Mark Asselstine <> | Subject | [PATCH 0/3] trace-cmd fixes for latency tracing record and report | Date | Thu, 5 Apr 2012 15:19:43 -0400 |
| |
The following three patches are for the latency-cmd tree.
trace-cmd latency tracing is broken due to segfaults and disappearing 'trace' logs. Recent commits seem to have broken latency tracers by changing when things are being initialized or leaving some things uninitialized since they are unused in certain circumstances. The first two patches address segfaults when running both the record and report commands caused by attempts to access uninitialized pointers. The last patch avoids empty reports due to the premature clearing of the 'trace' log caused by resetting the current_tracer to 'nop'. We still set the 'current_tracer' to 'nop', just after we have grabbed the data we want.
These changes have been tested on top of the latest trace-cmd tree as well as on top of the trace-cmd-v1.2 tag point in conjunction with the latest mainline kernel as well as an older 2.6.34 vintage kernel.
Tests were done with # ./trace-cmd record -p irqsoff ls /bin # ./trace-cmd report
Regards, Mark Asselstine
| |