X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=trunk%2Flttv%2Fdoc%2Fdeveloper%2Fust.html;h=c1cbeb2ed88450aa71394b21c6713b7d4eb29bc7;hb=0c71c32a2f82cd194799975350bf5fa935b13655;hp=3fb0c444ec025ded44abce5f974a2eb388081f66;hpb=ca3fb06a495dcfc02b284274d59bdef1d47e53e7;p=lttv.git diff --git a/trunk/lttv/doc/developer/ust.html b/trunk/lttv/doc/developer/ust.html index 3fb0c444..c1cbeb2e 100644 --- a/trunk/lttv/doc/developer/ust.html +++ b/trunk/lttv/doc/developer/ust.html @@ -46,9 +46,20 @@ crashing). Such notification may be obtained through utrace. This tracing scheme plans to use a direct function call to tracing into buffers mapped in user-space. This should be an order of magnitude faster than the current Dtrace implementation (c.f. -https://ltt.polymtl.ca/tracingwiki/index.php/DTrace) which uses a breakpoint to +Dtrace information +on the TracingWiki) which uses a breakpoint to perform both dynamic and static user-space tracing. Performance comparison of a function call vs the int3 approach is available at -http://sourceware.org/ml/systemtap/2006-q3/msg00793.html (see "Conclusion"). +Markers vs +int3 performance comparison (see "Conclusion"). + +Tracing of Java application is planned to be done through a JNI interface. +Linking standard low-level C tracing library to the application within a JNI +adaptation class will be required to trace Java events. This has been prototyped +in the past. The work is available +here +for older LTTng versions. +