X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=doc%2Fdeveloper%2Flttng-lttv-compatibility.html;h=8f87b2d2c602c1eea361466957cece8e0208f58e;hb=49d782724593dede34cf7c4eebc01d2482aac62a;hp=76934f223612dea23c2205510ce38c4d8def0081;hpb=47e314707b8da465353c8e05732b461888a92127;p=lttv.git diff --git a/doc/developer/lttng-lttv-compatibility.html b/doc/developer/lttng-lttv-compatibility.html index 76934f22..8f87b2d2 100644 --- a/doc/developer/lttng-lttv-compatibility.html +++ b/doc/developer/lttng-lttv-compatibility.html @@ -3806,6 +3806,10 @@ powerpc64, s390, sparc, sparc64.
0.12.30
+0.12.31
+0.12.32
+0.12.33
+0.12.34
0.191
@@ -3821,6 +3825,24 @@ powerpc64, s390, sparc, sparc64.
0.201
0.202
0.203
+0.204
+0.205
+0.206
+0.207
+0.208
+0.209
+0.210
+0.211
+0.212
+0.213
+0.214
+0.215
+0.216
+0.217
+0.218
+0.219
+0.220
+0.221
0.76
@@ -3829,6 +3851,12 @@ powerpc64, s390, sparc, sparc64.
0.79
0.80
0.81
+0.82
+0.83
+0.84
+0.85
+0.86
+0.87
obsolete
@@ -3848,6 +3876,9 @@ obsolete
2.6.33
2.6.33.1
2.6.33.2
+2.6.33.3
+2.6.33.4
+2.6.34
LTTng 0.191, LTTV 0.12.30 coming with trace format 2.6 revert to the pre-2.4 @@ -3883,6 +3914,56 @@ ltt-control 0.81 divides the lttd daemon in a LGPLv2.1 library and GPLv2 program parts. It makes it possible to spawn a daemon instance from a program without requiring to fork a new process.
LTTng 0.204 supports kernel 2.6.33.2
+LTTng 0.205 fixes a kref race in channel teardown vs lttd file open.
+ltt-control 0.82 ensures lttctl waits for lttd to complete when called at trace +destruction in overwrite mode. Failure to do so can result in unread channels in +flight recorder mode.
+LTTng 0.206 marks Immediate Values as BROKEN for PowerPC. Will be replaced by +asm goto from mainline eventually anyway, so don't bother looking for the cause +of the bug.
+LTTng 0.207 fixes trivial error from 0.206.
+LTTng 0.208 uses msleep() rather than cpu_relax() for better !PREEMPT UP support +for the kref teardown.
+ltt-control 0.83 does a temporary fix to ensure lttd grabs file handles at the +end of overwrite mode tracing.
+LTTV 0.12.31 fixes the statedump end state handler to correctly deal with +threads scheduled out from userspace (waiting for CPU) when the statedump end +event happen.
+ltt-control 0.84 fixes /debugfs auto-find in ltt-armall and ltt-disarmall +scripts.
+LTTng 0.209 fixes a module build issue.
+LTTng 0.210 reverts some powerpc-specific instrumentation from mainline that +clashes with arch-agnostic LTTng instrumentation.
+LTTng 0.211 fixes build menu Kconfig dependencies.
+LTTng 0.212 adds more complete MIPS syscall instrumentation.
+LTTng 0.213 supports kernel 2.6.33.3, moves call_64.h to the correct header +location and fixes -rt kernel teardown locking issue.
+LTTng 0.214 support kernel 2.6.33.4.
+LTTng 0.215 fixes module circular dependendy.
+ltt-control 0.85 contains an update lttd which uses fadvise and sync_file_range +to ensure that the page cache is not filled by trace buffers.
+ltt-control 0.86 puts fadvise after sync writeback to use sync writeback rather +than dirty page writeback. (should improve streaming)
+LTTng 0.216 fixes a trace-clock-32-to-64 teardown bug recently introcuced. Only +affects ARM and MIPS SMP systems.
+LTTV 0.12.32 includes various cleanups and fixes.
+ltt-control 0.87 fixes argument parsing for periodical buffer switch option.
+LTTng 0.217 supports kernel 2.6.34.
+LTTng 0.218 fixes a missing irq_desc export in kernel/irq/handle.c, affects +sparse irq configurations.
+LTTV 0.12.33 fixes statistics handling. Use per-cpu rather than per-tracefile +event tree head. This bug was introduced when LTTng started supporting multiple +channels.
+LTTng 0.219 fixes an out-of-bound array use in marker.c.
+LTTng 0.220 forces alignment on 128 bytes (larger than structure) to ensure that +the section alignment in the linker script matches that of overly enthusiastic +compilers.
+LTTV 0.12.34 fixes a bug in string handling in libltttraceread. Caused incorrect +string length calculation when a string appeared in many per-cpu tracefiles of +the same channel.
+LTTng 0.221 now supports writing strings into the buffer when string input is +being modified concurrently. Such a race should not render the trace +unreadable.