OProfile

I revised the patch to apply to the 2.5.69 kernel and added support so 
there is a boot line option "oprofile_timer" that will force oprofile to 
use the timer regardless of performance monitoring hardware. The 
"oprofile_timer=1" can still be used at module load to force use of the 
timer interrupt mechanism.

-Will

John Levon wrote:
> On Thu, Apr 10, 2003 at 02:05:01PM -0400, Will Cohen wrote:
> 
> 
>>I have a small patch to the 2.5 oprofile driver which provides a 
>>oprofile_force_timer flag, that allows insmod to force the use of the 
> 
> 
> Can you redo the patch, and also test that it works with
> CONFIG_OPROFILE=y (i.e. boot-time flag). I vaguely remember that the
> flag is prefixed with the module name in fact. If this is true, then it
> can just be called "force_timer", as it's now local to oprof.c
> 
> thanks
> john
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> oprofile-list mailing list
> oprofile-list@...
> https://lists.sourceforge.net/lists/listinfo/oprofile-list
>

On Tue, May 06, 2003 at 04:45:27PM -0400, William Cohen wrote:

> I revised the patch to apply to the 2.5.69 kernel and added support so 
> there is a boot line option "oprofile_timer" that will force oprofile to 
> use the timer regardless of performance monitoring hardware. The 
> "oprofile_timer=1" can still be used at module load to force use of the 
> timer interrupt mechanism.

This is wrong, __setup() is  obsolete, see the comment around __setup()
definition.

You should be using module_param() API. Note in particular,
MODULE_PARAM_PREFIX in moduleparam.h. So it can simply be called "timer"
or maybe "force_timer"

Sorry I wasn't clearer about this.

regards,
john