You *can't* require an unchanging interface to changeable internals.
Posted Sep 21, 2006 7:34 UTC (Thu) by xoddam
Parent article: Tracing infrastructures
> Tracepoints clutter the code itself, and they must continue to
> work into the indefinite future. In a sense, each one can be
> thought of as a little system call which, once placed, cannot
> be changed.
That argument looks absurd to me. A tracing interface is intimately
tied to kernel internals. There is no way it should be considered
part of the "Don't break userspace" contract.
The 'marker' idea looks very sound to me. A config option at
compile time could choose static tracepoints, dynamic tracepoints
or no tracepoints at all. Maintaining a set of tracepoints 'out
of tree', when the tracepoints are plainly inside the kernel,
makes far *less* sense than eg. an out-of-tree device driver.
to post comments)