Re: Regarding vmlinux file for opcontrol --init

On Mon, 27 Feb 2017, dhara buch wrote:
> Hello,

Hi Dhara,

> 
> I have installed Oprofile-0.9.9 on Ubuntu 15.10. I try to init oprofile with'
> opcontrol --init command, which requires uncompressed vmlinux file with --vmlinux option.
> 
> I have tried to uncompress the present vmlinuz with extract-vmlinux script. The file gts uncompressed,but when I init opcontrol with this uncompressed file, my CPU type gets wrongly
> identified. Hence, although the hardware events are supported by the processor, 'timer' mode gets set and event monitoring doesn't become possible.

You can test the CPU identification by running `ophelp -r` which should
print what OProfile thinks your CPU is, such as:

$ ophelp -r
Intel Skylake microarchitecture

What is your CPU type? OProfile 0.9.9 is pretty old, it might not support
the newer processors. Consider using the latest OProfile 1.1. It might not
fit you if you need the legacy opcontrol-based profiling mode (which was
removed from 1.0 and above), but since you probably want to use the CPU
hardware events, I guess, operf-mode (and oprofile-1.1) should serve you
well.

Regards,
Michael

> 
> I would be thankful if anybody can guide me to solve this problem.
> 
> Dhara Buch
> 
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot