Re: no location information

[Maynard J. <may...@us...>]

Andre Richter wrote:
> Hello all,
> 
> I've built an native 2.6.18 Kernel by myself, the source tree is in  
> standard place (/usr/src) and also /lib/modules/`uname -r`/built  
> points to it.
> Now when profiling the Kernel itself (networking speed test), i get  
> the following callgraph results:
> 
> Snippet:
> -------------------------------------------------------------------------------
> 187102   17.1590  (no location information)   vmlinux                   
> vmlinux                  e1000_clean
> 187102   100.000  (no location information)   vmlinux                   
> vmlinux                  e1000_clean [self]
> -------------------------------------------------------------------------------
> 137094   12.5728  (no location information)   vmlinux                   
> vmlinux                  e1000_intr
> 137094   100.000  (no location information)   vmlinux                   
> vmlinux                  e1000_intr [self]
> -------------------------------------------------------------------------------
If the vmlinux you build has debugging information in it, oprofile will find it. 
  Do 'objdump -h <my-vmlinux-file>' and look for sections that have the 
DEBUGGING flag.  The kernels I build (using 'make') always seem to include 
debugging sections.  I don't know how you would build a kernel without it.  Are 
you using rpmbuild on a kernel spec file?  Maybe that would strip the debugging 
stuff out.
> 
> When profiling under Xen, with a self-baked kernel too, opreport /  
> oprofile resolves the kernel symblos correctly to the source files:
> 
> 180156   11.4266  e1000_main.c:3430           vmlinux                   
> vmlinux                  e1000_clean
> 542497   74.4918  e1000_main.c:3630           vmlinux                   
> vmlinux                  e1000_clean_rx_irq
> 180156   24.7377  e1000_main.c:3430           vmlinux                   
> vmlinux                  e1000_clean [self]
Most distros have a separate debuginfo rpm you need to install in order to see 
this level of detail in oprofile reports.   Maybe you have some ancillary kernel 
rpm(s) that provide the needed debugging info.

-Maynard
> 
> What could possibly go wrong in my native setup?
> 
> Thank you in advance,
> Andre
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> oprofile-list mailing list
> opr...@li...
> https://lists.sourceforge.net/lists/listinfo/oprofile-list