https://community.intel.com/t5/Analyzers/Problem-getting-VTune-to-instrument-code-with-a-custom-kernel/m-p/994913#M11720 <DIV>Any time you change the kernel, you will need to rebuild the driver (build-driver script) as root. If this succeeds, the driver will be loaded (use 'lsmod' and look for a driver witha name that starts with 'vtune_drv')and you can run a sampling activity.</DIV> <DIV></DIV> <DIV>An application module like testProgram.o should never show up in Other32, unless the driver does not match the kernel (that is what the build-driver script is for). However, without symbols for the kernel, you may see samples in Other32. Building the kernel with -g is all that should be required. Just make sure the symbols aren't stripped in the finally link step of the build.</DIV> Tue, 01 Mar 2005 02:45:42 GMT David_A_Intel1 2005-03-01T02:45:42Z https://community.intel.com/t5/Analyzers/Problem-getting-VTune-to-instrument-code-with-a-custom-kernel/m-p/994912#M11719 <DIV><FONT size="2"> <P>Hello,</P> <P></P></FONT><FONT face="Times New Roman">With a standard Redhat Enterprise 3.0WS installation running on a Pentium M, using a Sampling Activity, I have successfully analysed an object file (testProgram.o). I can drill down into this object and see in which functions the CPU is being spent etc... <P></P> <P>My problem is that after creating a custom kernel, VTune can no longer instrument this object file. It seems to have categorised it under the "other32" module. I've rebuilt the kernel again with the gcc -g option enabled in the top level Makefile under CFLAGS and CFLAGS_KERNEL but this seems to have had no effect. </P> <P>I ran the /opt/intel/vtune/vdk/src/build-kernel script which reported that the sampling driver failed to build successfully, but there was no apparent warnings/errors reported. Running the build-driver script from the same directory passes. </P> <P>Are there any specific kernel options that I should have enabled for this to work?</P> <P>Any help you can give would be appreciated. </P> <P>Thanks.</P></FONT></DIV> Mon, 28 Feb 2005 17:52:22 GMT https://community.intel.com/t5/Analyzers/Problem-getting-VTune-to-instrument-code-with-a-custom-kernel/m-p/994912#M11719 Adrian_H_Intel 2005-02-28T17:52:22Z https://community.intel.com/t5/Analyzers/Problem-getting-VTune-to-instrument-code-with-a-custom-kernel/m-p/994913#M11720 <DIV>Any time you change the kernel, you will need to rebuild the driver (build-driver script) as root. If this succeeds, the driver will be loaded (use 'lsmod' and look for a driver witha name that starts with 'vtune_drv')and you can run a sampling activity.</DIV> <DIV></DIV> <DIV>An application module like testProgram.o should never show up in Other32, unless the driver does not match the kernel (that is what the build-driver script is for). However, without symbols for the kernel, you may see samples in Other32. Building the kernel with -g is all that should be required. Just make sure the symbols aren't stripped in the finally link step of the build.</DIV> Tue, 01 Mar 2005 02:45:42 GMT https://community.intel.com/t5/Analyzers/Problem-getting-VTune-to-instrument-code-with-a-custom-kernel/m-p/994913#M11720 David_A_Intel1 2005-03-01T02:45:42Z