X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=README;h=97c96f6305336366c39f064d150af101bbd8cae8;hb=14a8117ffda897ab50e9cbe5d3c1e1d34fcb9f2d;hp=e6a0d4a043d85611117b90440af27e757137c29b;hpb=6b40862968f9211983918d0e99cbe3656a0dd600;p=lttng-modules.git

diff --git a/README b/README
index e6a0d4a0..97c96f63 100644
--- a/README
+++ b/README
@@ -37,9 +37,12 @@ http://lttng.org/lttng2.0
 Please note that the LTTng-UST 2.0 (user-space tracing counterpart of LTTng 2.0)
 is still in active development and not released yet.
 
-So far, it has been tested on vanilla kernels 2.6.38 and 2.6.39 (on x86 at the
-moment). 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.
+So far, it has been tested on vanilla Linux kernels 2.6.38, 2.6.39 and 3.0-rc7
+(on x86 at the moment). 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.