X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=README;h=583d0e024864d2e37fd22a86d847ec955539b1d7;hb=3da843ea85c6dd4aef5703fa24ca8bb29d172b57;hp=48ac65727aec9d6056ed2f4e4c38b75c8b1c7461;hpb=98541fcfb395ad8bc7f1dc347694b3ce5527c4c7;p=lttng-modules.git

diff --git a/README b/README
index 48ac6572..583d0e02 100644
--- a/README
+++ b/README
@@ -8,32 +8,41 @@ need for additional patches. Other features:
 
 - Produces CTF (Common Trace Format) natively,
   (http://www.efficios.com/ctf)
-- Function tracer, perf counters and kprobes support,
+- Tracepoints, Function tracer, CPU Performance Monitoring Unit (PMU)
+  counters and kprobes support,
 - Integrated interface for both kernel and userspace tracing,
 - Have the ability to attach "context" information to events in the
-  trace (e.g. any perf counter, pid, ppid, tid, comm name, etc). So
-  basically, all the perf "required fields" like "preempt count" and
-  "bkl count" are all optional, specified on a per-tracing-session basis
-  (except for timestamp and event id, which are mandatory).
+  trace (e.g. any PMU counter, pid, ppid, tid, comm name, etc).
+  All the extra information fields to be collected with events are
+  optional, specified on a per-tracing-session basis (except for
+  timestamp and event id, which are mandatory).
 
 To build and install, you will need to have your kernel headers available (or
 access to your full kernel source tree), and use:
 
-make
-make install
+% make
+# make modules_install
 
 If you need to specify the target directory to the kernel you want to build
 against, use:
 
-KERNELDIR=path_to_kernel_dir make
-KERNELDIR=path_to_kernel_dir make install
-
-Use lttng-tools to control the tracer. LTTng tools should automatically load the
-kernel modules when needed.
-
-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.
+% KERNELDIR=path_to_kernel_dir make
+# KERNELDIR=path_to_kernel_dir make modules_install
+
+Use lttng-tools to control the tracer. LTTng tools should automatically load
+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
+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.