X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=trunk%2Flttv%2Fdoc%2Fdeveloper%2Flttng-lttv-compatibility.html;h=106d218f2ca93abfa1ae2ddbfb3e42707b8d8438;hb=838c5eb0afbb49a76587d7fc34c1141d073048d8;hp=e606f860a6d90091376fb350bc5653039fe0d728;hpb=076b3ebc7b1115a9752c81dfd7f9f6f3988c7e7f;p=lttv.git diff --git a/trunk/lttv/doc/developer/lttng-lttv-compatibility.html b/trunk/lttv/doc/developer/lttng-lttv-compatibility.html index e606f860..106d218f 100644 --- a/trunk/lttv/doc/developer/lttng-lttv-compatibility.html +++ b/trunk/lttv/doc/developer/lttng-lttv-compatibility.html @@ -3378,6 +3378,9 @@ powerpc64, s390, sparc, sparc64.
0.12.10
0.12.11
0.12.12
+0.12.13
+0.12.14
+0.12.15
0.92
@@ -3418,6 +3421,16 @@ powerpc64, s390, sparc, sparc64.
0.128
0.129
0.130
+0.131
+0.132
+0.133
+0.134
+0.135
+0.136
+0.137
+0.138
+0.139
+0.140
0.65
@@ -3445,6 +3458,8 @@ obsolete
2.6.29.1
2.6.30-rc1
2.6.30-rc2
+2.6.30-rc5
+2.6.30
LTTng 0.92 reorders the LTTng patchset and drops the /proc/ltt interface.
@@ -3479,6 +3494,24 @@ LTTng 0.126 supports kernel 2.6.30-rc2.
LTTng 0.129 finally gets merge with event tracer right.
LTTng 0.130 fixes issues when building LTTng as modules (in ltt kprobes support, Kconfig for ltt-relay-*.c and exporting vmalloc_sync_all symbol appropriately).
+LTTng 0.133 fixes a irq handler instrumentation regression introduced in the +2.6.30-rc LTTng versions.
+LTTng 0.134 includes ARM OMAP3 trace clock fixes, idle support, PM tracepoints +and LTTng async timer running as deferrable timer to save power.
+LTTng 0.135 support kernel 2.6.30-rc5.
+LTTV 0.12.13 fixes a bug in resourceview trap exit handling when occurs before +any trap entry at the beginning of the trace.
+LTTV 0.12.14 fixes irq and softirq handling of resourceview for exit event at +the beginning of the trace.
+LTTng 0.137 moves trace_clock generic variable to trace_clock_var. Conflict with +ftrace.
+LTTng 0.139 modifies the memory barrier IPIs (at sub-subber switch) to give them +a good deal of paranoia : don't trust the Linux IPI mechanism to ensure that +memory is presented in program order when the remote ipi handler runs. Use our +own smp_mb()s to ensure memory ordering. It's a slow path anyway, we don't +care.
+LTTng 0.140 supports kernel 2.6.30.
+LTTV 0.12.15 contains some fixes for the resource view.