[root@test175 boot]# opcontrol --init
[root@test175 boot]# opcontrol --vmlinux=/boot/vmlinuz-2.6.32-220.el6.x86_64
[root@test175 boot]# opcontrol --start
The specified file /boot/vmlinuz-2.6.32-220.el6.x86_64does not seem to be valid
Make sure you are using the non-compressed image file (e.g. vmlinux not vmlinuz)
This topic has been locked.
3 replies Latest Post - 2012-09-29T07:46:43Z by pperf
Pinned topic How to uncompress Linux kernel so that oprofile can recognize it?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-09-29T07:46:43Z at 2012-09-29T07:46:43Z by pperf
Re: How to uncompress Linux kernel so that oprofile can recognize it?2012-09-27T11:11:17Z in response to pperffound the solutionFor Red Hat, need to install kernel-debuginfo rpmthen load the uncompressed kernel at /usr/lib/debug/lib/modules/2.6.32-220.el6.ppc64/vmlinux
Bill_Buros 270000QDEP73 PostsACCEPTED ANSWER
Re: How to uncompress Linux kernel so that oprofile can recognize it?2012-09-27T13:15:22Z in response to pperfYeah, RedHat can be annoying in this respect - you have to hunt down the extra media and install the RPMs. The SLES compressed kernel can be unzipped in place - very nice.There is code in the lpcpu package which can be used to help guide you through the steps when the oprofile profiler is specified. This challenge with the RedHat kernel-debuginfo has actually caused us to remove oprofile from the default list of profilers..