Date: Wed, 28 Mar 2012 00:27:56 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Ryan Stone <rstone@FreeBSD.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r233552 - in head/sys: cddl/dev/sdt kern sys Message-ID: <20120328002756.0000118e@unknown> In-Reply-To: <201203271507.q2RF7hO2091110@svn.freebsd.org> References: <201203271507.q2RF7hO2091110@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 Mar 2012 15:07:43 +0000 (UTC) Ryan Stone <rstone@FreeBSD.org> wrote: > Author: rstone > Date: Tue Mar 27 15:07:43 2012 > New Revision: 233552 > URL: http://svn.freebsd.org/changeset/base/233552 > > Log: > Instead of only iterating over the set of known SDT probes when > sdt.ko is loaded and unloaded, also have sdt.ko register callbacks > with kern_sdt.c that will be called when a newly loaded KLD module > adds more probes or a module with probes is unloaded. Great! Is this automatic, or do I need to do something in the newly loaded KLD? > This makes it possible to create SDT probes in KLD modules, > although there are still two caveats: first, any SDT probes in a KLD > module must be part of a DTrace provider that is defined in that > module. To make sure I understand it correctly: If I have the provider "linuxulator", all probes for this provider need to be within the KLD. No other KLD is allowed to reference this provider. To stay with the linuxulator example: if a module which depends upon linux.ko wants to have some SDT probes, it has to use a different provider. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120328002756.0000118e>