Re: oprofile 2.5.42 patch not running on athlon machine

[William C. <wc...@nc...>]

Is the goal is that the daemon is persistent and doesn't have to be 
killed and restarted every time there is a change in a performance 
monitoring parameter?

-Will


John Levon wrote:
> On Tue, Oct 15, 2002 at 05:13:17PM -0400, William Cohen wrote:
> 
> 
>>versions.  I still haven't been successful in getting any data on the 
>>athlon machine. I am thinking about the difference between my PIII and 
> 
> 
> Ugh, I forgot about this.
> 
> 
>>The data collection does not work on my athlon machine. There is an 
>>oprofiled in the process table, but it doesn't appear that any samples 
>>are being taken. Suggestions on things I should look for?
> 
> 
> o check syslog has "Using NMI interrupt"
> o check /dev/oprofile/stats
> o printk/printfs
> 
> 
>>The op_start_25 script it doesn't kill the old process. Have to kill 
>>things by hand. John, why was that stripped out?
> 
> 
> User request - we should split up "starting the daemon" from "starting
> profiling". I'm thinking of an op_ctrl :
> 
> op_ctrl --setup --vmlinux=...
> 
> 	- starts/restarts the daemon
> 
> op_ctrl --start
> 
> 	- echo 1 >/dev/oprofile/enable
> 
> op_ctrl --stop
> 
> 	- echo 0 >/dev/oprofile/enable
> 
> op_ctrl --reset/--save
> 
> 	- rm -rf /var/lib/oprofile/samples; kill -HUP `cat
> 	  /var/lib/oprofile/lock`
> 
> op_ctrl --shutdown
> 
> 	kill -HUP `cat /var/lib/oprofile/lock`
> 
> op_ctrl --dump
> 
> 	See below
> 
> 
>>oprof_start is going to need to be massaged for 2.5 oprofile because it 
>>expects to get the cpu_type information and that isn't available until 
>>the "mount /dev/oprofile" occurs in op_start_25.
> 
> 
> Yes it needs fixing
> 
> 
>>How does one force a dump of the profiling data in the 2.5 system? The 
>>files that op_dump touches are no longer around?
> 
> 
> I'm not sure how we shuold do this yet. A simple echo 0 then echo 1
> won't work unless we can be sure the daemon has gone back to sleep
> before the "echo 1"
> 
> I'd like a way that's less fugly than what happens in 2.4
> 
> regards
> john