NoteThe VTune(TM) Performance Analyzer requires line number information and symbol information provided in the executable in order to display the function names in sampling and call graph views.
If the VTune analyzer doesn't find symbol information for a particular module, it cannot display any source code for functions within that module. Instead, it displays the content of the module as assembly language.
The following topics provide instructions on how to generate symbol and line number information using several popular compilers:
NoteGenerating line number and symbol information preserves any existing optimizations in the monitored application.
In order to drill down to kernel hotspots, a kernel file (for example, vmlinux) must be uncompressed and not be stripped of symbols. In order to drill down further to kernel sources, this kernel file must also be compiled with debug information.
Linux vendors typically release kernel files that are compressed and stripped of symbols (for example, vmlinuz). Some vendors, such as Red Hat* and Novell* SUSE*, may provide special debug versions of their kernels for some of their distros, which may be suitable for the VTune analzyer to drill down to sources.
The README for the VTune Performance Analyzer Driver Kit, installed, by default, in: /opt/intel/vtune/vdk/src provides the following information:
how to obtain debug versions of kernels from some Linux vendors of supported distros.
how to manually (re)build a version of the kernel with debug information, from kernel sources.
Once a debug version of the kernel is created/obtained, specify that kernel file (for example, vmlinux) when drilling down to Hotspot View.