X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=doc%2Fdeveloper%2Flttng-lttv-compatibility.html;h=4677f6c4253d61ace87b1e7427994bb1811af222;hb=b72282a64f7788287332b6a95cf3ce0f7dd96d8a;hp=8f87b2d2c602c1eea361466957cece8e0208f58e;hpb=49d782724593dede34cf7c4eebc01d2482aac62a;p=lttv.git diff --git a/doc/developer/lttng-lttv-compatibility.html b/doc/developer/lttng-lttv-compatibility.html index 8f87b2d2..4677f6c4 100644 --- a/doc/developer/lttng-lttv-compatibility.html +++ b/doc/developer/lttng-lttv-compatibility.html @@ -3810,6 +3810,7 @@ powerpc64, s390, sparc, sparc64.
0.12.32
0.12.33
0.12.34
+0.12.35
0.191
@@ -3843,6 +3844,8 @@ powerpc64, s390, sparc, sparc64.
0.219
0.220
0.221
+0.222
+0.223
0.76
@@ -3879,6 +3882,8 @@ obsolete
2.6.33.3
2.6.33.4
2.6.34
+2.6.34.4
+2.6.35.2
LTTng 0.191, LTTV 0.12.30 coming with trace format 2.6 revert to the pre-2.4 @@ -3964,6 +3969,13 @@ 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.
+LTTng 0.222 supports kernel 2.6.34.4. It includes a lttng splice actor +adjustment to match a splice.c change in 2.6.34.2 which changed the checks for +seekable files.
+LTTV 0.12.35 fixes a problem introduced in 0.12.34, fixing the problem initially +fixed by 0.12.34 in the "correct" way; without unwanted side-effects. LTTV +0.12.34 had problems calling hooks for some events.
+LTTng 0.223 supports kernel 2.6.35.2.