Skip to contentSkip to conversation

trace: drop LTTng Userspace Tracer backend

PATCH In review Stefan Hajnoczi 4 participants 6 messages Sep 25, 2013 – Sep 30, 2013

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 trace: drop LTTng Userspace Tracer backend

The current LTTng Userspace Tracer backend does not build against modern libraries. LTTng has changed the library ABI several times, making it difficult to support this backend.

Due to lack of users, remove this trace backend until someone turns up who is willing to actively maintain it.

Details for anyone wishing to contribute an updated backend:

* Header files have been renamed from <ust/*> to <lttng/*>
* Tracepoint macros are no longer DECLARE_TRACE(name, TP_PROTO(args), TP_ARGS(argnames))
* Probably more breakage

---
 configure                        | 19 --------
 docs/tracing.txt                 | 11 +----
 scripts/tracetool/backend/ust.py | 93 ----------------------------------------
 3 files changed, 2 insertions(+), 121 deletions(-)
 delete mode 100644 scripts/tracetool/backend/ust.py
configure +0 -19
index 05e16da..95a8a4f 100755
@@ -3280,22 +3280,6 @@ if test "$?" -ne 0 ; then
 fi
 
 ##########################################
-# For 'ust' backend, test if ust headers are present
-if test "$trace_backend" = "ust"; then
-  cat > $TMPC << EOF
-#include <ust/tracepoint.h>
-#include <ust/marker.h>
-int main(void) { return 0; }
-EOF
-  if compile_prog "" "" ; then
-    LIBS="-lust -lurcu-bp $LIBS"
-    libs_qga="-lust -lurcu-bp $libs_qga"
-  else
-    error_exit "Trace backend 'ust' missing libust header files"
-  fi
-fi
-
-##########################################
 # For 'dtrace' backend, test if 'dtrace' command is present
 if test "$trace_backend" = "dtrace"; then
   if ! has 'dtrace' ; then
@@ -4191,9 +4175,6 @@ if test "$trace_backend" = "stderr"; then
   echo "CONFIG_TRACE_STDERR=y" >> $config_host_mak
   trace_default=no
 fi
-if test "$trace_backend" = "ust"; then
-  echo "CONFIG_TRACE_UST=y" >> $config_host_mak
-fi
 if test "$trace_backend" = "dtrace"; then
   echo "CONFIG_TRACE_DTRACE=y" >> $config_host_mak
   if test "$trace_backend_stap" = "yes" ; then
docs/tracing.txt +2 -9
index bfc261b..3d0d620 100644
@@ -135,9 +135,8 @@ the following monitor command:
 
 The "tracetool" script automates tedious trace event code generation and also
 keeps the trace event declarations independent of the trace backend.  The trace
-events are not tightly coupled to a specific trace backend, such as LTTng or
-SystemTap.  Support for trace backends can be added by extending the "tracetool"
-script.
+events are not tightly coupled to a specific trace backend, such as SystemTap.
+Support for trace backends can be added by extending the "tracetool" script.
 
 The trace backend is chosen at configure time and only one trace backend can
 be built into the binary:
@@ -208,12 +207,6 @@ You must ensure that the same "trace-events" file was used to build QEMU,
 otherwise trace event declarations may have changed and output will not be
 consistent.
 
-=== LTTng Userspace Tracer ===
-
-The "ust" backend uses the LTTng Userspace Tracer library.  There are no
-monitor commands built into QEMU, instead UST utilities should be used to list,
-enable/disable, and dump traces.
-
 === SystemTap ===
 
 The "dtrace" backend uses DTrace sdt probes but has only been tested with
scripts/tracetool/backend/ust.py deleted +0 -93

93 lines not on this page · raw message

Signature · 1 line
1.8.3.1
#1 lore raw

Hi Stefan,

I am actually using LTTng 2.x as a backend for UST to do some performance analysis and latency investigation using Qemu/KVM. I already have all the patches ready to replace the old 0.x interface, and I am preparing them for the merge upstream.

#2 lore raw
In reply to Stefan Hajnoczi

Hi Stefan,

I am actually using LTTng 2.x as a backend for UST to do some performance analysis and latency investigation using Qemu/KVM. I already have all the patches ready to replace the old 0.x interface, and I am preparing them for the merge upstream.

#3 lore raw
Quoted 4 lines · Mohamad Gebai

I am actually using LTTng 2.x as a backend for UST to do some performance analysis and latency investigation using Qemu/KVM. I already have all the patches ready to replace the old 0.x interface, and I am preparing them for the merge upstream.

Excellent, I was hoping to find someone who wants to update the code.

Do you need the old 0.x code for your patches or is it cleaner if we apply my patch to drop that first? I guess you pretty much rewrote the ./configure and tracetool pieces...

Stefan

#4 lore raw

Hi Stefan,
Sorry for the delay but I rewrote all the patches to make the merge as non-intrusive as possible, which wasn't the case in the patches I wrote for my personal use.
I submitted them in a different thread on the mailing list.

Mohamad

Quoted 12 lines · Stefan Hajnoczi
Quoted 4 lines · Mohamad Gebai

I am actually using LTTng 2.x as a backend for UST to do some performance analysis and latency investigation using Qemu/KVM. I already have all the patches ready to replace the old 0.x interface, and I am preparing them for the merge upstream.

Excellent, I was hoping to find someone who wants to update the code.

Do you need the old 0.x code for your patches or is it cleaner if we apply my patch to drop that first? I guess you pretty much rewrote the ./configure and tracetool pieces...

Stefan