linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: acme@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: callchain sampling bug in perf?
Date: Sun, 15 Aug 2010 18:53:59 -0400	[thread overview]
Message-ID: <20100815225359.GA32152@infradead.org> (raw)

I'm trying to play with perf record -g, that is sampling the callchains.
Doing this with simple workloads works fine, but when I try to do this
with compilebench a lot of samples seem to get lost.

I'm doing the following:

perf probe --add xlog_sync
perf record -g -e probe:xlog_sync -- ./compilebench

Trying to report it I do not get any callchains at all:

[root@virtlab106 compilebench-0.6]# perf report -g flat -n
# Events: 9K cycles
#
# Overhead  Samples         Command      Shared Object     Symbol
# ........ ..........  ............  .................  .........
#
    70.41%       6757  compilebench  [kernel.kallsyms]  [k] xlog_sync
    22.61%       2170          sync  [kernel.kallsyms]  [k] xlog_sync
     3.89%        373            sh  [kernel.kallsyms]  [k] xlog_sync
     2.50%        240        python  [kernel.kallsyms]  [k] xlog_sync
     0.33%         32         :3881  [kernel.kallsyms]  [k] xlog_sync
     0.13%         12         :3971  [kernel.kallsyms]  [k] xlog_sync
     0.11%         11         :3956  [kernel.kallsyms]  [k] xlog_sync
     0.01%          1         :3972  [kernel.kallsyms]  [k] xlog_sync

Doing a perf report -g flat,0.0 -n shows lots of callgraph, but the
percentag for them doesn't add up at all.


             reply	other threads:[~2010-08-15 22:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 22:53 Christoph Hellwig [this message]
2010-08-19  0:57 ` callchain sampling bug in perf? Frederic Weisbecker
     [not found]   ` <20100819085700.GB8782@infradead.org>
2010-08-19 15:04     ` Arnaldo Carvalho de Melo
2010-08-20  9:16       ` Christoph Hellwig
2010-08-20 19:12         ` Arnaldo Carvalho de Melo
2010-08-21  2:29           ` Frederic Weisbecker
2010-08-21 14:44           ` Christoph Hellwig
2010-08-21  2:47         ` Frederic Weisbecker
2010-08-21 14:42           ` Christoph Hellwig
2010-08-21 14:46             ` Christoph Hellwig
2010-08-22  5:20               ` Frederic Weisbecker
2010-08-22  8:11                 ` Christoph Hellwig
2010-08-22  0:49             ` Frederic Weisbecker

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=20100815225359.GA32152@infradead.org \
    --to=hch@infradead.org \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).