Messages in this thread | | | Subject | Re: [PATCH 0/18] Allow different tracers to be compiled independently | From | Steven Rostedt <> | Date | Tue, 23 Mar 2010 09:18:51 -0400 |
| |
On Tue, 2010-03-23 at 08:27 -0400, Mathieu Desnoyers wrote: > * Ingo Molnar (mingo@elte.hu) wrote: > >
> > We're in complete agreement here. When I considered if it was worth it to create > such a per-tracepoint group compile-time disabling in the first place, I decided > not to do it precisely due to the added-value that comes with the availability > of system-wide tracepoints. And I think with the static jump patching, we are > now at a point where the overhead is stunningly low. > > Now, space-wise, the one thing I would consider appropriate as a compromise for > small embedded systems would be to allow the TRACE_EVENT probes to be compiled > as modules.
Yeah, I agree here. Hmm, I wonder if we could automate this. That is, we could now, create a module per trace system if it is so configured. It would move the functions that create, record and output the trace points in TRACE_EVENT() into a separate module. Then you just need to load the modules you want to trace (grouped by system).
We can make add kobjects to /sys so that udev loads them automatically for distros.
-- Steve
| |