KTR_SPAREx

[Konstantin Belousov]

On Tue, Jun 05, 2012 at 04:40:32PM +0200, Dag-Erling Sm??rgrav wrote:
> Konstantin Belousov <kostikbel at gmail.com> writes:
> > Moving all device drivers to KTR_DEV makes the KTR unusable for device
> > driver debugging. When looking at the drm2 and gem traces, I do not want
> > to see other devices tracepoints. Amount of data from GEM is huge, and
> > obfuscating it with unrelated debugging recycles the ktr ring faster, aside
> > of making noise that cayses log to be meaningless.
> 
> We only have a limited number of KTR types - 32, to be precise.  We
> can't spare one for each driver, and there's no reason why *your* driver
> (for any value of "you") should get its own while everybody else shares
> KTR_DEV.
I want to have only *my* driver trace points in the ring, by whatever
means. Breaking it right now would mean that I cannot do any GEM
debugging.

> 
> If you think KTR_DEV is too noisy, add sysctls to enable or disable
> tracing on a per-device basis.  It should be quite easy to generalize.
So you are planning to break some useful, but possibly randomly-achieved
functionality, and delegate the work to repair it to somebody else ?

> 
> (I still haven't gotten around to implementing a similar infrastructure
> for network interfaces...)
> 
> DES
> -- 
> Dag-Erling Sm??rgrav - des at des.no
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20120605/f086f0a3/attachment.pgp