X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=trunk%2Flttv%2FQUICKSTART.html;h=31c6bbae40e2c320d64f7633e12eb931e08b2ce6;hb=0e12ccd4b1063e26bc14dbde81920ae41dd868a3;hp=59bc934cd24b084be7256cab7f7a25f221be405a;hpb=83cebd384aaf56f8b040faf9e90ad74909819a7f;p=lttv.git
diff --git a/trunk/lttv/QUICKSTART.html b/trunk/lttv/QUICKSTART.html
index 59bc934c..31c6bbae 100644
--- a/trunk/lttv/QUICKSTART.html
+++ b/trunk/lttv/QUICKSTART.html
@@ -1,11 +1,11 @@
- Linux Trace Toolkit Next Generation User Documentation
+ Linux Trace Toolkit Next Generation Manual
-Linux Trace Toolkit Next Generation User Documentation
+Linux Trace Toolkit Next Generation Manual
Author : Mathieu Desnoyers, September 2005
Last update : January 21st, 2009
@@ -15,6 +15,9 @@ Last update : January 21st, 2009
- Introduction
+
- Installing LTTng and LTTV from
sources
@@ -79,11 +82,16 @@ To see the list of compatibilities between LTTng, ltt-control, LTTV, please
refer to :
LTTng+LTTV versions compatibility
-The lttng patch is necessary to have the tracing hooks in the kernel.
+
+The ongoing work had the Linux Kernel Markers integrated in the mainline Linux
+kernel since Linux 2.6.24 and the Tracepoints since 2.6.28. In its current
+state, the lttng patchset is necessary to have the trace clocksource, the
+instrumentation and the LTTng high-speed data extraction mechanism added to the
+kernel.
-Supported architectures :
+
LTTng :
@@ -92,6 +100,11 @@ LTTng :
- ARM (with limited timestamping precision, e.g. 1HZ. Need
architecture-specific support for better precision)
- MIPS
+
- sh (partial architecture-specific instrumentation)
+
- sparc64 (partial architecture-specific instrumentation)
+
- s390 (partial architecture-specific instrumentation)
+
- Other architectures supported without architecture-specific instrumentation
+and with low-resolution timestamps.
LTTV :
@@ -422,7 +435,7 @@ see lttctl --help for details.
(note : to see if the buffers has been filled, look at the dmesg output after
-lttctl -R or after stopping tracing from the GUI, it will show an event lost
+lttctl -D or after stopping tracing from the GUI, it will show an event lost
count. If it is the case, try using larger buffers. See lttctl --help to learn
how. lttv now also shows event lost messages in the console when loading a trace
with missing events or lost subbuffers.)