trace-cmd split: Do not allow spliting of latency tracers
trace-cmd split is an operation to make large data records into more
manageable sized files.
But for latency tracers like:
trace-cmd record wakeup
trace-cmd does not record any binary files, it only records the ASCII
contents of the trace file that is only a snapshot of where the latency
happens (which is usually rather small). trace-cmd split is made for
"flight recording" (constant recording over a period of time) that can
cause the file to become gigabytes in size. Splitting the ASCII text does
not make any sense.
That said, trace-cmd split should not segfault either when trying to split
a latency trace. Instead do what trace-cmd hist does, which is to simply
exit with an error message that says it does not support latency traces.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
3 files changed
