From: Blanco Alejandro-E. <Ale...@mo...> - 2011-08-24 21:00:23
|
I'm trying to get oprofile working under Android on an OMAP4 Blaze board. I'm running into trouble getting it going. I see this: $ opcontrol --setup Unable to open cpu_type file for reading Make sure you have done opcontrol --init Please ignore the above error if running opcontrol --setup mount: No such device do_setup failed I looked at the source, and it says: if (system("mount -t oprofilefs nodev "OP_DRIVER_BASE)) { return -1; and #define OP_DRIVER_BASE "/dev/oprofile" I'm a bit confused on the mount command, because when I look at the mount man page, it says nodev is an option, and there should be a device as the 2nd to last param. Must be something simple? Any help appreciated. FYI, I followed instructions I found at omappedia. Alex |
From: William C. <wc...@re...> - 2011-08-24 21:55:01
|
On 08/24/2011 04:59 PM, Blanco Alejandro-EAB005 wrote: > I'm trying to get oprofile working under Android on an OMAP4 Blaze board. I'm running into trouble getting it going. I see this: > > $ opcontrol --setup > Unable to open cpu_type file for reading > Make sure you have done opcontrol --init > Please ignore the above error if running opcontrol --setup > mount: No such device > do_setup failed > > I looked at the source, and it says: > > if (system("mount -t oprofilefs nodev "OP_DRIVER_BASE)) { > return -1; > and > > #define OP_DRIVER_BASE "/dev/oprofile" > > I'm a bit confused on the mount command, because when I look at the mount man page, it says nodev is an option, and there should be a device as the 2nd to last param. Must be something simple? Any help appreciated. > > FYI, I followed instructions I found at omappedia. > > Alex Hi Alex, It looks like the android oprofile has its own version of opcontrol (opcontrol.cpp). I am not familiar with it. Sure that running kernel has the oprofile support in it? You might try to do the "mkdir /dev/oprofile" and "mount -t oprofilefs nodev /dev/oprofile" on the command line to debug what is going on. -Will |
From: Blanco Alejandro-E. <Ale...@mo...> - 2011-08-25 13:41:40
|
I did pick up a patch that claims to support oprofile for the kernel. I tried at the command line, but get the same error. What is confusing me, is that I understand why that command fails by reading the mount man page, because nodev is not a device, and the man page says it is an option that can be used with -o. Can someone explain what device is trying to be mounted? Is nodev something that an oprofile-enabled kernel should recognize? Alex -----Original Message----- From: William Cohen [mailto:wc...@re...] Sent: Wednesday, August 24, 2011 5:55 PM To: Blanco Alejandro-EAB005 Cc: opr...@li... Subject: Re: mount: No such device On 08/24/2011 04:59 PM, Blanco Alejandro-EAB005 wrote: > I'm trying to get oprofile working under Android on an OMAP4 Blaze board. I'm running into trouble getting it going. I see this: > > $ opcontrol --setup > Unable to open cpu_type file for reading Make sure you have done > opcontrol --init Please ignore the above error if running opcontrol > --setup > mount: No such device > do_setup failed > > I looked at the source, and it says: > > if (system("mount -t oprofilefs nodev "OP_DRIVER_BASE)) { > return -1; > and > > #define OP_DRIVER_BASE "/dev/oprofile" > > I'm a bit confused on the mount command, because when I look at the mount man page, it says nodev is an option, and there should be a device as the 2nd to last param. Must be something simple? Any help appreciated. > > FYI, I followed instructions I found at omappedia. > > Alex Hi Alex, It looks like the android oprofile has its own version of opcontrol (opcontrol.cpp). I am not familiar with it. Sure that running kernel has the oprofile support in it? You might try to do the "mkdir /dev/oprofile" and "mount -t oprofilefs nodev /dev/oprofile" on the command line to debug what is going on. -Will |