(1) opcontrol --setup, if it failed, the oProfile is not built in your android kernel.
you need to enable the CONFIG_OPROFILE=y CONFIG_PROFILING=y CONFIG_OPROFILE_ARMV6=y (2) If the opcontrol --setup successed. cat /dev/oproflie/cpu_type check whether it is arm/armv6 Seems google android supports arvm6 by default. (3) opcontrol --event TLB_MISS:150000 (you can change the events) (4) echo 1 >/dev/oprofile/enable to start profiling (seems "opcontrol --start" not work). (5) opcontrol --status ,check whether oprofiled is runing or not (6) echo 0 >/dev/oprofile/enable to stop the profiling(seems opcontrol --stop not work). Sample data will be collected to /data/oprofile/samples/current/ On Feb 23, 5:22 pm, luyen <nvlu...@gmail.com> wrote: > an user has this question: > > Does anyone try the tool "oprofile" in the source code folder > "external". > When I use command "oprofile-r start", it will show "Unable to open > cpu_type file for reading Make sure you have done opcontrol --init" > After I finish opcontrol --init, it show the same. > Does I need to set up something first, there is no guide to tell how > to use it. > > from:http://androidcore.com/android-community.html?func=view&catid=22&id=17 > > Does anyone has the answer? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---