User`s guide

Using the Execution Graph to View Program Execution
Thread Scheduling 4-79
4.10.2 Threads in the Execution Graph Window
The SWI and PRD functions listed in the left column are listed from highest
to lowest priority. However, for performance reasons, there is no information
in the Execution Graph about hardware interrupt and background threads
(aside from the CLK ticks, which are normally performed by an interrupt).
Time not spent within an SWI, PRD, or TSK thread must be within an HWI or
IDL thread, so this time is shown in the Other Threads row.
Functions run by PIP (notify functions) run as part of the thread that called the
PIP API. The LNK_dataPump object runs a function that manages the host’s
end of an HST (Host Channel Manager) object. This object and other IDL
objects run from the IDL background thread, and are included in the Other
Threads row.
Note:
The Time marks and the PRD Ticks are not equally spaced. This graph
shows a square for each event. If many events occur between two Time
interrupts or PRD Ticks, the distance between the marks is wider than for
intervals during which fewer events occurred.
4.10.3 Sequence Numbers in the Execution Graph Window
The tick marks above the bottom scroll bar in Figure 4-22 show the sequence
of events in the Execution Graph.
Note:
Circular logs (the default for the Execution Graph) contain only the most
recent n events. Normally, there are events that are not listed in the log
because they occur after the host polls the log and are overwritten before
the next time the host polls the log. The Execution Graph shows a red
vertical line and a break in the log sequence numbers at the end of each
group of log events it polls.
You can view more log events by increasing the size of the log to hold the full
sequence of events you want to examine. You can also set the RTA Control
Panel to log only the events you want to examine.