Re: oprofile-0.9.7 can't open unit mask description file

[Colin W. <cwe...@ai...>]

I also had this problem as support for mips octeon chip type is not in
oprofiler.
I did find a patch to add support in an old oprofile post from 2007, which
got me over this.
Have a search to see if an equivalent patch has been made before.
Also here's the link to my patch so that you can see the places where
changes need to be made for your chip: 
http://old.nabble.com/-PATCH--Support-for-Cavium-Octeon-performance-counters-td10026688.html


ljpapuga wrote:
> 
> Thanks for help Colin.
> 
> This helps with the second part of my problem, now oprofile can read the
> unit mask descriptor file. 
> Unfortunately, it still aims for the 34K platform. Compiling with
> --host=mipsisa32r2-timesys-linux-gnu didn't help. 
> I realized that oprofile parses the content of /dev/oprofile/cpu_type file
> and I can see that the cpu_type specified is indeed mips 34K. However,
> /proc/cpuinfo states that my cpu has 4 1004Kc processors. Now I wonder how
> does oprofile set the parameters in this file.
> 
> 
> Colin Wernham wrote:
>> 
>> The --host needs to specify the entire arch-chip-os etc for the target.
>> For Mips octeon I use:
>> --host=mips64-octeon-linux-gnu.
>> 
>> Also before running ./opcontrol, make the subdirectory ./mips/1004k and
>> copy the contents of oprofile-0.9.7/events/mips/1004k into it.
>> And also set the env variable OPROFILE_EVENTS_DIR to the path to where
>> your oprofile is.
>>  
>> Colin Wernham
>> 
>> 
> 
> 
-- 
View this message in context: http://old.nabble.com/oprofile-0.9.7-can%27t-open-unit-mask-description-file-tp33194903p33201438.html
Sent from the oprofile-list mailing list archive at Nabble.com.