From owner-freebsd-current@FreeBSD.ORG Sun Apr 14 15:18:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DB9524B1 for ; Sun, 14 Apr 2013 15:18:41 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by mx1.freebsd.org (Postfix) with ESMTP id AF823281 for ; Sun, 14 Apr 2013 15:18:41 +0000 (UTC) Received: from pool-141-154-241-44.bos.east.verizon.net ([141.154.241.44] helo=homobox.opal.com) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1UROhP-000LdF-G7; Sun, 14 Apr 2013 15:18:35 +0000 Received: from shibato (shibato.opal.com [IPv6:2001:470:8cb8:4:221:63ff:fe5a:c9a7]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id r3EFIVea055092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 14 Apr 2013 11:18:32 -0400 (EDT) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 141.154.241.44 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/Oodk0tgdJLrM55p69c7// Date: Sun, 14 Apr 2013 11:18:23 -0400 From: "J.R. Oldroyd" To: Alexander Leidinger Subject: Re: DTrace of radeonkms on 9.1 Message-ID: <20130414111823.19e30e63@shibato> In-Reply-To: <20130401143652.00001870@unknown> References: <20130327180714.5beae7d6@shibato> <20130401143652.00001870@unknown> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/cfxMsEF0P/4pgVqjEC0kB6K"; protocol="application/pgp-signature" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (homobox.opal.com [IPv6:2001:470:8cb8:4::1]); Sun, 14 Apr 2013 11:18:32 -0400 (EDT) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on homobox.opal.com Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Apr 2013 15:18:41 -0000 --Sig_/cfxMsEF0P/4pgVqjEC0kB6K Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 1 Apr 2013 14:36:52 +0200 Alexander Leidinger wrote: > > On Wed, 27 Mar 2013 18:07:14 -0400 > "J.R. Oldroyd" wrote: >=20 > > Is there any known magic involved in getting DTrace to do its thing on > > 9.1-release? > >=20 > > I am trying to use it to debug a memory leak problem with the > > radeonkms driver under 9.x. >=20 > Can you check if you have the same dtrace-problem with -current? I > would expect that 9.1 already has some dtrace-fixes regarding new > probes in run-time loaded modules, this is just to verify this > assumption. >=20 > Assuming there is some kind of dead-lock in this module-load interaction > with dtrace, you could modify the radeonkms module to do it's > initialization magic once a sysctl is set to 1, instead of doing this > magic at module-load time. This way you could load the module, start > the dtrace script and then issue the magic sysctl. >=20 > Bye, > Alexander. >=20 Thanks for the suggestion. The problem I was hoping to use DTrace to debug turned out to be an incompletely back-ported vm_alloc_page_contig() function. This was discovered using careful code analysis. Having improved the back-port of this function, the radeonkms driver is now running fine on 9.1-release. The need for DTtrace has therefore gone away for the time being. That said, the back-port of the VM function is not 100%, yet. I've had to put this on hold due to other commitments, but when I get back to this, I probably need to talk to our VM experts to get a list of commits that will be needed to properly merge that function into 9-stable. -jr --Sig_/cfxMsEF0P/4pgVqjEC0kB6K Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFqyMcACgkQls33urr0k4lWgQCeJYAVlvXKHB32kaj02hIg/gKE HRgAnj0uLakPdTIq8oqcb7e9/lbK46QI =U+9J -----END PGP SIGNATURE----- --Sig_/cfxMsEF0P/4pgVqjEC0kB6K--