On Saturday 27 May 2006 05:20, John Birrell wrote: > I've added a KDTRACE kernel option which compiles in the hooks that > DTrace uses and a bit of extra exception handling code. This > is only minimal bloat. > > Apart from those hooks, the DTrace kernel functionality is in the > 'dtrace' device which is also the 'dtrace' provider. The other > providers register themselves with the 'dtrace' device. > > If the DTrace device modules aren't loaded, there is very little > code in the kernel to share. Factoring out the common code into a separate module that dtrace/ktrace/etc can depend would be a good approach IMO. Although having just a single source copy but compiling it N times would be better (modulo licensing concerns - perhaps the hwpmc version could be used?) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:56 UTC