All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
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: Fri, 16 Oct 2009 10:41:26 +1100	[thread overview]
Message-ID: <20091015234126.GI4808@kryten> (raw)
In-Reply-To: <20091015122839.GA4960@nowhere>


Hi,

> > 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.
>
> Hmm, could you please send me a perf.data where you can see that?
> Does that only happen on powerpc?

I can replicate this on x86 by taking a perf.data and truncating it
after the first sample+backtrace:


# wget http://samba.org/~anton/perf_truncated.test


# perf report -i perf_truncated.test -g fractal
...
   100.00%     perf  [kernel]       [k] native_write_msr_safe


# perf report -i perf_truncated.test -g flat
...
   100.00%     perf  [kernel]       [k] native_write_msr_safe
           100.00%
                native_write_msr_safe
                intel_pmu_enable_all
                hw_perf_enable
                perf_enable
                __perf_counter_enable
                smp_call_function_single
                task_oncpu_function_call
                perf_counter_enable
                perf_counter_for_each_child
                perf_ioctl
                vfs_ioctl
                do_vfs_ioctl
                sys_ioctl
                system_call_fastpath
                0x7f00c1857537

  reply	other threads:[~2009-10-15 23:44 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
2009-10-15 23:41   ` Anton Blanchard [this message]
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=20091015234126.GI4808@kryten \
    --to=anton@samba.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=fweisbec@gmail.com \
    --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 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.