[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1712291149040.2237@hadrien>
Date: Fri, 29 Dec 2017 11:58:42 +0100 (CET)
From: Julia Lawall <julia.lawall@...6.fr>
To: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
linux-kernel@...r.kernel.org
Subject: perf: documentation for cycles_no_execute event
Hello,
Many of the x86 pipeline.json files have the brief description "Total
execution stalls" for both CYCLE_ACTIVITY.CYCLES_NO_EXECUTE and
CYCLE_ACTIVITY.STALLS_TOTAL. Should the case for
CYCLE_ACTIVITY.CYCLES_NO_EXECUTE have a brief description that mentions
cycles? Some of the files do have a public description that mentions
cycles, eg broadwellde/pipeline.json has "Counts number of cycles nothing
is executed on any execution port.", but others (eg ivytown/pipeline.json)
just have "Total execution stalls." twice. Maybe "Cycles where nothing is
executed" would be ok for CYCLE_ACTIVITY.CYCLES_NO_EXECUTE?
thanks,
julia
Powered by blists - more mailing lists