linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Wim Heirman <wim@heirman.net>, Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	"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:02:30 -0600	[thread overview]
Message-ID: <4DCDB886.7090909@gmail.com> (raw)
In-Reply-To: <BANLkTi=UKJ2Ztkcui_+8UHF16b_8mTvpnA@mail.gmail.com>



On 05/13/11 14:32, Wim Heirman wrote:
> Hi,
> 
>> 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.
> 
> Thanks, this is exactly what I'm looking for. In 2.6.32 (Ubuntu 10.04)
> it works, although if I use --pid rather than the -- <command> variant
> the first thread seams to be missing. In 2.6.38 (Ubuntu 11.04) the
> first thread is missing in both use cases, and I get one column per
> processor (which in itself is fine).
> 
> Regards,
> Wim

Hmm.... my mileage varies using latest kernel
(446cc6345d3de6571bdd0840f48aca441488a28d)

$ /tmp/build-perf/perf record --stat -fo /tmp/perf.data -p $(pidof rsyslogd)
^C[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.007 MB /tmp/perf.data (~308 samples) ]

$ /tmp/build-perf/perf report -T -i /tmp/perf.data
# Events: 6  cycles
#
# Overhead   Command      Shared Object                      Symbol
# ........  ........  .................  ..........................
#
    97.61%  rsyslogd  libc-2.13.so       [.] __libc_disable_asynccancel
     2.39%  rsyslogd  [kernel.kallsyms]  [k] native_write_msr_safe


#
# (For a higher level overview, try: perf report --sort comm,dso)
#
# PID  TID


ie., I do not get the counter values. Specifying the counter with -e
(e.g., -e branch-misses) does not help -- still no counter output.

David

  parent reply	other threads:[~2011-05-13 23:02 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
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 [this message]
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=4DCDB886.7090909@gmail.com \
    --to=dsahern@gmail.com \
    --cc=Brice.Goglin@inria.fr \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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;
as well as URLs for NNTP newsgroup(s).