1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >Why an event driven trace reader ?
</TITLE
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE=
"Linux Trace Toolkit Viewer Developer Guide"
11 HREF=
"index.html"><LINK
13 TITLE=
"How to use the Linux Trace Toolkit Viewer's Reading Context"
16 TITLE=
"How to use the Linux Trace Toolkit Viewer's Reading Context"
19 TITLE=
"Using the reading context"
20 HREF=
"x50.html"></HEAD
31 SUMMARY=
"Header navigation table"
40 >Linux Trace Toolkit Viewer Developer Guide
</TH
56 >Chapter
2. How to use the Linux Trace Toolkit Viewer's Reading Context
</TD
77 >2.2. Why an event driven trace reader ?
</A
80 > The complexity of synchronizing the tracesets is then hidden to the viewer. Some
81 future plans involve to be able to put many traces together in a trace set.
82 Before this becomes possible, the time of each trace must be synchronized in
83 some way. Some work is actually done to create a module that uses the network
84 traffic shared by different computers to synchronize the time of different
88 > In order to make each module integrate well with each other, we made the trace
89 reader a simple hook caller. For each event it reads, it just calls the hook
90 lists for this event. For each event, it calls the by_id specific hooks
91 registered for this event and also the
"main" hooks, registered for all events.
92 Note that the two hook lists are merged when called so the priority of the
93 hooks of each list is respected. For example, a hook of higher priority (
20) in
94 the main list will be called before a hook of lower priority (
40) from the
103 SUMMARY=
"Footer navigation table"
142 >How to use the Linux Trace Toolkit Viewer's Reading Context
</TD
156 >Using the reading context
</TD