From c4a5a3f622e2c1bf0e18388b81097db9cb7c4ea1 Mon Sep 17 00:00:00 2001 From: compudj Date: Fri, 10 Oct 2008 23:08:12 +0000 Subject: [PATCH] update compat/ git-svn-id: http://ltt.polymtl.ca/svn@3093 04897980-b3bd-0310-b5e0-8ef037075253 --- .../developer/lttng-lttv-compatibility.html | 54 +++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/trunk/lttv/doc/developer/lttng-lttv-compatibility.html b/trunk/lttv/doc/developer/lttng-lttv-compatibility.html index bf5c36fa..f9c3dd6b 100644 --- a/trunk/lttv/doc/developer/lttng-lttv-compatibility.html +++ b/trunk/lttv/doc/developer/lttng-lttv-compatibility.html @@ -2970,6 +2970,60 @@ powerpc64, s390, sparc, sparc64.
+ + +0.11.0
+ + +0.37
+ + +0.53
+ + +obsolete
+ + +0.6
+ + +obsolete
+ + +2.0
+ + +2.6.27
+ + +LTTng 0.37 and LTTV 0.11.0 +I just cleaned up the LTTng trace format heavily, got rid of the +heartbeat timer (by checking for overflow at the tracing site), got rid +of the "special" compact channel; it removed about 5 FIXMEs in LTTng +(cpu hotplug and compact channel related). Everything is compact now :
+
+This is much more compact than the previous format, and permits a +"tracer debug mode" in menuconfig which enables the "event size" field, +which helps cross-checking the size expected by the userspace tool and +the size written by the kernel.
+
+Note that this "event size" field can eventually be enabled on a +per-event or per-channel basis. This will probably be useful to encode +"binary blobs"...
+
+The trace major number is bumped to "2" and is completely incompatible +with old LTTV.
+ + + + +x86, alpha, arm26, avr32, cris, frv, h8300, m32r, m68knommu, parisc, sh, sh64, +um, v850, xtensa.
+arm, i686, ia64, m68k, mips, mipsel, x86_64, powerpc 405, +powerpc64, s390, sparc, sparc64.
+ + + -- 2.34.1