Re: [PATCH 1/6] perf: Fix orphan callchain branches

[Frederic Weisbecker]

On Fri, May 21, 2010 at 06:15:21PM +1000, Anton Blanchard wrote:
> 
> Hi,
> 
> > From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
> > 
> > Callchains have markers inside their capture to tell we
> > enter a context (kernel, user, ...).
> > 
> > Those are not displayed in the callchains but they are
> > incidentally an active part of the radix tree where
> > callchains are stored, just like any other address.
> > 
> > If we have the two following callchains:
> > 
> > addr1 -> addr2 -> user context -> addr3
> > addr1 -> addr2 -> user context -> addr4
> > addr1 -> addr2 -> addr 5
> > 
> > This is pretty common if addr1 and addr2 are part of an
> > interrupt path, addr3 and addr4 are user addresses and
> > addr5 is a kernel non interrupt path.
> > 
> > This will be stored as follows in the tree:
> > 
> >                    addr1
> >                    addr2
> >                    /   \
> >                   /     addr5
> >             user context
> >                /    \
> >              addr3  addr4
> > 
> > But we ignore the context markers in the report, hence
> > the addr3 and addr4 will appear as orphan branches:
> > 
> >     |--28.30%-- hrtimer_interrupt
> >     |          smp_apic_timer_interrupt
> >     |          apic_timer_interrupt
> >     |          |           <------------- here, no parent!
> >     |          |          |
> >     |          |          |--11.11%-- 0x7fae7bccb875
> >     |          |          |
> >     |          |          |--11.11%-- 0xffffffffff60013b
> >     |          |          |
> >     |          |          |--11.11%-- __pthread_mutex_lock_internal
> >     |          |          |
> >     |          |          |--11.11%-- __errno_location
> > 
> > Fix this by removing the context markers when we process the
> > callchains to the tree.
> 
> I noticed some weird perf report output from a git pull today:
> 
>     38.61%      yes  libc-2.9.so         [.] fputs_unlocked
>                 |
>                 --- fputs_unlocked
>                     fputs_unlocked
>                    |          
>                    |--94.43%-- 0x10001370
>                    |          0xfff869ad33c
>                    |          __libc_start_main
>                    |          (nil)
>                    |          
>                     --5.57%-- 0xfff869ad33c
>                               __libc_start_main
>                               (nil)
> 
>                 |
>                 --- _IO_file_xsputn
>                     fputs_unlocked
>                    |          
>                    |--90.33%-- 0x10001370
>                    |          0xfff869ad33c
>                    |          __libc_start_main
>                    |          (nil)
>                    |          
>                     --9.67%-- fputs_unlocked
>                               0x10001370
>                               0xfff869ad33c
>                               __libc_start_main
>                               (nil)
> 
> Notice how percentages are missing from fputs_unlocked and _IO_file_xsputn,
> and there is no ascii art line joining them. If I backout this patch things
> look better:
> 
>     38.61%      yes  libc-2.9.so         [.] fputs_unlocked
>                 |          
>                 |--42.92%-- fputs_unlocked
>                 |          fputs_unlocked
>                 |          |          
>                 |          |--94.43%-- 0x10001370
>                 |          |          0xfff869ad33c
>                 |          |          __libc_start_main
>                 |          |          (nil)
>                 |          |          
>                 |           --5.57%-- 0xfff869ad33c
>                 |                     __libc_start_main
>                 |                     (nil)
>                 |          
>                 |--28.94%-- _IO_file_xsputn
>                 |          fputs_unlocked
>                 |          |          
>                 |          |--90.33%-- 0x10001370
>                 |          |          0xfff869ad33c
>                 |          |          __libc_start_main
>                 |          |          (nil)
>                 |          |          
>                 |           --9.67%-- fputs_unlocked
>                 |                     0x10001370
>                 |                     0xfff869ad33c
>                 |                     __libc_start_main
>                 |                     (nil)
> 
> 
> All of these backtraces are completely in userspace and so shouldn't have any
> context markers. A check of a few raw backtraces confirms it:
> 
> 0x70e860 [0x60]: PERF_RECORD_SAMPLE(IP, 2): 11799/11799: 0xfff86a161a0 period: 366
> ... chain: nr:7
> .....  0: fffffffffffffe00
> .....  1: 00000fff86a161d0
> .....  2: 00000fff86a065d4
> .....  3: 0000000010001370
> .....  4: 00000fff869ad33c
> .....  5: 00000fff869ad55c
> .....  6: 0000000000000000
> 
> Anton


Hi Anton,

In fact it's a known bug. I just need to find the time
to sit down and fix that.

It happens when we sort by dsos (the default IIRC) and we have more
than one root of callchains attached to it.

This patch fixed another bug, which bug had the side effect to fix
the above ascii art breakage :) But in fact it wasn't fixing it
properly, and if you drop this patch, you'll see other tree output
breakages elsewhere, much worse as they also break the newt TUI.

I'll push some time on it.

Thanks.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/