public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Stephane Eranian <eranian@google.com>,
	Andi Kleen <andi@firstfloor.org>,
	Minchan Kim <minchan@kernel.org>
Subject: Re: [RFC/PATCH] perf stat: Show sample events stat for a data file
Date: Fri, 8 May 2015 16:46:20 +0200	[thread overview]
Message-ID: <20150508144620.GN27504@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150429115822.GA31120@danjae.kornet>

On Wed, Apr 29, 2015 at 08:58:22PM +0900, Namhyung Kim wrote:
> > It would be nice if this thing could support 'perf record -s' which
> > enables perf_event_attr::inherit_stat, which in turn results in
> > PERF_RECORD_READ entries after every PERF_RECORD_EXIT which give the
> > total number of events for each recorded task.
> 
> Hmm.. this is one of the areas that I don't understand what's going
> on.  It'd be nice if you can help me understand and possibly improve
> the doc too.
> 
> So the combination of 'perf record -s' and 'perf report -T' should
> show some per-thread counter values, right?  I've found a bug on it.

Right, they should. perf-record -s should give the event count per
monitored thread, which when summed, should match what perf-stat gives
for that workload.

And agreed on the bug, I can see it too.

> Anyway, I don't understand the numbers it shows.

Me neither. I don't quite know why it has 5 cycles columns, we only
measure the one cycles event.

> 
> So the cycles values on 'perf report -T' are a lot more than the value
> of perf stat.  And I have no idea why it shows 5 different cycles for
> each thread.  Could you shed some light on this?

Sadly no, not making sense. But I can confirm this is what it does.

Lemme go poke at this, its weird.

  reply	other threads:[~2015-05-08 14:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29  7:27 [RFC/PATCH] perf stat: Show sample events stat for a data file Namhyung Kim
2015-04-29  7:42 ` Jiri Olsa
2015-04-29  7:58   ` Namhyung Kim
2015-04-29  9:27 ` Peter Zijlstra
2015-04-29 11:58   ` Namhyung Kim
2015-05-08 14:46     ` Peter Zijlstra [this message]
2015-05-09 14:39       ` Namhyung Kim

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=20150508144620.GN27504@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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