X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=trunk%2Flttv%2FQUICKSTART.html;h=bbde9ecfd9cc6bf23a2b93928f4d5060a1336602;hb=196f71c403099b015052b9b1bc2ee6a0eb382f81;hp=cf6733f9a8610e5e3e3dc6d6c2d35ad39da97ef2;hpb=7e77d1a9ef11e94da20e89456656f3512cb53b9b;p=lttv.git
diff --git a/trunk/lttv/QUICKSTART.html b/trunk/lttv/QUICKSTART.html
index cf6733f9..bbde9ecf 100644
--- a/trunk/lttv/QUICKSTART.html
+++ b/trunk/lttv/QUICKSTART.html
@@ -82,7 +82,12 @@ 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.
@@ -95,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 :
@@ -425,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.)