Re: [PATCH 05/11] perf stat: Check existence of frontend/backed stalled cycles

2016-03-03 Thread Arnaldo Carvalho de Melo
Em Thu, Mar 03, 2016 at 09:49:00AM -0300, Arnaldo Carvalho de Melo escreveu: > Em Thu, Mar 03, 2016 at 09:28:18AM +0100, Ingo Molnar escreveu: > > > > * Arnaldo Carvalho de Melo wrote: > > > > > Before: > > > > > > $ perf stat ls > > > a.patch > > > > > > Performance counter stats for 'l

Re: [PATCH 05/11] perf stat: Check existence of frontend/backed stalled cycles

2016-03-03 Thread Arnaldo Carvalho de Melo
Em Thu, Mar 03, 2016 at 09:28:18AM +0100, Ingo Molnar escreveu: > > * Arnaldo Carvalho de Melo wrote: > > > Before: > > > > $ perf stat ls > > a.patch > > > > Performance counter stats for 'ls': > > > > 0.822067 task-clock (msec) # 0.873 CPUs utilized (82.26%) > >

Re: [PATCH 05/11] perf stat: Check existence of frontend/backed stalled cycles

2016-03-03 Thread Ingo Molnar
* Arnaldo Carvalho de Melo wrote: > Before: > > $ perf stat ls > a.patch > > Performance counter stats for 'ls': > > 0.822067 task-clock (msec) # 0.873 CPUs utilized (82.26%) > 0 context-switches# 0.000 K/sec (82.26%) > 0 cp

[PATCH 05/11] perf stat: Check existence of frontend/backed stalled cycles

2016-02-29 Thread Arnaldo Carvalho de Melo
From: Andi Kleen Only put the frontend/backend stalled cycles into the default perf stat events when the CPU actually supports them. This avoids empty columns with --metric-only on newer Intel CPUs. Committer note: Before: $ perf stat ls a.patch Performance counter stats for 'ls':