Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Jun 2012 17:49:38 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Dag-Erling Sm??rgrav <des@des.no>
Cc:        arch@freebsd.org
Subject:   Re: KTR_SPAREx
Message-ID:  <20120605144938.GN85127@deviant.kiev.zoral.com.ua>
In-Reply-To: <86pq9dvn33.fsf@ds4.des.no>
References:  <86bokyvtc2.fsf@ds4.des.no> <20120605143215.GL85127@deviant.kiev.zoral.com.ua> <86pq9dvn33.fsf@ds4.des.no>

next in thread | previous in thread | raw e-mail | index | archive | help

--CQDko/0aYvuiEzgn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 05, 2012 at 04:40:32PM +0200, Dag-Erling Sm??rgrav wrote:
> 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, a=
side
> > of making noise that cayses log to be meaningless.
>=20
> 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.

>=20
> 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 ?

>=20
> (I still haven't gotten around to implementing a similar infrastructure
> for network interfaces...)
>=20
> DES
> --=20
> Dag-Erling Sm??rgrav - des@des.no

--CQDko/0aYvuiEzgn
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (FreeBSD)

iEYEARECAAYFAk/OHIEACgkQC3+MBN1Mb4ipIwCeNnkTQuffMM3uGSnbZt2zY5pU
rl0AoMUPQEGfFH93xKOOz/jGwcHZ5BIQ
=gP0D
-----END PGP SIGNATURE-----

--CQDko/0aYvuiEzgn--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120605144938.GN85127>