public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Anton Blanchard <anton@samba.org>
Cc: mingo@elte.hu, paulus@samba.org, a.p.zijlstra@chello.nl,
	linux-kernel@vger.kernel.org
Subject: Re: perf report fractal output issue
Date: Thu, 15 Oct 2009 14:28:48 +0200	[thread overview]
Message-ID: <20091015122839.GA4960@nowhere> (raw)
In-Reply-To: <20091014225726.GF4808@kryten>

On Thu, Oct 15, 2009 at 09:57:26AM +1100, Anton Blanchard wrote:
> 
> Hi,
> 
> I noticed a problem where I wasn't always getting callchains:
> 
> # perf report
>     98.47%  lock1_processes  [kernel]                [k] .lock_kernel
> 
>      0.91%  lock1_processes  [kernel]                [k] .fput
> 
> 
> But a flat output confirmed the data is there:
> 
> # perf report -g flat
>     98.47%  lock1_processes  [kernel]                             [k] .lock_kernel
>             98.47%
>                 .lock_kernel
>                 .__posix_lock_file
>                 (nil)
>                 .fcntl_setlk
>                 .sys_fcntl
>                 syscall_exit
>                 0xfffb7d04844
>                 .testcase
>                 .testcase
>                 .affinitize
>                 .new_task
>                 .main
>                 0xfffb7c4933c
>                 0xfffb7c4955c
>                 (nil)
> 
> It looks like callchain__fprintf_graph() only prints the callchain if we
> have at least one rb entry at the top. In my case all the associated
> backtraces are identical so I assume we dont have to do any splitting.
> 
> Anton


Hmm, could you please send me a perf.data where you can see that?
Does that only happen on powerpc?


Thanks.


  reply	other threads:[~2009-10-15 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 22:57 perf report fractal output issue Anton Blanchard
2009-10-15 12:28 ` Frederic Weisbecker [this message]
2009-10-15 23:41   ` Anton Blanchard
2009-10-20 21:53     ` 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=20091015122839.GA4960@nowhere \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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