X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=trunk%2Flttv%2FQUICKSTART.html;h=bbde9ecfd9cc6bf23a2b93928f4d5060a1336602;hb=196f71c403099b015052b9b1bc2ee6a0eb382f81;hp=0e1a36a250161ff15cb34ea83b033577767465cb;hpb=f7828b7ccba07835f79e34898faf94d3d9e7520d;p=lttv.git diff --git a/trunk/lttv/QUICKSTART.html b/trunk/lttv/QUICKSTART.html index 0e1a36a2..bbde9ecf 100644 --- a/trunk/lttv/QUICKSTART.html +++ b/trunk/lttv/QUICKSTART.html @@ -15,6 +15,9 @@ Last update : January 21st, 2009
+
  • Examples of LTTng use in the +field
    • +

    Introduction

    -This document is made of four parts : the first one explains how +This document is made of five parts : the first one explains how to install LTTng and LTTV from sources, the second one describes the steps to follow to trace a system and view it. The third part explains briefly how to add a new trace point to the kernel and to user space -applications. The fourth and last part explains how to create Debian or RPM -packages from the LTTng and LTTV sources. +applications. The fourth part explains how to create Debian or RPM +packages from the LTTng and LTTV sources. The fifth and last part describes use +of LTTng in the field.

    These operations are made for installing the LTTng 0.86 tracer on a linux 2.6.X kernel. You will also find instructions for installation of LTTV 0.12.x : the @@ -75,21 +82,33 @@ 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


    -Supported architectures : -br> LTTng :
    +
  • x86 32/64 bits
  • PowerPC 32 and 64 bits
  • 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 :
    +
  • Intel 32/64 bits
  • PowerPC 32 and 64 bits
  • Possibly others. Takes care of endianness and type size difference between @@ -416,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.) @@ -552,7 +571,50 @@ dpkg -i /usr/src/(image-name).deb

    Then, follow the section "Editing the system wide configuration" in section 2. +

    +

    Examples of LTTng use in the field

    +

    +A few examples of successful LTTng users : +