dtrace discuss - Jan 2006 - Limiting classes that are instrumented by DVM DVMPI provider

I would like to be able to limit what classes get instrumented with the DVMPI
provider.  From the C code (which I am not 100% I understand) I don''t
see a reference to the ''interested'' function call that?s in
the DVMTI provider, so it appears to matching all classes.

I know I can do it with predicates in the .d script, but by then I believe It?s
a bit too late, as far as overheads are concerned.

Any assistance appreciated
This message posted from opensolaris.org

Hi Jason,

The dvm provider does indeed cause every class to be instrumented. While
we''d
like to address this at some point, the more pressing problem we''re
looking
at in that domain is being able to dynamically insert the instrumentation
into a running JVM. After we get that working, we''ll look at limiting
instrumentation to particular mehtods and classes.

Adam

On Thu, Jan 19, 2006 at 08:18:21PM -0800, Jason Pell
wrote:
> I would like to be able to limit what classes get instrumented with the
DVMPI provider.  From the C code (which I am not 100% I understand) I
don''t see a reference to the ''interested'' function
call that?s in the DVMTI provider, so it appears to matching all classes.
> 
> I know I can do it with predicates in the .d script, but by then I believe
It?s a bit too late, as far as overheads are concerned.
> 
> Any assistance appreciated
> This message posted from opensolaris.org
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
-- 
Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl