X-Git-Url: http://git.lttng.org/?a=blobdiff_plain;f=README;h=abbfd27746926f6a1426e81ee96b1c4c9e53a4e3;hb=d117fe45a02e9bbeae37fd66c237b2779367defc;hp=1fd49b68dea49d650b394c064a4c43f73a5bbabe;hpb=1bca821c350a3a77ced6af4ce45eb584ffae3d96;p=lttng-modules.git

diff --git a/README b/README
index 1fd49b68..abbfd277 100644
--- a/README
+++ b/README
@@ -36,15 +36,17 @@ 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 and 3.0 (on
-x86 32/64-bit, and powerpc 32-bit at the moment, build tested on ARM). 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.
+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). 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.
 
 LTTng-modules depends on having kallsyms enabled in the kernel it is
 built against. Ideally, if you want to have system call tracing, the