update lttv to 0.12.15

[lttv.git] / trunk / lttv / doc / developer / lttng-lttv-compatibility.html

diff --git a/trunk/lttv/doc/developer/lttng-lttv-compatibility.html b/trunk/lttv/doc/developer/lttng-lttv-compatibility.html
index cac86183596c8109246de487742932f204d2d38e..106d218f2ca93abfa1ae2ddbfb3e42707b8d8438 100644 (file)
--- a/trunk/lttv/doc/developer/lttng-lttv-compatibility.html
+++ b/trunk/lttv/doc/developer/lttng-lttv-compatibility.html
@@ -3380,6 +3380,7 @@ powerpc64, s390, sparc, sparc64.<br>
 0.12.12<br>
 0.12.13<br>
 0.12.14<br>
+0.12.15<br>
 </td>
 <td style="vertical-align: top;">
 0.92<br>
@@ -3428,6 +3429,8 @@ powerpc64, s390, sparc, sparc64.<br>
 0.136<br>
 0.137<br>
 0.138<br>
+0.139<br>
+0.140<br>
 </td>
 <td style="vertical-align: top;">
 0.65<br>
@@ -3456,6 +3459,7 @@ obsolete<br>
 2.6.30-rc1<br>
 2.6.30-rc2<br>
 2.6.30-rc5<br>
+2.6.30<br>
 </td>
 <td style="vertical-align: top;">
 LTTng 0.92 reorders the LTTng patchset and drops the /proc/ltt interface.<br>
@@ -3501,6 +3505,13 @@ LTTV 0.12.14 fixes irq and softirq handling of resourceview for exit event at
 the beginning of the trace.<br>
 LTTng 0.137 moves trace_clock generic variable to trace_clock_var. Conflict with
 ftrace.<br>
+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.<br>
+LTTng 0.140 supports kernel 2.6.30.<br>
+LTTV 0.12.15 contains some fixes for the resource view.<br>
 </td>
 <td style="vertical-align: top;">
 </td>