1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >Control Flow View Colors
</TITLE
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE=
"Linux Trace Toolkit Viewer User Guide"
11 HREF=
"index.html"><LINK
13 TITLE=
"Using LTTV graphical interface"
16 TITLE=
"Using LTTV graphical interface"
19 TITLE=
"Using LTTV text modules"
20 HREF=
"c115.html"></HEAD
31 SUMMARY=
"Header navigation table"
40 >Linux Trace Toolkit Viewer User Guide
</TH
56 >Chapter
3. Using LTTV graphical interface
</TD
76 NAME=
"ControlFlowColors"
77 >3.2. Control Flow View Colors
</A
83 SRC=
"lttv-color-list.png"
87 >Control Flow View Color Legend
</P
92 > Here is a description of the colors used in the control flow view. Each color
93 represents a state of the process at a given time.
100 > White : this color is used for process from which state is not known. It may
101 happen when you seek quickly at a far time in the trace just after it has been
102 launched. At that moment, the precomputed state information is incomplete. The
103 "unknown" state is used to identify this. Note that the viewer gets refreshed
104 once the precomputation ends.
109 > Green : This color is only used for process when they are running in user mode.
110 That includes execution of all the source code of an executable as well as the
116 > Pale blue : A process is doing a system call to the kernel, and the mode is
117 switched from process limited rights to super user mode. Only code from the
118 kernel (including modules) should be run in that state.
123 > Yellow : The kernel is running a trap that services a fault. The most frequent
124 trap is the memory page fault trap : it is called every time a page is missing
125 from physical memory.
130 > Orange : IRQ servicing routine is running. It interrupts the currently running
131 process. As the IRQ does not change the currently running process (on some
132 architectures it uses the same stack as the process), the IRQ state is shown in
133 the state of the process. IRQ can be nested : a higher priority interrupt can
134 interrupt a lower priority interrupt.
139 > Pink : SoftIRQ handler is running. A SoftIRQ is normally triggered by an
140 interrupt that whishes to have some work done very soon, but not
"now". This is
141 especially useful, for example, to have the longest part of the network stack
142 traversal done : a too long computation in the interrupt handler would increase
143 the latency of the system. Therefore, doing the long part of the computation in
144 a softirq that will be run just after the IRQ handler exits will permits to do
145 this work while interrupts are enabled, without increasing the system latency.
150 > Dark red : A process in that state is waiting for an input/output operation to
151 complete before it can continue its execution.
156 > Dark yellow : A process is ready to run, but waiting to get the CPU (a schedule
162 > Dark purple : A process in zombie state. This state happens when a process
163 exits and then waits for the parent to wait for it (wait() or waitpid()).
168 > Dark green : A process has just been created by its parent and is waiting for
174 > Magenta : The process has exited, but still has the control of the CPU. It may
175 happend if it has some tasks to do in the exit system call.
185 SUMMARY=
"Footer navigation table"
224 >Using LTTV graphical interface
</TD
238 >Using LTTV text modules
</TD