On Tue, Sep 21, 2004 at 09:59:01PM +0300, Eran Tromer wrote: > On 09/21/2004 09:54 PM, Muli Ben-Yehuda wrote: > > Understandable... > > The oprofile-sepcific part can be compiled as a module, and anyway it is > de/activated at runtime. Is the overhead of the remaining stub > significant?
To the best of my recollection, CONFIG_PROFILE turns on some other non-oprofile profiling support that has non-negligible run-time impact. Maybe oprofile's dependancy on CONFIG_PROFILE should be removed, or things arranged os that oprofile is enabled/disabled at run time without any overhead. Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/
signature.asc
Description: Digital signature
