7cb02901 |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd"> |
2 | <HTML |
3 | ><HEAD |
4 | ><TITLE |
5 | >How to use the Linux Trace Toolkit Viewer's Reading Context</TITLE |
6 | ><META |
7 | NAME="GENERATOR" |
8 | CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK |
9 | REL="HOME" |
10 | TITLE="Linux Trace Toolkit Viewer Developer Guide" |
11 | HREF="index.html"><LINK |
12 | REL="PREVIOUS" |
13 | TITLE="The hooks" |
14 | HREF="x33.html"><LINK |
15 | REL="NEXT" |
16 | TITLE="Why an event driven trace reader ?" |
17 | HREF="x46.html"></HEAD |
18 | ><BODY |
19 | CLASS="chapter" |
20 | BGCOLOR="#FFFFFF" |
21 | TEXT="#000000" |
22 | LINK="#0000FF" |
23 | VLINK="#840084" |
24 | ALINK="#0000FF" |
25 | ><DIV |
26 | CLASS="NAVHEADER" |
27 | ><TABLE |
28 | SUMMARY="Header navigation table" |
29 | WIDTH="100%" |
30 | BORDER="0" |
31 | CELLPADDING="0" |
32 | CELLSPACING="0" |
33 | ><TR |
34 | ><TH |
35 | COLSPAN="3" |
36 | ALIGN="center" |
37 | >Linux Trace Toolkit Viewer Developer Guide</TH |
38 | ></TR |
39 | ><TR |
40 | ><TD |
41 | WIDTH="10%" |
42 | ALIGN="left" |
43 | VALIGN="bottom" |
44 | ><A |
45 | HREF="x33.html" |
46 | ACCESSKEY="P" |
47 | >Prev</A |
48 | ></TD |
49 | ><TD |
50 | WIDTH="80%" |
51 | ALIGN="center" |
52 | VALIGN="bottom" |
53 | ></TD |
54 | ><TD |
55 | WIDTH="10%" |
56 | ALIGN="right" |
57 | VALIGN="bottom" |
58 | ><A |
59 | HREF="x46.html" |
60 | ACCESSKEY="N" |
61 | >Next</A |
62 | ></TD |
63 | ></TR |
64 | ></TABLE |
65 | ><HR |
66 | ALIGN="LEFT" |
67 | WIDTH="100%"></DIV |
68 | ><DIV |
69 | CLASS="chapter" |
70 | ><H1 |
71 | ><A |
72 | NAME="AEN40" |
73 | ></A |
74 | >Chapter 2. How to use the Linux Trace Toolkit Viewer's Reading Context</H1 |
75 | ><DIV |
76 | CLASS="sect1" |
77 | ><H1 |
78 | CLASS="sect1" |
79 | ><A |
80 | NAME="AEN42" |
81 | >2.1. Introduction</A |
82 | ></H1 |
83 | ><P |
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. |
86 | </P |
87 | ><P |
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. |
92 | </P |
93 | ></DIV |
94 | ></DIV |
95 | ><DIV |
96 | CLASS="NAVFOOTER" |
97 | ><HR |
98 | ALIGN="LEFT" |
99 | WIDTH="100%"><TABLE |
100 | SUMMARY="Footer navigation table" |
101 | WIDTH="100%" |
102 | BORDER="0" |
103 | CELLPADDING="0" |
104 | CELLSPACING="0" |
105 | ><TR |
106 | ><TD |
107 | WIDTH="33%" |
108 | ALIGN="left" |
109 | VALIGN="top" |
110 | ><A |
111 | HREF="x33.html" |
112 | ACCESSKEY="P" |
113 | >Prev</A |
114 | ></TD |
115 | ><TD |
116 | WIDTH="34%" |
117 | ALIGN="center" |
118 | VALIGN="top" |
119 | ><A |
120 | HREF="index.html" |
121 | ACCESSKEY="H" |
122 | >Home</A |
123 | ></TD |
124 | ><TD |
125 | WIDTH="33%" |
126 | ALIGN="right" |
127 | VALIGN="top" |
128 | ><A |
129 | HREF="x46.html" |
130 | ACCESSKEY="N" |
131 | >Next</A |
132 | ></TD |
133 | ></TR |
134 | ><TR |
135 | ><TD |
136 | WIDTH="33%" |
137 | ALIGN="left" |
138 | VALIGN="top" |
139 | >The hooks</TD |
140 | ><TD |
141 | WIDTH="34%" |
142 | ALIGN="center" |
143 | VALIGN="top" |
144 | > </TD |
145 | ><TD |
146 | WIDTH="33%" |
147 | ALIGN="right" |
148 | VALIGN="top" |
149 | >Why an event driven trace reader ?</TD |
150 | ></TR |
151 | ></TABLE |
152 | ></DIV |
153 | ></BODY |
154 | ></HTML |
155 | > |