From: Ingo Molnar <mingo@elte.hu>
To: Wim Heirman <wim@heirman.net>
Cc: linux-kernel@vger.kernel.org,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: perf-stat per thread results
Date: Fri, 13 May 2011 17:30:28 +0200 [thread overview]
Message-ID: <20110513153028.GC3854@elte.hu> (raw)
In-Reply-To: <BANLkTimTOTz4qNwYPa6Ey7=QRjOhQHWt-Q@mail.gmail.com>
* Wim Heirman <wim@heirman.net> 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? [...]
Not at the moment, but it would be a useful feature.
> [...] 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. Or, alternatively, can I use perf record --stat and
> get an exact count for each performance counter?
Yes perf record --stat should work. 'perf report -T --stdio' is supposed to
print this, but it has regressed i think.
Arnaldo, any ideas?
Thanks,
Ingo
next prev parent reply other threads:[~2011-05-13 15:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 15:14 perf-stat per thread results Wim Heirman
2011-05-13 15:30 ` Ingo Molnar [this message]
2011-05-13 15:41 ` David Ahern
2011-05-13 15:35 ` David Ahern
2011-05-13 15:44 ` Ingo Molnar
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=20110513153028.GC3854@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.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 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.