</td>
<td style="vertical-align: top;">
0.191<br>
+0.192<br>
+0.193<br>
+0.194<br>
+0.195<br>
+0.196<br>
+0.197<br>
+0.198<br>
+0.199<br>
+0.200<br>
+0.201<br>
</td>
<td style="vertical-align: top;">
0.76<br>
</td>
<td style="vertical-align: top;">
2.6.32.4<br>
+2.6.32.9<br>
+2.6.33<br>
+2.6.33.1<br>
</td>
<td style="vertical-align: top;">
LTTng 0.191, LTTV 0.12.30 coming with trace format 2.6 revert to the pre-2.4
behavior for alignment of 64-bit fields on 32-bit architectures. It aligns them
on 32-bit (maximum alignment is the architecture size). This follows gcc
behavior.<br>
+LTTng 0.192 fixes a crash with immediate values on x86 for kernel configured
+without modules. It was caused by a mainline commit which restricted the
+liveness of the "nop" table to init time in this configuration.<br>
+LTTng 0.193 modifies timers to support RT kernels again, and modifies omap3
+trace clock spinlock taken with irqs off, turning it into a raw spinlock
+(needed for RT kernel).<br>
+LTTng 0.194 uses mod_timer_pinned with add_timer_on to support NO_HZ SMP
+configs. Fixes incorrect API use introduced in 0.193.<br>
+LTTng 0.195 supports kernel 2.6.32.9.<br>
+LTTng 0.196 fixes a declaration omission in ARM omap3 trace clock, introduced in
+0.194.<br>
+LTTng 0.197 adds compiler barriers within nesting count. Eliminates possible
+false-negative caused by heavy compiler optimization. This only affects
+self-detection of internal LTTng problems (e.g. detecting trap recursion within
+the tracer), so it is not crucially important to update.<br>
+LTTng 0.198 fixes a periodic flush timer bug introduced in LTTng 0.194.<br>
+LTTng 0.199 supports Linux kernel 2.6.33.<br>
+LTTng 0.200 supports Linux kernel 2.6.33.1.<br>
+LTTng 0.201 fixes omap3 trace clock build: header moved from mach/ to plat/.<br>
</td>
<td style="vertical-align: top;">
</td>
projects / lttv.git / blobdiff