On Tue, Oct 27, 2015 at 11:42:44AM -0300, Arnaldo Carvalho de Melo wrote: SNIP
> This is confusing... > > Anyway, now the perf.data file doesn't produce that many confusing > messages, just one, and the error reporting continues needing a > newline, oops just noticed another problem: > > [root@zoo linux]# perf stat record usleep 1 > > Performance counter stats for 'usleep 1': > > 0.520959 task-clock (msec) # 0.504 CPUs utilized > > 1 context-switches # 0.002 M/sec > > 0 cpu-migrations # 0.000 K/sec > > 51 page-faults # 0.098 M/sec > > 929738 cycles # 1.785 GHz > > 625885 stalled-cycles-frontend # 67.32% frontend cycles > idle > <not supported> stalled-cycles-backend > 634514 instructions # 0.68 insns per cycle > > # 0.99 stalled cycles > per insn > 128859 branches # 247.350 M/sec > > 7602 branch-misses # 5.90% of all branches > > > 0.001034675 seconds time elapsed > > [root@zoo linux]# perf evlist > non matching sample_type[root@zoo linux]# will check, thanks, jirka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
