Comment 1 for bug 1316047

>So you can't use trace-cmd output with idlestat
Right. it only takes idlestat output format.(1)

The ASCII trace data and cpu information needs to be extracted from trace-cmd output file.
To support this trace-cmd header parsing is required as per "trace-cmd.dat - trace-cmd file format".

(1)
idlestat output format:
------------------------------------
version = 1
cpus=4 << here it reads the number of cpus
clusterA:
        core0
                cpu0
        core1
                cpu1
        core2
                cpu2
        core3
                cpu3

      <idle>-0 [002] d..2 14853.939301: cpu_idle: state=1 cpu_id=2
          <idle>-0 [000] .N.2 14853.939331: cpu_idle: state=4294967295 cpu_id=0
          <idle>-0 [000] d..2 14853.939514: cpu_idle: state=1 cpu_id=0