[PATCH 0/3] trace-cmd fixes for latency tracing record and report

[Mark Asselstine]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/