mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: David Ahern <dsahern@gmail.com>
Cc: "Wim Heirman" <wim@heirman.net>,
	linux-kernel@vger.kernel.org,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Brice Goglin" <Brice.Goglin@inria.fr>
Subject: Re: perf-stat per thread results
Date: Fri, 13 May 2011 17:44:10 +0200	[thread overview]
Message-ID: <20110513154410.GA6373@elte.hu> (raw)
In-Reply-To: <4DCD4FC5.8020608@gmail.com>


* David Ahern <dsahern@gmail.com> wrote:

> On 05/13/11 09:14, Wim Heirman wrote:
> > Hi all,
> > 
> > I'm using perf-stat to look at hardware performance counters for a
> > parallel program. Is there a way to get counter values for each thread
> > individually, rather than aggregated for the whole process? I know I
> > can attach to a specific thread using --tid=, but due to the time
> > required to find the tid and attach/detach this isn't accurate for
> > short-running programs.
> 
> perf-stat requires changes to dump counters per thread; it currently
> sums all threads into a single value.
> 
> > Or, alternatively, can I use perf record --stat and get an exact count
> > for each performance counter?
> 
> perf-record does not read values from hardware counters.

It's supposed to do that if --stat is specified, and it used to work - see this 
commit:

  8d51327090ac: perf report: Fix and improve the displaying of per-thread event counters

and the output there:

     #  PID   TID  cache-misses  cache-references
       4658  4659        495581           3238779
       4658  4662        498246           3236823
       4658  4663        499531           3243162

which appears to be roughly what Wim is asking for, AFAICT.

But this seems to have regressed meanwhile.

Thanks,

	Ingo

  reply	other threads:[~2011-05-13 15:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 15:14 Wim Heirman
2011-05-13 15:30 ` Ingo Molnar
2011-05-13 15:41   ` David Ahern
2011-05-13 15:35 ` David Ahern
2011-05-13 15:44   ` Ingo Molnar [this message]
2011-05-13 20:32     ` Wim Heirman
2011-05-13 20:45       ` Arnaldo Carvalho de Melo
2011-05-14 12:45         ` Wim Heirman
2011-05-14 20:24           ` Wim Heirman
2011-05-13 23:02       ` David Ahern
2011-05-14 12:49         ` Wim Heirman
2011-05-14 17:48           ` David Ahern
2011-05-14 18:52             ` Wim Heirman
2011-05-14 18:57               ` David Ahern
2011-05-13 20:11 ` Juri Lelli

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=20110513154410.GA6373@elte.hu \
    --to=mingo@elte.hu \
    --cc=Brice.Goglin@inria.fr \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wim@heirman.net \
    /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

Powered by JetHome