1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >How to use the Linux Trace Toolkit Viewer's Reading Context
</TITLE
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE=
"Linux Trace Toolkit Viewer Developer Guide"
11 HREF=
"index.html"><LINK
16 TITLE=
"Why an event driven trace reader ?"
17 HREF=
"x46.html"></HEAD
28 SUMMARY=
"Header navigation table"
37 >Linux Trace Toolkit Viewer Developer Guide
</TH
74 >Chapter
2. How to use the Linux Trace Toolkit Viewer's Reading Context
</H1
84 > This chapter describes how to use the Linux Trace Toolkit reading context, a
85 data structure that is given as call data parameter of the modules'callbacks.
88 > Linux Trace Toolkit Viewer provides a backend that reads the traces. In combines
89 them in tracesets. A trace is an abstaction over many tracefiles, one per CPU.
90 LTTV reads the whole trace together, providing the events to modules by calling
91 their pre-registered hook lists in a chronological order.
100 SUMMARY=
"Footer navigation table"
149 >Why an event driven trace reader ?
</TD