update compat

git-svn-id: http://ltt.polymtl.ca/svn@2550 04897980-b3bd-0310-b5e0-8ef037075253

diff --git a/ltt/branches/poly/doc/developer/lttng-lttv-compatibility.html b/ltt/branches/poly/doc/developer/lttng-lttv-compatibility.html
index 56d01d758a973d056cbd522d6fc85a4aecafbe79..0069681c3954714e216c80e24ebf715936bf47c3 100644 (file)
--- a/ltt/branches/poly/doc/developer/lttng-lttv-compatibility.html
+++ b/ltt/branches/poly/doc/developer/lttng-lttv-compatibility.html
@@ -2381,10 +2381,46 @@ v850, xtensa.<br>
 arm, i686, ia64, m68k, mips, mipsel, x86_64, powerpc 405, powerpc64, s390,
 sparc, sparc64.<br>
 </td>
-
 </tr>
 
-
+<tr>
+<td style="vertical-align: top;">
+0.8.83<br>
+</td>
+<td style="vertical-align: top;">
+0.9.10<br>
+</td>
+<td style="vertical-align: top;">
+0.41<br>
+</td>
+<td style="vertical-align: top;">
+obsolete<br>
+</td>
+<td style="vertical-align: top;">
+Not available (syscall IDs not updated)<br>
+</td>
+<td style="vertical-align: top;">
+obsolete<br>
+</td>
+<td style="vertical-align: top;">
+0.8<br>
+</td>
+<td style="vertical-align: top;">
+2.6.22.1-rt4<br>
+</td>
+<td style="vertical-align: top;">
+LTTng 0.9.10 port to 2.6.22.1-rt4.<br>
+</td>
+<td style="vertical-align: top;">
+Tested on x86_32.
+</td>
+<td style="vertical-align: top;">
+alpha, arm26, avr32, cris, frv, h8300, m32r, m68knommu, parisc, sh, sh64, um,
+v850, xtensa.<br>
+arm, i686, ia64, m68k, mips, mipsel, x86_64, powerpc 405, powerpc64, s390,
+sparc, sparc64.<br>
+</td>
+</tr>
 
 </tbody>
 </table>

diff --git a/ltt/branches/poly/doc/developer/lttng-new-marker-event-desc.txt b/ltt/branches/poly/doc/developer/lttng-new-marker-event-desc.txt
index 221c286a2f4479f673a6e35e6e14e19ff04058f9..a22b40f2bd7726eccd47c95ebbb5c007d7f1ed40 100644 (file)
--- a/ltt/branches/poly/doc/developer/lttng-new-marker-event-desc.txt
+++ b/ltt/branches/poly/doc/developer/lttng-new-marker-event-desc.txt
@@ -91,12 +91,29 @@ update probes (temp)
 /proc/markers: enable/disable name [channel]
 
 probe_data should provide, for ltt:
-channel_index
 callbacks
 id <-- will stay in marker because otherwise we would need another hash table.
-
+channel index : put inside the marker structure (parameter to register).
+A marker control module
 
 Q: field names in dictionnary or in marker ?
 
 
+What users will do with marker interface:
+
+from userspace:
+enable/disable marker_name (act on any marker, reg by module or other)
+channel marker_name channel_name (act on any marker)
+
+Default: use serializer
+But.. module can override _default_ probe with a "register" operation.
+
+Use case
+Set channel
+Register by specific module (unregister default, register specific)
+activate.
+
+Serve as a proxy for probe registration.
+
+