K 10
svn:author
V 6
rstone
K 8
svn:date
V 27
2012-05-27T14:48:14.156015Z
K 7
svn:log
V 1198
MFC r233552

 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.

 This fixes two issues: first, if a module with SDT probes was loaded after
 sdt.ko was loaded, those new probes would not be available in DTrace.
 Second, if a module with SDT probes was unloaded while sdt.ko was loaded,
 the kernel would panic the next time DTrace had cause to try and do
 anything with the no-longer-existent probes.

 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.  At present DTrace
 only destroys probes when the provider is destroyed, so you can still
 panic the system if a KLD module creates new probes in a provider from a
 different module(including the kernel) and then unload the the first module.

 Second, the system will panic if you unload a module containing SDT probes
 while there is an active D script that has enabled those probes.

END