Date: Tue, 05 Jun 2012 16:40:32 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Konstantin Belousov <kostikbel@gmail.com> Cc: arch@freebsd.org Subject: Re: KTR_SPAREx Message-ID: <86pq9dvn33.fsf@ds4.des.no> In-Reply-To: <20120605143215.GL85127@deviant.kiev.zoral.com.ua> (Konstantin Belousov's message of "Tue, 5 Jun 2012 17:32:15 %2B0300") References: <86bokyvtc2.fsf@ds4.des.no> <20120605143215.GL85127@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Konstantin Belousov <kostikbel@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, asi= de > 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. 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. (I still haven't gotten around to implementing a similar infrastructure for network interfaces...) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86pq9dvn33.fsf>