mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: perf: documentation for cycles_no_execute event
Date: Mon, 8 Jan 2018 22:18:08 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1801082217570.14062@hadrien> (raw)
In-Reply-To: <20180108211049.bbtq7uvaec3hhjyz@two.firstfloor.org>



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

      reply	other threads:[~2018-01-08 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 10:58 Julia Lawall
2018-01-08 14:00 ` Jiri Olsa
2018-01-08 21:10   ` Andi Kleen
2018-01-08 21:18     ` Julia Lawall [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1801082217570.14062@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®