All of lore.kernel.org
 help / color / mirror / Atom feed
* perf: documentation for cycles_no_execute event
@ 2017-12-29 10:58 Julia Lawall
  2018-01-08 14:00 ` Jiri Olsa
  0 siblings, 1 reply; 4+ messages in thread
From: Julia Lawall @ 2017-12-29 10:58 UTC (permalink / raw)
  To: Peter Zijlstra, Ingo Molnar, Arnaldo Carvalho de Melo,
	Alexander Shishkin, Jiri Olsa, Namhyung Kim, linux-kernel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: perf: documentation for cycles_no_execute event
  2017-12-29 10:58 perf: documentation for cycles_no_execute event Julia Lawall
@ 2018-01-08 14:00 ` Jiri Olsa
  2018-01-08 21:10   ` Andi Kleen
  0 siblings, 1 reply; 4+ messages in thread
From: Jiri Olsa @ 2018-01-08 14:00 UTC (permalink / raw)
  To: Julia Lawall
  Cc: Peter Zijlstra, Ingo Molnar, Arnaldo Carvalho de Melo,
	Alexander Shishkin, Namhyung Kim, linux-kernel, Andi Kleen

On Fri, Dec 29, 2017 at 11:58:42AM +0100, Julia Lawall wrote:
> Hello,

hi,
adding Andi in cc, he should be able to answer this

thanks,
jirka

> 
> 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

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: perf: documentation for cycles_no_execute event
  2018-01-08 14:00 ` Jiri Olsa
@ 2018-01-08 21:10   ` Andi Kleen
  2018-01-08 21:18     ` Julia Lawall
  0 siblings, 1 reply; 4+ messages in thread
From: Andi Kleen @ 2018-01-08 21:10 UTC (permalink / raw)
  To: Jiri Olsa
  Cc: Julia Lawall, Peter Zijlstra, Ingo Molnar,
	Arnaldo Carvalho de Melo, Alexander Shishkin, Namhyung Kim,
	linux-kernel, Andi Kleen

> > 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?

Yes it's all in cycles

Will clarify in a future event list update.

-Andi

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: perf: documentation for cycles_no_execute event
  2018-01-08 21:10   ` Andi Kleen
@ 2018-01-08 21:18     ` Julia Lawall
  0 siblings, 0 replies; 4+ messages in thread
From: Julia Lawall @ 2018-01-08 21:18 UTC (permalink / raw)
  To: Andi Kleen
  Cc: Jiri Olsa, Peter Zijlstra, Ingo Molnar, Arnaldo Carvalho de Melo,
	Alexander Shishkin, Namhyung Kim, linux-kernel



On Mon, 8 Jan 2018, Andi Kleen wrote:

> > > 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?
>
> Yes it's all in cycles
>
> Will clarify in a future event list update.

Thanks.

julia

^ permalink raw reply	[flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-01-08 21:18 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-12-29 10:58 perf: documentation for cycles_no_execute event Julia Lawall
2018-01-08 14:00 ` Jiri Olsa
2018-01-08 21:10   ` Andi Kleen
2018-01-08 21:18     ` Julia Lawall

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.