Version 2.5.6

[lttng-modules.git] / README

diff --git a/README b/README
index 1bcd5b2d69bd9109bdb38236063470294b3f3d7d..70d991f4d907024fa7d9390e60de25e566ba9aa9 100644 (file)
--- a/README
+++ b/README
@@ -1,9 +1,9 @@
-LTTng 2.0 modules
+LTTng 2.x modules
 
 Mathieu Desnoyers
-April 6, 2012
+March 29, 2013
 
-LTTng 2.0 kernel modules build against a vanilla or distribution kernel, without
+LTTng 2.x kernel modules build against a vanilla or distribution kernel, without
 need for additional patches. Other features:
 
 - Produces CTF (Common Trace Format) natively,
@@ -36,18 +36,7 @@ the kernel modules when needed. Use Babeltrace to print traces as a
 human-readable text log. These tools are available at the following URL:
 http://lttng.org/lttng2.0
 
-So far, it has been tested on vanilla Linux kernels 2.6.38, 2.6.39, 3.0,
-3.1, 3.2, 3.3 (on x86 32/64-bit, and powerpc 32-bit at the moment, build
-tested on ARM). Kernels 2.6.32 to 2.6.34 need up to 3 patches applied
-(refer to linux-patches within the lttng-modules tree). It should work
-fine with newer kernels and other architectures, but expect build issues
-with kernels older than 2.6.36.  The clock source currently used is the
-standard gettimeofday (slower, less scalable and less precise than the
-LTTng 0.x clocks).  Support for LTTng 0.x clocks will be added back soon
-into LTTng 2.0.  Please note that lttng-modules 2.0 can build on a Linux
-kernel patched with the LTTng 0.x patchset, but the lttng-modules 2.0
-replace the lttng-modules 0.x, so both tracers cannot be installed at
-the same time for a given kernel version.
+Linux kernels >= 2.6.36 are supported.
 
 
 * Kernel config options required
@@ -86,6 +75,8 @@ CONFIG_KPROBES:
 CONFIG_KRETPROBES:
             Dynamic function entry/return probe.
                lttng enable-event -k --function ...
+CONFIG_KALLSYMS_ALL:
+            State dump of mapping between block device number and name.
 
 
 * Note about Perf PMU counters support