X-Git-Url: http://git.lttng.org/?a=blobdiff_plain;f=README;h=1fd49b68dea49d650b394c064a4c43f73a5bbabe;hb=e54456f5bc70a46e11d23e1e3b2ae70bcda4c49f;hp=f4e3368cec50bad0d3f88465d565193617d6abf5;hpb=65a8ae6b080e172f6c4f47bfb8f51b42ff6aaaa7;p=lttng-modules.git

diff --git a/README b/README
index f4e3368c..1fd49b68 100644
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
 LTTng 2.0 modules
 
 Mathieu Desnoyers
-July 19, 2011
+February 8, 2012
 
 LTTng 2.0 kernel modules build against a vanilla or distribution kernel, without
 need for additional patches. Other features:
@@ -36,9 +36,6 @@ 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
 
-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 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
@@ -49,6 +46,10 @@ 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
+"Trace Syscalls" feature should be enabled too. 
+
 * Note about Perf PMU counters support
 
 Each PMU counter has its zero value set when it is attached to a context with