update features

[lttv.git] / trunk / lttv / QUICKSTART.html

diff --git a/trunk/lttv/QUICKSTART.html b/trunk/lttv/QUICKSTART.html
index 137b3f8cd87a6613e6abb689a45c7205ecfade68..8678c6d91ca77d87f5238dac15c8c50ab34d3861 100644 (file)
--- 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>
@@ -83,7 +86,7 @@ The lttng patch is necessary to have the tracing hooks in the kernel.
 
 <br>
 <br>
-Supported architectures : 
+<h3><a href="#TOCarch" name="arch">Supported architectures</a></h3>
 <br>
 LTTng :<br>
 <br>
@@ -92,6 +95,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>
@@ -571,9 +579,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.