From: Monthadar Al J. <mon...@gm...> - 2009-03-18 14:46:52
|
Hi, I have a problem that I could not find a solution to. I am using oprofile in VMWare with Host:Win2000 Guest:Kubuntu 8.04. I didn't know that I can't use performance counters inside a virtual machine, and now I can't remove the event to use timer interrupts instead. I tried to delete the file in /root/.oprofile/daemonrc but it didn't help. If I just modprobe oprofile with timer=1 and then opcontroll --start, then I can't run any command, I always get a failure message that I can't use events in timer mode. I can't even --deinit! Any suggestions on how I can remove an event and run in timer interrupt? Thank you. -- //Monthadar Al Jaberi |
From: Maynard J. <may...@us...> - 2009-03-18 18:38:37
|
Monthadar Al Jaberi wrote: > Hi, I have a problem that I could not find a solution to. I am using > oprofile in VMWare with Host:Win2000 Guest:Kubuntu 8.04. > > I didn't know that I can't use performance counters inside a virtual > machine, and now I can't remove the event to use timer interrupts > instead. I tried to delete the file in /root/.oprofile/daemonrc but it > didn't help. If I just modprobe oprofile with timer=1 and then How are you doing this? You should edit the opcontrol script where it does the 'modprobe oprofile'. > opcontroll --start, then I can't run any command, I always get a > failure message that I can't use events in timer mode. I can't even > --deinit! Any suggestions on how I can remove an event and run in > timer interrupt? If you succeed in forcing oprofile to use timer mode, you should see /dev/oprofile/cpu_type be 'timer'. If you haven't been able to deinit, then I don't see how you could have successfully set the module to timer mode yet. You say you "can't even --deinit". What's the error? -Maynard > > Thank you. > |
From: Monthadar Al J. <mon...@gm...> - 2009-03-19 10:00:51
|
On Wed, Mar 18, 2009 at 7:38 PM, Maynard Johnson <may...@us...> wrote: > Monthadar Al Jaberi wrote: >> >> Hi, I have a problem that I could not find a solution to. I am using >> oprofile in VMWare with Host:Win2000 Guest:Kubuntu 8.04. >> >> I didn't know that I can't use performance counters inside a virtual >> machine, and now I can't remove the event to use timer interrupts >> instead. I tried to delete the file in /root/.oprofile/daemonrc but it >> didn't help. If I just modprobe oprofile with timer=1 and then > > How are you doing this? You should edit the opcontrol script where it does > the 'modprobe oprofile'. I modprobe it like: sudo modprobe oprofile timer=1 I don't know how to edit opcontrol, if I just put timer=1 in front of modeprobe oprilfe it will give the same error... What I do is: sudo modprobe oprofile timer=1 sudo opcontrol --start then I get an error saying: You cannot specify any performance counter events because OProfile is in timer mode. >> >> opcontroll --start, then I can't run any command, I always get a >> failure message that I can't use events in timer mode. I can't even >> --deinit! Any suggestions on how I can remove an event and run in >> timer interrupt? > > If you succeed in forcing oprofile to use timer mode, you should see > /dev/oprofile/cpu_type be 'timer'. If you haven't been able to deinit, then > I don't see how you could have successfully set the module to timer mode > yet. You say you "can't even --deinit". What's the error? > > -Maynard I get the same error mentioned above. it is running in timer mode, I can see that from dmesg: [70115.334630] oprofile: using timer interrupt. After I --start oprofile, the cpy_type is set to timer like you say. At this point I can't do anything! I can't even modprobe -r it will just give me: FATAL: Module oprofile is in use. The only thing I can do is resart the VMWare. So how do I remove events? Thank you. -- //Monthadar Al Jaberi |
From: Maynard J. <may...@us...> - 2009-03-19 14:26:33
|
Monthadar Al Jaberi wrote: > On Wed, Mar 18, 2009 at 7:38 PM, Maynard Johnson <may...@us...> wrote: >> Monthadar Al Jaberi wrote: >>> Hi, I have a problem that I could not find a solution to. I am using >>> oprofile in VMWare with Host:Win2000 Guest:Kubuntu 8.04. >>> >>> I didn't know that I can't use performance counters inside a virtual >>> machine, and now I can't remove the event to use timer interrupts >>> instead. I tried to delete the file in /root/.oprofile/daemonrc but it >>> didn't help. If I just modprobe oprofile with timer=1 and then >> How are you doing this? You should edit the opcontrol script where it does >> the 'modprobe oprofile'. > > I modprobe it like: sudo modprobe oprofile timer=1 > > I don't know how to edit opcontrol, if I just put timer=1 in front of > modeprobe oprilfe it will give the same error... > > What I do is: > sudo modprobe oprofile timer=1 Yes, it should be OK to do it this way. Disregard my previous comment about editing opcontrol > sudo opcontrol --start This would fail unless one of the following was true: 1) you had just previously run 'opcontrol --no-vmlinux (or --vmlinux=<path-to-vmlinux file>)' 2) you have an existing daemonrc file with VMLINUX=none (or <path-to-vmlinux file>) > > then I get an error saying: > You cannot specify any performance counter events > because OProfile is in timer mode. hmmm . . . the only way I can see you getting that error is if the daemonrc file still exists. Let's try a few different things to gather information about oprofile status: 1. Do 'opcontrol --status' 2. Do 'cat /root/.oprofile/daemonrc' 3. Do 'ps awx | grep oprofiled' >From the above commands, what event(s) does opcontrol think you're specifying? If you see the daemonrc file still exists, then delete it and run the following commands: 1. 'opcontrol --deinit' 2. 'modprobe oprofile timer=1' 3. 'opcontrol --no-vmlinux' (or set the --vmlinux option appropriately) 4. 'opcontrol --start --verbose' If this still doesn't work, post the output of each of the commands, as well as the output from the three commands I suggested above for gathering status information. -Maynard > >>> opcontroll --start, then I can't run any command, I always get a >>> failure message that I can't use events in timer mode. I can't even >>> --deinit! Any suggestions on how I can remove an event and run in >>> timer interrupt? >> If you succeed in forcing oprofile to use timer mode, you should see >> /dev/oprofile/cpu_type be 'timer'. If you haven't been able to deinit, then >> I don't see how you could have successfully set the module to timer mode >> yet. You say you "can't even --deinit". What's the error? >> >> -Maynard > > I get the same error mentioned above. > > it is running in timer mode, I can see that from dmesg: > [70115.334630] oprofile: using timer interrupt. > > After I --start oprofile, the cpy_type is set to timer like you say. > > At this point I can't do anything! I can't even modprobe -r it will > just give me: > FATAL: Module oprofile is in use. > > The only thing I can do is resart the VMWare. > > So how do I remove events? > > Thank you. > |
From: Monthadar Al J. <mon...@gm...> - 2009-03-20 08:49:57
|
On Thu, Mar 19, 2009 at 3:26 PM, Maynard Johnson <may...@us...> wrote: > Monthadar Al Jaberi wrote: >> On Wed, Mar 18, 2009 at 7:38 PM, Maynard Johnson <may...@us...> wrote: >>> Monthadar Al Jaberi wrote: >>>> Hi, I have a problem that I could not find a solution to. I am using >>>> oprofile in VMWare with Host:Win2000 Guest:Kubuntu 8.04. >>>> >>>> I didn't know that I can't use performance counters inside a virtual >>>> machine, and now I can't remove the event to use timer interrupts >>>> instead. I tried to delete the file in /root/.oprofile/daemonrc but it >>>> didn't help. If I just modprobe oprofile with timer=1 and then >>> How are you doing this? You should edit the opcontrol script where it does >>> the 'modprobe oprofile'. >> >> I modprobe it like: sudo modprobe oprofile timer=1 >> >> I don't know how to edit opcontrol, if I just put timer=1 in front of >> modeprobe oprilfe it will give the same error... >> >> What I do is: >> sudo modprobe oprofile timer=1 > Yes, it should be OK to do it this way. Disregard my previous comment about editing opcontrol >> sudo opcontrol --start > This would fail unless one of the following was true: > 1) you had just previously run 'opcontrol --no-vmlinux (or --vmlinux=<path-to-vmlinux file>)' > 2) you have an existing daemonrc file with VMLINUX=none (or <path-to-vmlinux file>) Indeed I have called opcontrol --vmlinux=<path> (after compiling a new kernel 2.6.28.7) >> >> then I get an error saying: >> You cannot specify any performance counter events >> because OProfile is in timer mode. > hmmm . . . the only way I can see you getting that error is if the daemonrc file still exists. Let's try a few different things to gather information about oprofile status: Ok, I restarted VMWare to get out of the problem, and am running your commands in a new fresh start. > 1. Do 'opcontrol --status' Daemon not running Event 0: CPU_CLK_UNHALTED:600000:0:1:1 Separate options: none vmlinux file: /usr/src/linux/vmlinux Image filter: none Call-graph depth: 20 > 2. Do 'cat /root/.oprofile/daemonrc' cat: /root/.oprofile/daemonrc: No such file or directory > 3. Do 'ps awx | grep oprofiled' 7877 pts/2 R+ 0:00 grep oprofiled i.e. not running > > From the above commands, what event(s) does opcontrol think you're specifying? If you see the daemonrc file still exists, then delete it and run the following commands: > 1. 'opcontrol --deinit' Daemon not running Unloading oprofile module > 2. 'modprobe oprofile timer=1' > 3. 'opcontrol --vmlinux=/usr/src/linux-2.6.28.7/' You cannot specify any performance counter events because OProfile is in timer mode. > 4. 'opcontrol --start --verbose' You cannot specify any performance counter events because OProfile is in timer mode. > If this still doesn't work, post the output of each of the commands, as well as the output from the three commands I suggested above for gathering status information. > > -Maynard >> You see what ever option I give opcontrol it gives the same error message, seems like a bug? even when I now type 'opcontrol --status': You cannot specify any performance counter events because OProfile is in timer mode. >>>> opcontroll --start, then I can't run any command, I always get a >>>> failure message that I can't use events in timer mode. I can't even >>>> --deinit! Any suggestions on how I can remove an event and run in >>>> timer interrupt? >>> If you succeed in forcing oprofile to use timer mode, you should see >>> /dev/oprofile/cpu_type be 'timer'. If you haven't been able to deinit, then >>> I don't see how you could have successfully set the module to timer mode >>> yet. You say you "can't even --deinit". What's the error? >>> >>> -Maynard >> >> I get the same error mentioned above. >> >> it is running in timer mode, I can see that from dmesg: >> [70115.334630] oprofile: using timer interrupt. >> >> After I --start oprofile, the cpy_type is set to timer like you say. >> >> At this point I can't do anything! I can't even modprobe -r it will >> just give me: >> FATAL: Module oprofile is in use. >> >> The only thing I can do is resart the VMWare. >> >> So how do I remove events? >> >> Thank you. >> > > -- //Monthadar Al Jaberi |
From: Maynard J. <may...@us...> - 2009-03-23 15:31:45
|
Monthadar Al Jaberi wrote: > On Thu, Mar 19, 2009 at 3:26 PM, Maynard Johnson <may...@us...> wrote: >> Monthadar Al Jaberi wrote: >>> On Wed, Mar 18, 2009 at 7:38 PM, Maynard Johnson <may...@us...> wrote: >>>> Monthadar Al Jaberi wrote: >>>>> Hi, I have a problem that I could not find a solution to. I am using >>>>> oprofile in VMWare with Host:Win2000 Guest:Kubuntu 8.04. >>>>> >>>>> I didn't know that I can't use performance counters inside a virtual >>>>> machine, and now I can't remove the event to use timer interrupts >>>>> instead. I tried to delete the file in /root/.oprofile/daemonrc but it >>>>> didn't help. If I just modprobe oprofile with timer=1 and then >>>> How are you doing this? You should edit the opcontrol script where it does >>>> the 'modprobe oprofile'. >>> I modprobe it like: sudo modprobe oprofile timer=1 >>> >>> I don't know how to edit opcontrol, if I just put timer=1 in front of >>> modeprobe oprilfe it will give the same error... >>> >>> What I do is: >>> sudo modprobe oprofile timer=1 >> Yes, it should be OK to do it this way. Disregard my previous comment about editing opcontrol >>> sudo opcontrol --start >> This would fail unless one of the following was true: >> 1) you had just previously run 'opcontrol --no-vmlinux (or --vmlinux=<path-to-vmlinux file>)' >> 2) you have an existing daemonrc file with VMLINUX=none (or <path-to-vmlinux file>) > > Indeed I have called opcontrol --vmlinux=<path> (after compiling a new > kernel 2.6.28.7) > >>> then I get an error saying: >>> You cannot specify any performance counter events >>> because OProfile is in timer mode. >> hmmm . . . the only way I can see you getting that error is if the daemonrc file still exists. Let's try a few different things to gather information about > oprofile status: > > Ok, I restarted VMWare to get out of the problem, and am running your > commands in a new fresh start. > >> 1. Do 'opcontrol --status' > Daemon not running > Event 0: CPU_CLK_UNHALTED:600000:0:1:1 > Separate options: none > vmlinux file: /usr/src/linux/vmlinux > Image filter: none > Call-graph depth: 20 > >> 2. Do 'cat /root/.oprofile/daemonrc' > cat: /root/.oprofile/daemonrc: No such file or directory I just don't see how you can get the above status information without getting it from the values cached in daemonrc. Put some debug echo commands in opcontrol's do_init and do_load_setup and run 'opcontrol --status' again. -Maynard > >> 3. Do 'ps awx | grep oprofiled' > 7877 pts/2 R+ 0:00 grep oprofiled > i.e. not running > >> From the above commands, what event(s) does opcontrol think you're specifying? If you see the daemonrc file still exists, then delete it and run the following commands: >> 1. 'opcontrol --deinit' > Daemon not running > Unloading oprofile module >> 2. 'modprobe oprofile timer=1' >> 3. 'opcontrol --vmlinux=/usr/src/linux-2.6.28.7/' > You cannot specify any performance counter events > because OProfile is in timer mode. > >> 4. 'opcontrol --start --verbose' > You cannot specify any performance counter events > because OProfile is in timer mode. > >> If this still doesn't work, post the output of each of the commands, as well as the output from the three commands I suggested above for gathering status information. >> >> -Maynard > > You see what ever option I give opcontrol it gives the same error > message, seems like a bug? > > even when I now type 'opcontrol --status': > You cannot specify any performance counter events > because OProfile is in timer mode. > >>>>> opcontroll --start, then I can't run any command, I always get a >>>>> failure message that I can't use events in timer mode. I can't even >>>>> --deinit! Any suggestions on how I can remove an event and run in >>>>> timer interrupt? >>>> If you succeed in forcing oprofile to use timer mode, you should see >>>> /dev/oprofile/cpu_type be 'timer'. If you haven't been able to deinit, then >>>> I don't see how you could have successfully set the module to timer mode >>>> yet. You say you "can't even --deinit". What's the error? >>>> >>>> -Maynard >>> I get the same error mentioned above. >>> >>> it is running in timer mode, I can see that from dmesg: >>> [70115.334630] oprofile: using timer interrupt. >>> >>> After I --start oprofile, the cpy_type is set to timer like you say. >>> >>> At this point I can't do anything! I can't even modprobe -r it will >>> just give me: >>> FATAL: Module oprofile is in use. >>> >>> The only thing I can do is resart the VMWare. >>> >>> So how do I remove events? >>> >>> Thank you. >>> >> > > > > -- > //Monthadar Al Jaberi > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list |
From: Monthadar Al J. <mon...@gm...> - 2009-03-24 08:11:43
|
after you where insisting on daemonrc, I did a complete search on my filesystem and found that there was one in /etc/oprofile. I deleted it and oprofile is working now. Is it soppused to create one there if the one in /root/.oprofile is deleted? Thank you for your help! On Mon, Mar 23, 2009 at 4:31 PM, Maynard Johnson <may...@us...> wrote: > Monthadar Al Jaberi wrote: >> On Thu, Mar 19, 2009 at 3:26 PM, Maynard Johnson <may...@us...> wrote: >>> Monthadar Al Jaberi wrote: >>>> On Wed, Mar 18, 2009 at 7:38 PM, Maynard Johnson <may...@us...> wrote: >>>>> Monthadar Al Jaberi wrote: >>>>>> Hi, I have a problem that I could not find a solution to. I am using >>>>>> oprofile in VMWare with Host:Win2000 Guest:Kubuntu 8.04. >>>>>> >>>>>> I didn't know that I can't use performance counters inside a virtual >>>>>> machine, and now I can't remove the event to use timer interrupts >>>>>> instead. I tried to delete the file in /root/.oprofile/daemonrc but it >>>>>> didn't help. If I just modprobe oprofile with timer=1 and then >>>>> How are you doing this? You should edit the opcontrol script where it does >>>>> the 'modprobe oprofile'. >>>> I modprobe it like: sudo modprobe oprofile timer=1 >>>> >>>> I don't know how to edit opcontrol, if I just put timer=1 in front of >>>> modeprobe oprilfe it will give the same error... >>>> >>>> What I do is: >>>> sudo modprobe oprofile timer=1 >>> Yes, it should be OK to do it this way. Disregard my previous comment about editing opcontrol >>>> sudo opcontrol --start >>> This would fail unless one of the following was true: >>> 1) you had just previously run 'opcontrol --no-vmlinux (or --vmlinux=<path-to-vmlinux file>)' >>> 2) you have an existing daemonrc file with VMLINUX=none (or <path-to-vmlinux file>) >> >> Indeed I have called opcontrol --vmlinux=<path> (after compiling a new >> kernel 2.6.28.7) >> >>>> then I get an error saying: >>>> You cannot specify any performance counter events >>>> because OProfile is in timer mode. >>> hmmm . . . the only way I can see you getting that error is if the daemonrc file still exists. Let's try a few different things to gather information about >> oprofile status: >> >> Ok, I restarted VMWare to get out of the problem, and am running your >> commands in a new fresh start. >> >>> 1. Do 'opcontrol --status' >> Daemon not running >> Event 0: CPU_CLK_UNHALTED:600000:0:1:1 >> Separate options: none >> vmlinux file: /usr/src/linux/vmlinux >> Image filter: none >> Call-graph depth: 20 >> >>> 2. Do 'cat /root/.oprofile/daemonrc' >> cat: /root/.oprofile/daemonrc: No such file or directory > I just don't see how you can get the above status information without getting it from the values cached in daemonrc. Put some debug echo commands in opcontrol's do_init and do_load_setup and run 'opcontrol --status' again. > > -Maynard >> >>> 3. Do 'ps awx | grep oprofiled' >> 7877 pts/2 R+ 0:00 grep oprofiled >> i.e. not running >> >>> From the above commands, what event(s) does opcontrol think you're specifying? If you see the daemonrc file still exists, then delete it and run the following commands: >>> 1. 'opcontrol --deinit' >> Daemon not running >> Unloading oprofile module >>> 2. 'modprobe oprofile timer=1' >>> 3. 'opcontrol --vmlinux=/usr/src/linux-2.6.28.7/' >> You cannot specify any performance counter events >> because OProfile is in timer mode. >> >>> 4. 'opcontrol --start --verbose' >> You cannot specify any performance counter events >> because OProfile is in timer mode. >> >>> If this still doesn't work, post the output of each of the commands, as well as the output from the three commands I suggested above for gathering status information. >>> >>> -Maynard >> >> You see what ever option I give opcontrol it gives the same error >> message, seems like a bug? >> >> even when I now type 'opcontrol --status': >> You cannot specify any performance counter events >> because OProfile is in timer mode. >> >>>>>> opcontroll --start, then I can't run any command, I always get a >>>>>> failure message that I can't use events in timer mode. I can't even >>>>>> --deinit! Any suggestions on how I can remove an event and run in >>>>>> timer interrupt? >>>>> If you succeed in forcing oprofile to use timer mode, you should see >>>>> /dev/oprofile/cpu_type be 'timer'. If you haven't been able to deinit, then >>>>> I don't see how you could have successfully set the module to timer mode >>>>> yet. You say you "can't even --deinit". What's the error? >>>>> >>>>> -Maynard >>>> I get the same error mentioned above. >>>> >>>> it is running in timer mode, I can see that from dmesg: >>>> [70115.334630] oprofile: using timer interrupt. >>>> >>>> After I --start oprofile, the cpy_type is set to timer like you say. >>>> >>>> At this point I can't do anything! I can't even modprobe -r it will >>>> just give me: >>>> FATAL: Module oprofile is in use. >>>> >>>> The only thing I can do is resart the VMWare. >>>> >>>> So how do I remove events? >>>> >>>> Thank you. >>>> >>> >> >> >> >> -- >> //Monthadar Al Jaberi >> >> ------------------------------------------------------------------------------ >> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are >> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and >> easily build your RIAs with Flex Builder, the Eclipse(TM)based development >> software that enables intelligent coding and step-through debugging. >> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >> _______________________________________________ >> oprofile-list mailing list >> opr...@li... >> https://lists.sourceforge.net/lists/listinfo/oprofile-list > > -- //Monthadar Al Jaberi |