</author>
</authorgroup>
-<date>29/11/2004</date>
-<releaseinfo>1.00.01</releaseinfo>
+<date>11/01/2006</date>
+<releaseinfo>1.00.02</releaseinfo>
<abstract>
<para>
<para>
Linux Trace Toolkit Viewer (LTTV) is the second generation of visualization
-tool. It is
-based on a trace format (the files where the data is recorded on disk) slightly
-different from LTT. As for now, November 29, 2004, the implementation of the new
-trace format in LTT is still not done, we must use a conversion tool to
-transform the original LTT traces to the new format.
+tool. It is based on a trace format (the files where the data is recorded on
+disk) written by the LTTng tracer.
</para>
<para>
<title>Getting started</title>
<sect1 id="install">
+<title>Installing LTTng and LTTV</title>
+<para>
+Follow the QUICKSTART guide found at
+<ulink url="http://ltt.polymtl.ca">ltt.polymtl.ca</ulink>.
+</para>
+
+<!--
<title>Installing LTTV</title>
<para>
First, you must download the latests version of LTTV. You should get it from
<prompt>$</prompt> <userinput>make</userinput>
<prompt>#</prompt> <userinput>make install</userinput> (as root)
</screen>
-
+-->
<para>
At this point, LTTV is installed in the default directory. You may find the
lttv executable in /usr/local/bin and the librairies in /usr/local/lib. You will
will be used later to convert from the Linux Trace Toolkit trace format to the
LTTV format.
</para>
-
+<!--
<para>
You are now ready to go to the next step : installing the LTT kernel tracer.
</para>
First, go to the <ulink url="http://ltt.polymtl.ca">ltt.polymtl.ca</ulink>
website, in the "Patches for the Official LTT" section. Use the latest version
of patches available. The file name convention used goes like this :
-aaaaaa-x.x--bbbbb-y.y.patch. That means a patch made for aaaaa, release x.x,
-that adds bbbbb, release y.y to it. Notice the presence of the -- sign that
+aaaaaa-x.x\-\-bbbbb-y.y.patch. That means a patch made for aaaaa, release x.x,
+that adds bbbbb, release y.y to it. Notice the presence of the \-\- sign that
separates the "from" field from the name of the patch applied. This way, it's
impossible to be mixed up on the specific sequence of patch application. I
suggest that you use the "relayfs", "ltt" and then "md" patches. The "md" patch
<para>
You now have a converted trace ready for visualization in LTTV. Congratulations!
</para>
-
+-->
</sect1>
<sect1 id="running">
Starting the graphical mode with the basic viewer activated is as simple as :
</para>
<screen>
-<prompt>$</prompt> <userinput>lttv -L /usr/local/lib/lttv/plugins -m lttvwindow\
--m guievents -m guicontrolflow -m guistatistics -t sample.converted/</userinput>
+<prompt>$</prompt> <userinput>lttv-gui</userinput>
</screen>
<para>
Using the text mode is very simple too. Look in /usr/local/lib/lttv/plugins for
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
+<HTML
+><HEAD
+><TITLE
+>Using LTTV text modules</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
+REL="HOME"
+TITLE="Linux Trace Toolkit Viewer User Guide"
+HREF="index.html"><LINK
+REL="PREVIOUS"
+TITLE="Control Flow View Colors"
+HREF="x81.html"><LINK
+REL="NEXT"
+TITLE="The text dump module"
+HREF="x125.html"></HEAD
+><BODY
+CLASS="chapter"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Linux Trace Toolkit Viewer User Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="x81.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="x125.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="chapter"
+><H1
+><A
+NAME="AEN115"
+></A
+>Chapter 4. Using LTTV text modules</H1
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="batchAnalysis"
+>4.1. The batch analysis module</A
+></H1
+><P
+> This batch analysis module can be invoked like this :
+</P
+><PRE
+CLASS="screen"
+> <SAMP
+CLASS="prompt"
+>$</SAMP
+> <KBD
+CLASS="userinput"
+>lttv -L path/to/lib/plugins -m batchAnalysis\
+-t trace1 -t trace2 ...</KBD
+>
+</PRE
+><P
+> It permits to call any registered action to perform in batch mode on all the
+trace set, which consists of the traces loaded on the command line. Actions that
+are built in the batchAnalysis module are statistics computation. They can be
+triggered by using the -s (--stats) switch.
+</P
+><P
+> However, the batchAnalysis module is mostly a backend for every other text
+module that does batch computation over a complete trace set.
+</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="x81.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="x125.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Control Flow View Colors</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>The text dump module</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Using LTTV text modules</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Control Flow View Colors"
-HREF="x127.html"><LINK
-REL="NEXT"
-TITLE="The text dump module"
-HREF="x169.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="x127.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="x169.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="AEN159"
-></A
->Chapter 4. Using LTTV text modules</H1
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="batchAnalysis"
->4.1. The batch analysis module</A
-></H1
-><P
-> This batch analysis module can be invoked like this :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L path/to/lib/plugins -m batchAnalysis\
--t trace1 -t trace2 ...</KBD
->
-</PRE
-><P
-> It permits to call any registered action to perform in batch mode on all the
-trace set, which consists of the traces loaded on the command line. Actions that
-are built in the batchAnalysis module are statistics computation. They can be
-triggered by using the -s (--stats) switch.
-</P
-><P
-> However, the batchAnalysis module is mostly a backend for every other text
-module that does batch computation over a complete trace set.
-</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="x127.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="x169.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Control Flow View Colors</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The text dump module</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Using LTTV text modules</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Control Flow View Colors"
-HREF="x130.html"><LINK
-REL="NEXT"
-TITLE="The text dump module"
-HREF="x172.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="x130.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="x172.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="AEN162"
-></A
->Chapter 4. Using LTTV text modules</H1
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="batchAnalysis"
->4.1. The batch analysis module</A
-></H1
-><P
-> This batch analysis module can be invoked like this :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L path/to/lib/plugins -m batchAnalysis\
--t trace1 -t trace2 ...</KBD
->
-</PRE
-><P
-> It permits to call any registered action to perform in batch mode on all the
-trace set, which consists of the traces loaded on the command line. Actions that
-are built in the batchAnalysis module are statistics computation. They can be
-triggered by using the -s (--stats) switch.
-</P
-><P
-> However, the batchAnalysis module is mostly a backend for every other text
-module that does batch computation over a complete trace set.
-</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="x130.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="x172.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Control Flow View Colors</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The text dump module</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Using LTTV text modules</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Control Flow View Colors"
-HREF="x130.html"><LINK
-REL="NEXT"
-TITLE="The text dump module"
-HREF="x174.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="x130.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="x174.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="AEN164"
-></A
->Chapter 4. Using LTTV text modules</H1
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="batchAnalysis"
->4.1. The batch analysis module</A
-></H1
-><P
-> This batch analysis module can be invoked like this :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L path/to/lib/plugins -m batchAnalysis\
--t trace1 -t trace2 ...</KBD
->
-</PRE
-><P
-> It permits to call any registered action to perform in batch mode on all the
-trace set, which consists of the traces loaded on the command line. Actions that
-are built in the batchAnalysis module are statistics computation. They can be
-triggered by using the -s (--stats) switch.
-</P
-><P
-> However, the batchAnalysis module is mostly a backend for every other text
-module that does batch computation over a complete trace set.
-</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="x130.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="x174.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Control Flow View Colors</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The text dump module</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
</P
><P
> Linux Trace Toolkit Viewer (LTTV) is the second generation of visualization
-tool. It is
-based on a trace format (the files where the data is recorded on disk) slightly
-different from LTT. As for now, November 29, 2004, the implementation of the new
-trace format in LTT is still not done, we must use a conversion tool to
-transform the original LTT traces to the new format.
+tool. It is based on a trace format (the files where the data is recorded on
+disk) written by the LTTng tracer.
</P
><P
> This document explains all the steps that are necessary in order to record a
TITLE="Introduction"
HREF="c20.html"><LINK
REL="NEXT"
-TITLE="Installing LTT kernel tracer"
-HREF="x46.html"></HEAD
+TITLE="Running the executable with basic libraries"
+HREF="x32.html"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="x46.html"
+HREF="x32.html"
ACCESSKEY="N"
>Next</A
></TD
CLASS="sect1"
><A
NAME="install"
->2.1. Installing LTTV</A
+>2.1. Installing LTTng and LTTV</A
></H1
><P
-> First, you must download the latests version of LTTV. You should get it from
+> Follow the QUICKSTART guide found at
+<A
HREF="http://ltt.polymtl.ca"
TARGET="_top"
>ltt.polymtl.ca</A
>.
-I suggest that you get it from the "Packages" section.
</P
><P
-> You need a recent gcc compiler to compile the project. You might want to use gcc
-3.2 or newer.
-You will also need some libraries in order to compile it. They are described in
-the README of the LTTV package. These are GTK 2.0, GLIB 2.0, "popt" and Pango 1.0.
-Install them if they are not on your system. Remember that if you use a package
-manager from you favourite Linux distribution, you will need to specifically
-install the librairies'development packages.
-</P
-><P
-> Then, you are ready to compile LTTV. Extract and untar the file you previously
-downloaded :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->tar -xvzof LinuxTraceToolkitViewer-x.x-dddddddd.tar.bz2</KBD
->
-</PRE
-><P
-> Then, go to the directory newly created, and type :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->./configure</KBD
->
-<SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->make</KBD
->
-<SAMP
-CLASS="prompt"
->#</SAMP
-> <KBD
-CLASS="userinput"
->make install</KBD
-> (as root)
-</PRE
-><P
> At this point, LTTV is installed in the default directory. You may find the
lttv executable in /usr/local/bin and the librairies in /usr/local/lib. You will
also notice the presence of the convert executable in /usr/local/bin. This tool
will be used later to convert from the Linux Trace Toolkit trace format to the
LTTV format.
</P
-><P
-> You are now ready to go to the next step : installing the LTT kernel tracer.
-</P
></DIV
></DIV
><DIV
ALIGN="right"
VALIGN="top"
><A
-HREF="x46.html"
+HREF="x32.html"
ACCESSKEY="N"
>Next</A
></TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Installing LTT kernel tracer</TD
+>Running the executable with basic libraries</TD
></TR
></TABLE
></DIV
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
+<HTML
+><HEAD
+><TITLE
+>Using LTTV graphical interface</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
+REL="HOME"
+TITLE="Linux Trace Toolkit Viewer User Guide"
+HREF="index.html"><LINK
+REL="PREVIOUS"
+TITLE="Running the executable with basic libraries"
+HREF="x32.html"><LINK
+REL="NEXT"
+TITLE="Control Flow View Colors"
+HREF="x81.html"></HEAD
+><BODY
+CLASS="chapter"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Linux Trace Toolkit Viewer User Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="x32.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="x81.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="chapter"
+><H1
+><A
+NAME="AEN42"
+></A
+>Chapter 3. Using LTTV graphical interface</H1
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="mainwindow"
+>3.1. LTTV main window</A
+></H1
+><P
+> This section describes the main functionnalities that are provided by the LTTV
+GUI and how to use them.
+</P
+><P
+> By default, when the lttv GUI starts with all the graphical modules loaded,
+it loads the statistics viewer, the control flow viewer, and the detailed event
+list inside a tab. Other viewers can be added later to this tab by interacting
+with the main window. Let's describe the operations available on the window :
+</P
+><DIV
+CLASS="mediaobject"
+><P
+><IMG
+SRC="lttv-numbered-5.png"
+ALIGN="center"><DIV
+CLASS="caption"
+><P
+>Linux Trace Toolkit Viewer GUI</P
+></DIV
+></P
+></DIV
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> This toolbar allows you to navigate through the basic functionnalities of LTTV.
+The first button opens a new window and the second one, a new tab. You can leave
+your mouse over the buttons to read the information provided by the tooltips.
+</P
+></LI
+><LI
+><P
+> This notebook, containing different tabs, lets you select the "Trace Set" you
+want to interact with. A trace set is an aggregation of traces, synchronised in
+time. You may also want to use one tab per viewer by simply cloning the traceset
+to a new tab. This way, you can have vertically stacked viewers in one tab, as
+well as different viewers, independant from the time interval. Note that once
+the Trace Set cloning is done, each trace set becomes completely independant.
+For Traceset cloning, see the File Menu.
+</P
+></LI
+><LI
+><P
+> These buttons let you control the computation in progress on a trace. As
+sometimes the computation may last for a while, you may want to stop it, restart
+it from the beginning or simply to continue from where you stopped. This is
+exactly what those three buttons offer you.
+</P
+></LI
+><LI
+><P
+> Buttons on the right side of the last spacer are semantically different from the
+others. While the other buttons at the left side of the bar are built in the
+lttv program and let you operate the basic functionnalities, the buttons at the
+right side let you add a viewer to the active Tab. They belong to the
+viewers themselves. The number of buttons that appears there should directly
+depend on the number of viewer's modules loaded.
+</P
+></LI
+><LI
+><P
+> This is a tree representing the multiple statistics available for the current
+traceset. This is shown by the guistatistics viewer.
+</P
+></LI
+><LI
+><P
+> This is the Y axis of the guicontrolflow viewer. It shows the process list of
+the traced system. You may notice that it grows : it dynamically adds
+process when they appear in the trace.
+</P
+></LI
+><LI
+><P
+> This is a (missing) time bar for the X axis. Maybe will it be used for viewer
+specific buttons eventually. Work in progress.
+</P
+></LI
+><LI
+><P
+> The is the current time selected. The concept of current event and current time
+selected is synchronised in a Tab for all the viewers. The control flow viewer
+shows it a vertical white dotted line. You move this marker by clicking on the
+background of the process state graph. This graph shows evolution of each
+process's state through time. The meaning of the colors will be explained later.
+</P
+></LI
+><LI
+><P
+> This is the details event list. It shown the detailed information about each
+event of the trace. It is synchronised with the current time and current event,
+so selecting an event changes other viewer's current time and reciprocally.
+</P
+></LI
+><LI
+><P
+> You can enter the values of start time and end time you wish to see on the
+screen here. It also supports pasting time as text input, simply by clicking of
+the "Time Frame", "start" or "end:" fields. A valid entry consists of any
+digital input separated by any quantity of non digital characters. For example :
+"I start at 356247.124626 and stop at 724524.453455" would be a valid input
+for the "Time Frame" field.
+</P
+></LI
+><LI
+><P
+> This horizontal scrollbar modifies the window of time shown by all the viewers
+in the tab. It is linked with the fields below it (described at number 10 and
+12). Another way to modify the time shown is to use the zoom buttons of the
+toolbar (yes, the ones that looks like magnifying glasses).
+</P
+></LI
+><LI
+><P
+> This field works just like the "Time Frame" field. It modifies the current time
+selected by the viewers. For example, changing its value will change the current
+event selected by the detailed events list and the current time selected by the
+control flow viewer.
+</P
+></LI
+></OL
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="x32.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="x81.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Running the executable with basic libraries</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Control Flow View Colors</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Using LTTV graphical interface</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Running the executable with basic libraries"
-HREF="x78.html"><LINK
-REL="NEXT"
-TITLE="Control Flow View Colors"
-HREF="x127.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="x78.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="x127.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="AEN88"
-></A
->Chapter 3. Using LTTV graphical interface</H1
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="mainwindow"
->3.1. LTTV main window</A
-></H1
-><P
-> This section describes the main functionnalities that are provided by the LTTV
-GUI and how to use them.
-</P
-><P
-> By default, when the lttv GUI starts with all the graphical modules loaded,
-it loads the statistics viewer, the control flow viewer, and the detailed event
-list inside a tab. Other viewers can be added later to this tab by interacting
-with the main window. Let's describe the operations available on the window :
-</P
-><DIV
-CLASS="mediaobject"
-><P
-><IMG
-SRC="lttv-numbered-5.png"
-ALIGN="center"><DIV
-CLASS="caption"
-><P
->Linux Trace Toolkit Viewer GUI</P
-></DIV
-></P
-></DIV
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> This toolbar allows you to navigate through the basic functionnalities of LTTV.
-The first button opens a new window and the second one, a new tab. You can leave
-your mouse over the buttons to read the information provided by the tooltips.
-</P
-></LI
-><LI
-><P
-> This notebook, containing different tabs, lets you select the "Trace Set" you
-want to interact with. A trace set is an aggregation of traces, synchronised in
-time. You may also want to use one tab per viewer by simply cloning the traceset
-to a new tab. This way, you can have vertically stacked viewers in one tab, as
-well as different viewers, independant from the time interval. Note that once
-the Trace Set cloning is done, each trace set becomes completely independant.
-For Traceset cloning, see the File Menu.
-</P
-></LI
-><LI
-><P
-> These buttons let you control the computation in progress on a trace. As
-sometimes the computation may last for a while, you may want to stop it, restart
-it from the beginning or simply to continue from where you stopped. This is
-exactly what those three buttons offer you.
-</P
-></LI
-><LI
-><P
-> Buttons on the right side of the last spacer are semantically different from the
-others. While the other buttons at the left side of the bar are built in the
-lttv program and let you operate the basic functionnalities, the buttons at the
-right side let you add a viewer to the active Tab. They belong to the
-viewers themselves. The number of buttons that appears there should directly
-depend on the number of viewer's modules loaded.
-</P
-></LI
-><LI
-><P
-> This is a tree representing the multiple statistics available for the current
-traceset. This is shown by the guistatistics viewer.
-</P
-></LI
-><LI
-><P
-> This is the Y axis of the guicontrolflow viewer. It shows the process list of
-the traced system. You may notice that it grows : it dynamically adds
-process when they appear in the trace.
-</P
-></LI
-><LI
-><P
-> This is a (missing) time bar for the X axis. Maybe will it be used for viewer
-specific buttons eventually. Work in progress.
-</P
-></LI
-><LI
-><P
-> The is the current time selected. The concept of current event and current time
-selected is synchronised in a Tab for all the viewers. The control flow viewer
-shows it a vertical white dotted line. You move this marker by clicking on the
-background of the process state graph. This graph shows evolution of each
-process's state through time. The meaning of the colors will be explained later.
-</P
-></LI
-><LI
-><P
-> This is the details event list. It shown the detailed information about each
-event of the trace. It is synchronised with the current time and current event,
-so selecting an event changes other viewer's current time and reciprocally.
-</P
-></LI
-><LI
-><P
-> You can enter the values of start time and end time you wish to see on the
-screen here. It also supports pasting time as text input, simply by clicking of
-the "Time Frame", "start" or "end:" fields. A valid entry consists of any
-digital input separated by any quantity of non digital characters. For example :
-"I start at 356247.124626 and stop at 724524.453455" would be a valid input
-for the "Time Frame" field.
-</P
-></LI
-><LI
-><P
-> This horizontal scrollbar modifies the window of time shown by all the viewers
-in the tab. It is linked with the fields below it (described at number 10 and
-12). Another way to modify the time shown is to use the zoom buttons of the
-toolbar (yes, the ones that looks like magnifying glasses).
-</P
-></LI
-><LI
-><P
-> This field works just like the "Time Frame" field. It modifies the current time
-selected by the viewers. For example, changing its value will change the current
-event selected by the detailed events list and the current time selected by the
-control flow viewer.
-</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="x78.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="x127.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Running the executable with basic libraries</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Control Flow View Colors</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Using LTTV graphical interface</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Running the executable with basic libraries"
-HREF="x81.html"><LINK
-REL="NEXT"
-TITLE="Control Flow View Colors"
-HREF="x130.html"></HEAD
-><BODY
-CLASS="chapter"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="x81.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="x130.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="chapter"
-><H1
-><A
-NAME="AEN91"
-></A
->Chapter 3. Using LTTV graphical interface</H1
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="mainwindow"
->3.1. LTTV main window</A
-></H1
-><P
-> This section describes the main functionnalities that are provided by the LTTV
-GUI and how to use them.
-</P
-><P
-> By default, when the lttv GUI starts with all the graphical modules loaded,
-it loads the statistics viewer, the control flow viewer, and the detailed event
-list inside a tab. Other viewers can be added later to this tab by interacting
-with the main window. Let's describe the operations available on the window :
-</P
-><DIV
-CLASS="mediaobject"
-><P
-><IMG
-SRC="lttv-numbered-5.png"
-ALIGN="center"><DIV
-CLASS="caption"
-><P
->Linux Trace Toolkit Viewer GUI</P
-></DIV
-></P
-></DIV
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> This toolbar allows you to navigate through the basic functionnalities of LTTV.
-The first button opens a new window and the second one, a new tab. You can leave
-your mouse over the buttons to read the information provided by the tooltips.
-</P
-></LI
-><LI
-><P
-> This notebook, containing different tabs, lets you select the "Trace Set" you
-want to interact with. A trace set is an aggregation of traces, synchronised in
-time. You may also want to use one tab per viewer by simply cloning the traceset
-to a new tab. This way, you can have vertically stacked viewers in one tab, as
-well as different viewers, independant from the time interval. Note that once
-the Trace Set cloning is done, each trace set becomes completely independant.
-For Traceset cloning, see the File Menu.
-</P
-></LI
-><LI
-><P
-> These buttons let you control the computation in progress on a trace. As
-sometimes the computation may last for a while, you may want to stop it, restart
-it from the beginning or simply to continue from where you stopped. This is
-exactly what those three buttons offer you.
-</P
-></LI
-><LI
-><P
-> Buttons on the right side of the last spacer are semantically different from the
-others. While the other buttons at the left side of the bar are built in the
-lttv program and let you operate the basic functionnalities, the buttons at the
-right side let you add a viewer to the active Tab. They belong to the
-viewers themselves. The number of buttons that appears there should directly
-depend on the number of viewer's modules loaded.
-</P
-></LI
-><LI
-><P
-> This is a tree representing the multiple statistics available for the current
-traceset. This is shown by the guistatistics viewer.
-</P
-></LI
-><LI
-><P
-> This is the Y axis of the guicontrolflow viewer. It shows the process list of
-the traced system. You may notice that it grows : it dynamically adds
-process when they appear in the trace.
-</P
-></LI
-><LI
-><P
-> This is a (missing) time bar for the X axis. Maybe will it be used for viewer
-specific buttons eventually. Work in progress.
-</P
-></LI
-><LI
-><P
-> The is the current time selected. The concept of current event and current time
-selected is synchronised in a Tab for all the viewers. The control flow viewer
-shows it a vertical white dotted line. You move this marker by clicking on the
-background of the process state graph. This graph shows evolution of each
-process's state through time. The meaning of the colors will be explained later.
-</P
-></LI
-><LI
-><P
-> This is the details event list. It shown the detailed information about each
-event of the trace. It is synchronised with the current time and current event,
-so selecting an event changes other viewer's current time and reciprocally.
-</P
-></LI
-><LI
-><P
-> You can enter the values of start time and end time you wish to see on the
-screen here. It also supports pasting time as text input, simply by clicking of
-the "Time Frame", "start" or "end:" fields. A valid entry consists of any
-digital input separated by any quantity of non digital characters. For example :
-"I start at 356247.124626 and stop at 724524.453455" would be a valid input
-for the "Time Frame" field.
-</P
-></LI
-><LI
-><P
-> This horizontal scrollbar modifies the window of time shown by all the viewers
-in the tab. It is linked with the fields below it (described at number 10 and
-12). Another way to modify the time shown is to use the zoom buttons of the
-toolbar (yes, the ones that looks like magnifying glasses).
-</P
-></LI
-><LI
-><P
-> This field works just like the "Time Frame" field. It modifies the current time
-selected by the viewers. For example, changing its value will change the current
-event selected by the detailed events list and the current time selected by the
-control flow viewer.
-</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="x81.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="x130.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Running the executable with basic libraries</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Control Flow View Colors</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
><DT
>2.1. <A
HREF="c25.html#install"
->Installing LTTV</A
+>Installing LTTng and LTTV</A
></DT
><DT
>2.2. <A
-HREF="x46.html"
->Installing LTT kernel tracer</A
-></DT
-><DT
->2.3. <A
-HREF="x54.html"
->Installing LTT trace recording daemon</A
-></DT
-><DT
->2.4. <A
-HREF="x64.html"
->Conversion from LTT to LTTV trace format</A
-></DT
-><DT
->2.5. <A
-HREF="x81.html"
+HREF="x32.html"
>Running the executable with basic libraries</A
></DT
></DL
></DD
><DT
>3. <A
-HREF="c91.html"
+HREF="c42.html"
>Using LTTV graphical interface</A
></DT
><DD
><DL
><DT
>3.1. <A
-HREF="c91.html#mainwindow"
+HREF="c42.html#mainwindow"
>LTTV main window</A
></DT
><DT
>3.2. <A
-HREF="x130.html"
+HREF="x81.html"
>Control Flow View Colors</A
></DT
></DL
></DD
><DT
>4. <A
-HREF="c164.html"
+HREF="c115.html"
>Using LTTV text modules</A
></DT
><DD
><DL
><DT
>4.1. <A
-HREF="c164.html#batchAnalysis"
+HREF="c115.html#batchAnalysis"
>The batch analysis module</A
></DT
><DT
>4.2. <A
-HREF="x174.html"
+HREF="x125.html"
>The text dump module</A
></DT
></DL
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
+<HTML
+><HEAD
+><TITLE
+>The text dump module</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
+REL="HOME"
+TITLE="Linux Trace Toolkit Viewer User Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Using LTTV text modules"
+HREF="c115.html"><LINK
+REL="PREVIOUS"
+TITLE="Using LTTV text modules"
+HREF="c115.html"></HEAD
+><BODY
+CLASS="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Linux Trace Toolkit Viewer User Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="c115.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 4. Using LTTV text modules</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+> </TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="textDump"
+>4.2. The text dump module</A
+></H1
+><P
+> The goal of this module is to convert the binary data of the traces into
+a formatted text file.
+</P
+><P
+> The text dump module is a good example of a usage of the batch analysis module
+backend. In fact, the text dump module depends on it. You don't need to
+explicitly load the batchAnalysis module though, as lttv offers a rich module
+backend that deals with the dependencies, loading the module automatically if
+needed.
+</P
+><P
+> The text dump module is invoked just like the batchAnalysis module. It adds more
+options that can be specified in argument. You may specify the -o switch for the
+output file name of the text dump. You can enable the output of the field names
+(the identifier of the fields) with the -l switch. The -s switch, for process
+states, is very useful to indicate the state in which the process is when the
+event happens.
+</P
+><P
+> If you use the --help option on the textDump module, you will see all the detail
+about the switches that can be used to show per cpu statistics and per process
+statistics. You will notice that you can use both the switches for the
+batchAnalysis module and those for textDump. You will also notice that the
+options --process_state (from textDump) and --stats (from batchAnalysis) has the
+same short name "-s". If you choose to invoke this option using the short name,
+it will use the option of the last module loaded just before the -s switch.
+</P
+><P
+> For exemple, if you load the textDump module with -m textDump, it will first
+load the batchAnalysis module, and then load itself. As it is the last module
+loaded, the -s switch used after it will signify --process_stats. On the other
+hand, if you choose to specify explicitly the loading of both modules like this
+:
+</P
+><PRE
+CLASS="screen"
+> <SAMP
+CLASS="prompt"
+>$</SAMP
+> <KBD
+CLASS="userinput"
+>lttv -L path/to/lib/plugins -m batchAnalysis -s\
+-m textDump -s -t trace</KBD
+>
+</PRE
+><P
+> The first "-s" will invoke batchAnalysis --stats and the second "-s" will invoke
+textDump --process_state. The list of options generated by --help follows the
+order of registration of the options by the modules, therefore the invocation
+order of the modules.
+</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="c115.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+> </TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Using LTTV text modules</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="c115.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+> </TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Control Flow View Colors</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using LTTV graphical interface"
-HREF="c88.html"><LINK
-REL="PREVIOUS"
-TITLE="Using LTTV graphical interface"
-HREF="c88.html"><LINK
-REL="NEXT"
-TITLE="Using LTTV text modules"
-HREF="c159.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="c88.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 3. Using LTTV graphical interface</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="c159.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="ControlFlowColors"
->3.2. Control Flow View Colors</A
-></H1
-><DIV
-CLASS="mediaobject"
-><P
-><IMG
-SRC="lttv-color-list.png"
-ALIGN="center"><DIV
-CLASS="caption"
-><P
->Control Flow View Color Legend</P
-></DIV
-></P
-></DIV
-><P
-> Here is a description of the colors used in the control flow view. Each color
-represents a state of the process at a given time.
-</P
-><P
-></P
-><UL
-><LI
-><P
-> White : this color is used for process from which state is not known. It may
-happen when you seek quickly at a far time in the trace just after it has been
-launched. At that moment, the precomputed state information is incomplete. The
-"unknown" state is used to identify this. Note that the viewer gets refreshed
-once the precomputation ends.
-</P
-></LI
-><LI
-><P
-> Green : This color is only used for process when they are running in user mode.
-That includes execution of all the source code of an executable as well as the
-libraries it uses.
-</P
-></LI
-><LI
-><P
-> Pale blue : A process is doing a system call to the kernel, and the mode is
-switched from process limited rights to super user mode. Only code from the
-kernel (including modules) should be run in that state.
-</P
-></LI
-><LI
-><P
-> Yellow : The kernel is running a trap that services a fault. The most frequent
-trap is the memory page fault trap : it is called every time a page is missing
-from physical memory.
-</P
-></LI
-><LI
-><P
-> Orange : IRQ servicing routine is running. It interrupts the currently running
-process. As the IRQ does not change the currently running process (on some
-architectures it uses the same stack as the process), the IRQ state is shown in
-the state of the process. IRQ can be nested : a higher priority interrupt can
-interrupt a lower priority interrupt.
-</P
-></LI
-><LI
-><P
-> Dark red : A process in that state is waiting for an input/output operation to
-complete before it can continue its execution.
-</P
-></LI
-><LI
-><P
-> Dark yellow : A process is ready to run, but waiting to get the CPU (a schedule
-in event).
-</P
-></LI
-><LI
-><P
-> Dark purple : A process in zombie state. This state happens when a process
-exits and then waits for the parent to wait for it (wait() or waitpid()).
-</P
-></LI
-><LI
-><P
-> Dark green : A process has just been created by its parent and is waiting for
-first scheduling.
-</P
-></LI
-><LI
-><P
-> Magenta : The process has exited, but still has the control of the CPU. It may
-happend if it has some tasks to do in the exit system call.
-</P
-></LI
-></UL
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="c88.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="c159.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using LTTV graphical interface</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c88.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Using LTTV text modules</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Control Flow View Colors</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using LTTV graphical interface"
-HREF="c91.html"><LINK
-REL="PREVIOUS"
-TITLE="Using LTTV graphical interface"
-HREF="c91.html"><LINK
-REL="NEXT"
-TITLE="Using LTTV text modules"
-HREF="c164.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="c91.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 3. Using LTTV graphical interface</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="c164.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="ControlFlowColors"
->3.2. Control Flow View Colors</A
-></H1
-><DIV
-CLASS="mediaobject"
-><P
-><IMG
-SRC="lttv-color-list.png"
-ALIGN="center"><DIV
-CLASS="caption"
-><P
->Control Flow View Color Legend</P
-></DIV
-></P
-></DIV
-><P
-> Here is a description of the colors used in the control flow view. Each color
-represents a state of the process at a given time.
-</P
-><P
-></P
-><UL
-><LI
-><P
-> White : this color is used for process from which state is not known. It may
-happen when you seek quickly at a far time in the trace just after it has been
-launched. At that moment, the precomputed state information is incomplete. The
-"unknown" state is used to identify this. Note that the viewer gets refreshed
-once the precomputation ends.
-</P
-></LI
-><LI
-><P
-> Green : This color is only used for process when they are running in user mode.
-That includes execution of all the source code of an executable as well as the
-libraries it uses.
-</P
-></LI
-><LI
-><P
-> Pale blue : A process is doing a system call to the kernel, and the mode is
-switched from process limited rights to super user mode. Only code from the
-kernel (including modules) should be run in that state.
-</P
-></LI
-><LI
-><P
-> Yellow : The kernel is running a trap that services a fault. The most frequent
-trap is the memory page fault trap : it is called every time a page is missing
-from physical memory.
-</P
-></LI
-><LI
-><P
-> Orange : IRQ servicing routine is running. It interrupts the currently running
-process. As the IRQ does not change the currently running process (on some
-architectures it uses the same stack as the process), the IRQ state is shown in
-the state of the process. IRQ can be nested : a higher priority interrupt can
-interrupt a lower priority interrupt.
-</P
-></LI
-><LI
-><P
-> Pink : SoftIRQ handler is running. A SoftIRQ is normally triggered by an
-interrupt that whishes to have some work done very soon, but not "now". This is
-especially useful, for example, to have the longest part of the network stack
-traversal done : a too long computation in the interrupt handler would increase
-the latency of the system. Therefore, doing the long part of the computation in
-a softirq that will be run just after the IRQ handler exits will permits to do
-this work while interrupts are enabled, without increasing the system latency.
-</P
-></LI
-><LI
-><P
-> Dark red : A process in that state is waiting for an input/output operation to
-complete before it can continue its execution.
-</P
-></LI
-><LI
-><P
-> Dark yellow : A process is ready to run, but waiting to get the CPU (a schedule
-in event).
-</P
-></LI
-><LI
-><P
-> Dark purple : A process in zombie state. This state happens when a process
-exits and then waits for the parent to wait for it (wait() or waitpid()).
-</P
-></LI
-><LI
-><P
-> Dark green : A process has just been created by its parent and is waiting for
-first scheduling.
-</P
-></LI
-><LI
-><P
-> Magenta : The process has exited, but still has the control of the CPU. It may
-happend if it has some tasks to do in the exit system call.
-</P
-></LI
-></UL
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="c91.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="c164.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using LTTV graphical interface</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c91.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Using LTTV text modules</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->The text dump module</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using LTTV text modules"
-HREF="c159.html"><LINK
-REL="PREVIOUS"
-TITLE="Using LTTV text modules"
-HREF="c159.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="c159.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Using LTTV text modules</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-> </TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="textDump"
->4.2. The text dump module</A
-></H1
-><P
-> The goal of this module is to convert the binary data of the traces into
-a formatted text file.
-</P
-><P
-> The text dump module is a good example of a usage of the batch analysis module
-backend. In fact, the text dump module depends on it. You don't need to
-explicitly load the batchAnalysis module though, as lttv offers a rich module
-backend that deals with the dependencies, loading the module automatically if
-needed.
-</P
-><P
-> The text dump module is invoked just like the batchAnalysis module. It adds more
-options that can be specified in argument. You may specify the -o switch for the
-output file name of the text dump. You can enable the output of the field names
-(the identifier of the fields) with the -l switch. The -s switch, for process
-states, is very useful to indicate the state in which the process is when the
-event happens.
-</P
-><P
-> If you use the --help option on the textDump module, you will see all the detail
-about the switches that can be used to show per cpu statistics and per process
-statistics. You will notice that you can use both the switches for the
-batchAnalysis module and those for textDump. You will also notice that the
-options --process_state (from textDump) and --stats (from batchAnalysis) has the
-same short name "-s". If you choose to invoke this option using the short name,
-it will use the option of the last module loaded just before the -s switch.
-</P
-><P
-> For exemple, if you load the textDump module with -m textDump, it will first
-load the batchAnalysis module, and then load itself. As it is the last module
-loaded, the -s switch used after it will signify --process_stats. On the other
-hand, if you choose to specify explicitly the loading of both modules like this
-:
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L path/to/lib/plugins -m batchAnalysis -s\
--m textDump -s -t trace</KBD
->
-</PRE
-><P
-> The first "-s" will invoke batchAnalysis --stats and the second "-s" will invoke
-textDump --process_state. The list of options generated by --help follows the
-order of registration of the options by the modules, therefore the invocation
-order of the modules.
-</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="c159.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-> </TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using LTTV text modules</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c159.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-> </TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->The text dump module</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using LTTV text modules"
-HREF="c162.html"><LINK
-REL="PREVIOUS"
-TITLE="Using LTTV text modules"
-HREF="c162.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="c162.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Using LTTV text modules</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-> </TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="textDump"
->4.2. The text dump module</A
-></H1
-><P
-> The goal of this module is to convert the binary data of the traces into
-a formatted text file.
-</P
-><P
-> The text dump module is a good example of a usage of the batch analysis module
-backend. In fact, the text dump module depends on it. You don't need to
-explicitly load the batchAnalysis module though, as lttv offers a rich module
-backend that deals with the dependencies, loading the module automatically if
-needed.
-</P
-><P
-> The text dump module is invoked just like the batchAnalysis module. It adds more
-options that can be specified in argument. You may specify the -o switch for the
-output file name of the text dump. You can enable the output of the field names
-(the identifier of the fields) with the -l switch. The -s switch, for process
-states, is very useful to indicate the state in which the process is when the
-event happens.
-</P
-><P
-> If you use the --help option on the textDump module, you will see all the detail
-about the switches that can be used to show per cpu statistics and per process
-statistics. You will notice that you can use both the switches for the
-batchAnalysis module and those for textDump. You will also notice that the
-options --process_state (from textDump) and --stats (from batchAnalysis) has the
-same short name "-s". If you choose to invoke this option using the short name,
-it will use the option of the last module loaded just before the -s switch.
-</P
-><P
-> For exemple, if you load the textDump module with -m textDump, it will first
-load the batchAnalysis module, and then load itself. As it is the last module
-loaded, the -s switch used after it will signify --process_stats. On the other
-hand, if you choose to specify explicitly the loading of both modules like this
-:
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L path/to/lib/plugins -m batchAnalysis -s\
--m textDump -s -t trace</KBD
->
-</PRE
-><P
-> The first "-s" will invoke batchAnalysis --stats and the second "-s" will invoke
-textDump --process_state. The list of options generated by --help follows the
-order of registration of the options by the modules, therefore the invocation
-order of the modules.
-</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="c162.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-> </TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using LTTV text modules</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c162.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-> </TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->The text dump module</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using LTTV text modules"
-HREF="c164.html"><LINK
-REL="PREVIOUS"
-TITLE="Using LTTV text modules"
-HREF="c164.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="c164.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Using LTTV text modules</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-> </TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="textDump"
->4.2. The text dump module</A
-></H1
-><P
-> The goal of this module is to convert the binary data of the traces into
-a formatted text file.
-</P
-><P
-> The text dump module is a good example of a usage of the batch analysis module
-backend. In fact, the text dump module depends on it. You don't need to
-explicitly load the batchAnalysis module though, as lttv offers a rich module
-backend that deals with the dependencies, loading the module automatically if
-needed.
-</P
-><P
-> The text dump module is invoked just like the batchAnalysis module. It adds more
-options that can be specified in argument. You may specify the -o switch for the
-output file name of the text dump. You can enable the output of the field names
-(the identifier of the fields) with the -l switch. The -s switch, for process
-states, is very useful to indicate the state in which the process is when the
-event happens.
-</P
-><P
-> If you use the --help option on the textDump module, you will see all the detail
-about the switches that can be used to show per cpu statistics and per process
-statistics. You will notice that you can use both the switches for the
-batchAnalysis module and those for textDump. You will also notice that the
-options --process_state (from textDump) and --stats (from batchAnalysis) has the
-same short name "-s". If you choose to invoke this option using the short name,
-it will use the option of the last module loaded just before the -s switch.
-</P
-><P
-> For exemple, if you load the textDump module with -m textDump, it will first
-load the batchAnalysis module, and then load itself. As it is the last module
-loaded, the -s switch used after it will signify --process_stats. On the other
-hand, if you choose to specify explicitly the loading of both modules like this
-:
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L path/to/lib/plugins -m batchAnalysis -s\
--m textDump -s -t trace</KBD
->
-</PRE
-><P
-> The first "-s" will invoke batchAnalysis --stats and the second "-s" will invoke
-textDump --process_state. The list of options generated by --help follows the
-order of registration of the options by the modules, therefore the invocation
-order of the modules.
-</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="c164.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-> </TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using LTTV text modules</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c164.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-> </TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
+<HTML
+><HEAD
+><TITLE
+>Running the executable with basic libraries</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
+REL="HOME"
+TITLE="Linux Trace Toolkit Viewer User Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Getting started"
+HREF="c25.html"><LINK
+REL="PREVIOUS"
+TITLE="Getting started"
+HREF="c25.html"><LINK
+REL="NEXT"
+TITLE="Using LTTV graphical interface"
+HREF="c42.html"></HEAD
+><BODY
+CLASS="sect1"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Linux Trace Toolkit Viewer User Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="c25.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 2. Getting started</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="c42.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="sect1"
+><H1
+CLASS="sect1"
+><A
+NAME="running"
+>2.2. Running the executable with basic libraries</A
+></H1
+><P
+> Starting the graphical mode with the basic viewer activated is as simple as :
+</P
+><PRE
+CLASS="screen"
+> <SAMP
+CLASS="prompt"
+>$</SAMP
+> <KBD
+CLASS="userinput"
+>lttv-gui</KBD
+>
+</PRE
+><P
+> Using the text mode is very simple too. Look in /usr/local/lib/lttv/plugins for
+the list of modules. You may use the --help switch to get basic help on the
+command line parameters of every loaded modules. To simply output the events of
+a trace in a text file, try the textDump module. The batchAnalysis module
+permits to do batch mode analysis (state and statistics calculation ) on a
+trace.
+</P
+><PRE
+CLASS="screen"
+> <SAMP
+CLASS="prompt"
+>$</SAMP
+> <KBD
+CLASS="userinput"
+>lttv -L /usr/local/lib/lttv/plugins -m textDump --help</KBD
+>
+</PRE
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="c25.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="c42.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Getting started</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="c25.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Using LTTV graphical interface</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Installing LTT kernel tracer</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Getting started"
-HREF="c25.html"><LINK
-REL="PREVIOUS"
-TITLE="Getting started"
-HREF="c25.html"><LINK
-REL="NEXT"
-TITLE="Installing LTT trace recording daemon"
-HREF="x54.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="c25.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Getting started</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="x54.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="install-tracer"
->2.2. Installing LTT kernel tracer</A
-></H1
-><P
-> The goal of this guide is not to describe the Linux Trace Toolkit project in
-details, as it is a
-seperate project for now. It just gives pointers to the basic steps you must
-take in order to generate a trace suitable for conversion.
-</P
-><P
-> First, go to the <A
-HREF="http://ltt.polymtl.ca"
-TARGET="_top"
->ltt.polymtl.ca</A
->
-website, in the "Patches for the Official LTT" section. Use the latest version
-of patches available. The file name convention used goes like this :
-aaaaaa-x.x--bbbbb-y.y.patch. That means a patch made for aaaaa, release x.x,
-that adds bbbbb, release y.y to it. Notice the presence of the -- sign that
-separates the "from" field from the name of the patch applied. This way, it's
-impossible to be mixed up on the specific sequence of patch application. I
-suggest that you use the "relayfs", "ltt" and then "md" patches. The "md" patch
-adds events useful to LTTV that are not in the official LTT.
-</P
-><P
-> Once you have the patches you need, get the matching Linux kernel version, apply
-the patches on it, configure it, install it, reboot with the new kernel. You then
-have an instrumented kernel ready for tracing. If you have problems during this phase,
-please refer to <A
-HREF="http://www.opersys.com/ltt"
-TARGET="_top"
->www.opersys.com/ltt</A
->. If you need
-instructions about how to recompile a kernel, see
-<A
-HREF="http://www.tldp.org/HOWTO/Kernel-HOWTO/"
-TARGET="_top"
->Kernel-HOWTO</A
->.
-</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="c25.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="x54.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Getting started</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c25.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Installing LTT trace recording daemon</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Installing LTT trace recording daemon</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Getting started"
-HREF="c25.html"><LINK
-REL="PREVIOUS"
-TITLE="Installing LTT kernel tracer"
-HREF="x46.html"><LINK
-REL="NEXT"
-TITLE="Conversion from LTT to LTTV trace format"
-HREF="x64.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="x46.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Getting started</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="x64.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="install-daemon"
->2.3. Installing LTT trace recording daemon</A
-></H1
-><P
-> In order to install the LTT trace recording daemon, you should get the latest
-TraceToolkit (or ltt) package from the LTT ftp site.
-Use the link "Official Linux Trace Toolkit Packages" on the
-<A
-HREF="http://ltt.polymtl.ca"
-TARGET="_top"
->ltt.polymtl.ca</A
-> webpage to access it.
-As of November 30, 2004, the most recent version is 0.9.6-pre3.
-</P
-><P
-> Then, you should apply the TraceToolkit patches from the LTTV website related
-to the package version. Get them from the "Patches for the Official LTT"
-section.
-</P
-><P
-> You are now ready to install the daemon in your system. Please refer to the
-documentation in the package for details.
-</P
-><P
-> You may now use the following command to record a sample 30 seconds trace in
-your current directory. Command line switches are described on the official
-LTT website.
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->#</SAMP
-><KBD
-CLASS="userinput"
->tracedaemon -ts30 sample.out sample.proc (as root) userinput></KBD
->
-</PRE
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="x46.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="x64.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Installing LTT kernel tracer</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c25.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Conversion from LTT to LTTV trace format</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Conversion from LTT to LTTV trace format</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Getting started"
-HREF="c25.html"><LINK
-REL="PREVIOUS"
-TITLE="Installing LTT trace recording daemon"
-HREF="x54.html"><LINK
-REL="NEXT"
-TITLE="Running the executable with basic libraries"
-HREF="x78.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="x54.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Getting started</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="x78.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="convert"
->2.4. Conversion from LTT to LTTV trace format</A
-></H1
-><P
-> If you used the default directory for installation, you should find the
-conversion tool in /usr/local/bin/convert. Before using it, some other files are
-necessary. You will find them in
-/usr/local/share/LinuxTraceToolkitViewer/convert/. Those are sysInfo and
-core.xml.
-</P
-><P
-> sysInfo is a script that get informations about the traced computer. It should
-be invoked like this :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->sh /usr/local/LinuxTraceToolkitViewer/convert/sysInfo</KBD
->
-</PRE
-><P
-> It created a file named sysInfo.out. This file has to be present in the current
-directory where the convert tool will be executed. I suggest that you choose a
-destination directory for converted traces right now, put sysInfo.out in it, at
-use it as current directory for running the convert tool.
-</P
-><P
-> Once the sysInfo.out file is ready and you have a trace ready for conversion,
-you should invoke convert like the following example. This is for a uniprocessor
-computer. If you whish to get detailed explanation on the parameters, simply
-execute the convert tool without any. You may also wish to see the
-/usr/local/LinuxTraceToolkitViewer/convert/README file.
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->/usr/local/bin/convert sample.proc 1 sample.trace sample.converted</KBD
->
-</PRE
-><P
-> You must then copy the core event definition file to the converted trace directory :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->cp /usr/local/share/LinuxTraceToolkitViewer/convert/core.xml sample.converted/</KBD
->
-</PRE
-><P
-> You now have a converted trace ready for visualization in LTTV. Congratulations!
-</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="x54.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="x78.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Installing LTT trace recording daemon</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c25.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Running the executable with basic libraries</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Conversion from LTT to LTTV trace format</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Getting started"
-HREF="c25.html"><LINK
-REL="PREVIOUS"
-TITLE="Installing LTT trace recording daemon"
-HREF="x54.html"><LINK
-REL="NEXT"
-TITLE="Running the executable with basic libraries"
-HREF="x81.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="x54.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Getting started</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="x81.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="convert"
->2.4. Conversion from LTT to LTTV trace format</A
-></H1
-><P
-> If you used the default directory for installation, you should find the
-conversion tool in /usr/local/bin/convert. Before using it, some other files are
-necessary. You will find them in
-/usr/local/share/LinuxTraceToolkitViewer/convert/. Those are sysInfo and
-core.xml.
-</P
-><P
-> sysInfo is a script that get informations about the traced computer. It should
-be invoked like this :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->sh /usr/local/LinuxTraceToolkitViewer/convert/sysInfo</KBD
->
-</PRE
-><P
-> It creates a file named sysInfo.out. This file has to be present in the current
-directory where the convert tool will be executed. I suggest that you choose a
-destination directory where will be written converted traces right now, put sysInfo.out in it, at
-use it as current directory for running the convert tool.
-</P
-><P
-> Once the sysInfo.out file is ready and you have a trace ready for conversion,
-you should invoke convert like the following example. This is for a uniprocessor
-computer. If you whish to get detailed explanation on the parameters, simply
-execute the convert tool without any option. You may also wish to see the
-/usr/local/LinuxTraceToolkitViewer/convert/README file.
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->/usr/local/bin/convert sample.proc 1 sample.trace sample.converted</KBD
->
-</PRE
-><P
-> You must then copy the core event definition file to the converted trace directory :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->cp /usr/local/share/LinuxTraceToolkitViewer/convert/core.xml sample.converted/</KBD
->
-</PRE
-><P
-> You now have a converted trace ready for visualization in LTTV. Congratulations!
-</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="x54.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="x81.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Installing LTT trace recording daemon</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c25.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Running the executable with basic libraries</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->Running the executable with basic libraries</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Linux Trace Toolkit Viewer User Guide"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Getting started"
-HREF="c25.html"><LINK
-REL="PREVIOUS"
-TITLE="Conversion from LTT to LTTV trace format"
-HREF="x61.html"><LINK
-REL="NEXT"
-TITLE="Using LTTV graphical interface"
-HREF="c88.html"></HEAD
-><BODY
-CLASS="sect1"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Linux Trace Toolkit Viewer User Guide</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="x61.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Getting started</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="c88.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="running"
->2.5. Running the executable with basic libraries</A
-></H1
-><P
-> Starting the graphical mode with the basic viewer activated is as simple as :
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L /usr/local/lib/lttv/plugins -m lttvwindow\
--m guievents -m guicontrolflow -m guistatistics -t sample.converted/</KBD
->
-</PRE
-><P
-> Using the text mode is very simple too. Look in /usr/local/lib/lttv/plugins for
-the list of modules. You may use the --help switch to get basic help on the
-command line parameters of every loaded modules. To simply output the events of
-a trace in a text file, try the textDump module. The batchAnalysis module
-permits to do batch mode analysis (state and statistics calculation ) on a
-trace.
-</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L /usr/local/lib/lttv/plugins -m textDump --help</KBD
->
-</PRE
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="x61.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="c88.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Conversion from LTT to LTTV trace format</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="c25.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Using LTTV graphical interface</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
<HTML
><HEAD
><TITLE
->Running the executable with basic libraries</TITLE
+>Control Flow View Colors</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
TITLE="Linux Trace Toolkit Viewer User Guide"
HREF="index.html"><LINK
REL="UP"
-TITLE="Getting started"
-HREF="c25.html"><LINK
+TITLE="Using LTTV graphical interface"
+HREF="c42.html"><LINK
REL="PREVIOUS"
-TITLE="Conversion from LTT to LTTV trace format"
-HREF="x64.html"><LINK
-REL="NEXT"
TITLE="Using LTTV graphical interface"
-HREF="c91.html"></HEAD
+HREF="c42.html"><LINK
+REL="NEXT"
+TITLE="Using LTTV text modules"
+HREF="c115.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="x64.html"
+HREF="c42.html"
ACCESSKEY="P"
>Prev</A
></TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 2. Getting started</TD
+>Chapter 3. Using LTTV graphical interface</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="c91.html"
+HREF="c115.html"
ACCESSKEY="N"
>Next</A
></TD
><H1
CLASS="sect1"
><A
-NAME="running"
->2.5. Running the executable with basic libraries</A
+NAME="ControlFlowColors"
+>3.2. Control Flow View Colors</A
></H1
+><DIV
+CLASS="mediaobject"
+><P
+><IMG
+SRC="lttv-color-list.png"
+ALIGN="center"><DIV
+CLASS="caption"
+><P
+>Control Flow View Color Legend</P
+></DIV
+></P
+></DIV
><P
-> Starting the graphical mode with the basic viewer activated is as simple as :
+> Here is a description of the colors used in the control flow view. Each color
+represents a state of the process at a given time.
</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L /usr/local/lib/lttv/plugins -m lttvwindow\
--m guievents -m guicontrolflow -m guistatistics -t sample.converted/</KBD
->
-</PRE
><P
-> Using the text mode is very simple too. Look in /usr/local/lib/lttv/plugins for
-the list of modules. You may use the --help switch to get basic help on the
-command line parameters of every loaded modules. To simply output the events of
-a trace in a text file, try the textDump module. The batchAnalysis module
-permits to do batch mode analysis (state and statistics calculation ) on a
-trace.
+></P
+><UL
+><LI
+><P
+> White : this color is used for process from which state is not known. It may
+happen when you seek quickly at a far time in the trace just after it has been
+launched. At that moment, the precomputed state information is incomplete. The
+"unknown" state is used to identify this. Note that the viewer gets refreshed
+once the precomputation ends.
+</P
+></LI
+><LI
+><P
+> Green : This color is only used for process when they are running in user mode.
+That includes execution of all the source code of an executable as well as the
+libraries it uses.
+</P
+></LI
+><LI
+><P
+> Pale blue : A process is doing a system call to the kernel, and the mode is
+switched from process limited rights to super user mode. Only code from the
+kernel (including modules) should be run in that state.
+</P
+></LI
+><LI
+><P
+> Yellow : The kernel is running a trap that services a fault. The most frequent
+trap is the memory page fault trap : it is called every time a page is missing
+from physical memory.
</P
-><PRE
-CLASS="screen"
-> <SAMP
-CLASS="prompt"
->$</SAMP
-> <KBD
-CLASS="userinput"
->lttv -L /usr/local/lib/lttv/plugins -m textDump --help</KBD
->
-</PRE
+></LI
+><LI
+><P
+> Orange : IRQ servicing routine is running. It interrupts the currently running
+process. As the IRQ does not change the currently running process (on some
+architectures it uses the same stack as the process), the IRQ state is shown in
+the state of the process. IRQ can be nested : a higher priority interrupt can
+interrupt a lower priority interrupt.
+</P
+></LI
+><LI
+><P
+> Pink : SoftIRQ handler is running. A SoftIRQ is normally triggered by an
+interrupt that whishes to have some work done very soon, but not "now". This is
+especially useful, for example, to have the longest part of the network stack
+traversal done : a too long computation in the interrupt handler would increase
+the latency of the system. Therefore, doing the long part of the computation in
+a softirq that will be run just after the IRQ handler exits will permits to do
+this work while interrupts are enabled, without increasing the system latency.
+</P
+></LI
+><LI
+><P
+> Dark red : A process in that state is waiting for an input/output operation to
+complete before it can continue its execution.
+</P
+></LI
+><LI
+><P
+> Dark yellow : A process is ready to run, but waiting to get the CPU (a schedule
+in event).
+</P
+></LI
+><LI
+><P
+> Dark purple : A process in zombie state. This state happens when a process
+exits and then waits for the parent to wait for it (wait() or waitpid()).
+</P
+></LI
+><LI
+><P
+> Dark green : A process has just been created by its parent and is waiting for
+first scheduling.
+</P
+></LI
+><LI
+><P
+> Magenta : The process has exited, but still has the control of the CPU. It may
+happend if it has some tasks to do in the exit system call.
+</P
+></LI
+></UL
></DIV
><DIV
CLASS="NAVFOOTER"
ALIGN="left"
VALIGN="top"
><A
-HREF="x64.html"
+HREF="c42.html"
ACCESSKEY="P"
>Prev</A
></TD
ALIGN="right"
VALIGN="top"
><A
-HREF="c91.html"
+HREF="c115.html"
ACCESSKEY="N"
>Next</A
></TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Conversion from LTT to LTTV trace format</TD
+>Using LTTV graphical interface</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
-HREF="c25.html"
+HREF="c42.html"
ACCESSKEY="U"
>Up</A
></TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Using LTTV graphical interface</TD
+>Using LTTV text modules</TD
></TR
></TABLE
></DIV
projects / lttv.git / commitdiff
