X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=trunk%2Flttv%2FQUICKSTART.html;h=bbde9ecfd9cc6bf23a2b93928f4d5060a1336602;hb=196f71c403099b015052b9b1bc2ee6a0eb382f81;hp=137b3f8cd87a6613e6abb689a45c7205ecfade68;hpb=07e962a1dad3dadb568d3e2cda8c3c28bd3d4747;p=lttv.git

diff --git a/trunk/lttv/QUICKSTART.html b/trunk/lttv/QUICKSTART.html
index 137b3f8c..bbde9ecf 100644
--- a/trunk/lttv/QUICKSTART.html
+++ b/trunk/lttv/QUICKSTART.html
@@ -15,6 +15,9 @@ Last update : January 21st, 2009<br>
 
 <ul>
 <li><a href="#intro" name="TOCintro">Introduction</a></li>
+<ul>
+<li><a href="#arch" name="TOCarch">Supported architectures</a></li>
+</ul>
 
 <li><a href="#section1" name="TOCsection1">Installing LTTng and LTTV from
 sources</a></li>
@@ -79,11 +82,16 @@ To see the list of compatibilities between LTTng, ltt-control, LTTV, please
 refer to :
 <a
 href="http://ltt.polymtl.ca/svn/trunk/lttv/doc/developer/lttng-lttv-compatibility.html">LTTng+LTTV versions compatibility</a>
-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.
 
 <br>
 <br>
-Supported architectures : 
+<h3><a href="#TOCarch" name="arch">Supported architectures</a></h3>
 <br>
 LTTng :<br>
 <br>
@@ -92,6 +100,11 @@ LTTng :<br>
 <li> ARM (with limited timestamping precision, e.g. 1HZ. Need
 architecture-specific support for better precision)
 <li> MIPS
+<li> sh (partial architecture-specific instrumentation)
+<li> sparc64 (partial architecture-specific instrumentation)
+<li> s390 (partial architecture-specific instrumentation)
+<li> Other architectures supported without architecture-specific instrumentation
+and with low-resolution timestamps.<br>
 <br>
 <br>
 LTTV :<br>
@@ -422,7 +435,7 @@ see lttctl --help for details.
 </PRE>
 <p>
 (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.)
@@ -571,9 +584,9 @@ A few examples of successful LTTng users :
   success with such tracing approach to fix "rare disk delay" issues and
   VM-related issues presented in this article :
 <ul>
-  <li> "Linux Kernel Debugging on Google-sized clusters at Ottawa Linux
-    Symposium 2007"
-    http://ltt.polymtl.ca/papers/bligh-Reprint.pdf
+  <li> <a href="http://ltt.polymtl.ca/papers/bligh-Reprint.pdf">Linux Kernel
+Debugging on Google-sized clusters at Ottawa Linux
+    Symposium 2007</a>
 </ul>
 <li> IBM Research have had problems with Commercial Scale-out applications,
   which are being an increasing trend to split large server workloads.