📄 x-evtdic2.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> Event Dictionary </title></head><body bgcolor="FFFFFF"><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="x-evtdic.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="x-evtdic.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="x-evtdic1.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="x-evtdic3.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h3 class="H2"><i><a name="108692">B.2 Using the Event Dictionary</a></i></h3></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="108693"> </a>This section provides tips for using the event dictionary.</p><dd><p class="Body"><a name="108697"> </a>Suppose you see the icon <img class="figure" border="0" src="images/x-evtdic0.gif"> while viewing an event log in WindView.</p><dd><p class="Body"><a name="108709"> </a>You can click on the icon to see the name of the event in the Tornado status line (at the bottom of the Tornado window; see <a href="c-display1.html#84391">Figure 5-1</a>). As an alternative, you can locate the icon in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Legend</font></b> window under <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">WindView Help</font></b> in the main <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Help</font></b> menu. In either case, you can see that this is the <b class="eventType">taskResume</b> event icon. Using <a href="x-evtdic3.html#108821"><i class="title">B.3 Event Dictionary</i></a>, you can look up the information on what can cause a <b class="eventType">taskResume</b> event, what effect on the task state it may have, and what information is collected for a <b class="eventType">taskResume</b> event, as shown in <a href="x-evtdic2.html#127554">Figure 8-12</a>. <div class="frame"><h4 class="EntityTitle"><a name="127506"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure B-1: Anatomy of an Event-Dictionary Entry</font></a></h4><dl class="margin"><div class="Anchor"><a name="127508"> </a><img class="figure" border="0" src="images/x-evtdica2.gif"></div></dl></div></p><dd><p class="Body"><a name="108753"> </a>Most of the elements that are called out on the sample page are self-explanatory, with the possible exception of the table of information collected.</p><dd><p class="Body"><a name="108755"> </a>The table of information collected describes what information is logged for a particular event, and for which event-logging level that information is logged (indicated by X's in the appropriate columns):</p></dl><dl class="margin"><ul class="BulletSingle" type="disc"><li><a name="110805"> </a>Context switch event-logging level (CSE level) </li></ul><ul class="BulletSingle" type="disc"><li><a name="110806"> </a>Task state transition event-logging level (TST level) </li></ul><ul class="BulletSingle" type="disc"><li><a name="110811"> </a>Additional instrumentation event-logging level (AIL level) </li></ul></dl><dl class="margin"><dd><p class="Body"><a name="113074"> </a>In the sample event dictionary page above, you can see that the <i class="textVariable">context</i> (the task, ISR, or idle loop in which the event occurred), <i class="textVariable">eventName</i>, and <i class="textVariable">taskId</i> event parameters are logged when event logging is started at TST level.<sup><a href="#foot"><b class="FootnoteMarker">1</b></a></sup></p><dd><p class="Body"><a name="113076"> </a>At this level, <i class="textVariable">timeStamp</i> is not actually logged. Instead, it is calculated based on the next exit from the kernel; see <a href="c-collect2.html#84325"><i class="title">Task State Transition Logging Level (TST Level)</i></a> for information.</p><dd><p class="Body"><a name="108768"> </a>These same event parameters are logged when event logging is started at AIL level, but in addition, the <i class="textVariable">priority</i> event parameter is logged, and the <i class="textVariable">timeStamp</i> is logged rather than calculated.</p><dd><p class="Body"><a name="108769"> </a>For example, if event logging is at TST level, when you inspect the <b class="eventType">taskResume</b> icon with the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Show Event</font></b> dialog box, a display like <a href="x-evtdic2.html#127554">Figure 8-12</a> appears (note that although the <b class="symbol_lc">priority</b> label is present, its value is unknown, indicated by "<b class="symbol_lc">?</b>"). <div class="frame"><h4 class="EntityTitle"><a name="127554"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 8-12: Inspecting taskResume Event</font></a></h4><dl class="margin"><div class="Anchor"><a name="127556"> </a><img class="figure" border="0" src="images/x-evtdica1.gif"></div></dl></div></p><dd><p class="Body"><a name="108790"> </a>This provides the following information:</p><dl class="margin"><dd><p class="ListV"><a name="108791"> </a>[1] At calculated time 0.0336625 seconds,</p><dd><p class="ListV"><a name="108795"> </a>[2] within the context of <b class="task">tWdbTask</b> (context ID 0x3fe974<sup><a href="#foot"><b class="FootnoteMarker">2</b></a></sup>), a <b class="eventType">taskResume</b> event occurred.</p><dd><p class="ListV"><a name="108796"> </a>[3] The priority of the resumed task is not known for this -logging level.</p><dd><p class="ListV"><a name="108797"> </a>[4] The task being resumed has an ID of 0x33b6a7c, displayed here both as <b class="symbol_lc">taskId</b> in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Parameters</font></b> area, and in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Object</font></b> field (because this task is the object affected by the event).</p></dl><dd><p class="Body"><a name="126323"> </a>However, if event logging is at AIL level, and task <b class="task">tWdbTask</b> is instrumented, the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Time</font></b> field shows an exact timestamp, and the <b class="symbol_lc">priority</b> property displays the task priority for the affected task.</p></dl></dl><dl class="margin"><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/note.gif"></td><td><hr><div class="CalloutCell"><a name="126328"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE: </font></b></a>Remember that another important distinction between TST level logging and AIL level logging is that for the former, events are logged and displayed <i class="emphasis">only</i> if they result in a task state transition. At AIL level, all events are logged and displayed for all objects that are instrumented.</div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout><dd><p class="table" callout><table border="0" cellpadding="0" cellspacing="0"><tr valign="top"><td valign="top" width="40"><br><img border="0" alt="*" src="icons/note.gif"></td><td><hr><div class="CalloutCell"><a name="126349"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE: </font></b></a>If an invalid parameter is passed to a routine, an event icon may not appear, depending on whether the error is detected before or after event logging occurs. In particular, if an invalid object ID is passed to a routine, the event icon does <i class="emphasis">not</i> appear. </div></td></tr><tr valign="top"><td></td><td><hr></td></tr><tr valign="middle"><td colspan="20"></td></tr></table></p callout></dl><a name="foot"><hr></a><p class="FootnoteNumberMarker">1: <span class="Footnote"><a name="119256"> </a> For information on starting event logging, see <a href="c-collect4.html#84511"><i class="title">3.4 Starting and Stopping Data Collection</i></a>.</span><p class="FootnoteNumberMarker">2: <span class="Footnote"><a name="119271"> </a>For a task, the context ID is the task ID. For an ISR context, the ID is the hex value of the interrupt level; for example, an ISR that runs at INT 3 has an ID of 0x3. For the idle loop context, the ID is 0xffffffff.</span><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="x-evtdic.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="x-evtdic.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="x-evtdic1.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="x-evtdic3.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p></body></html><!---by WRS Documentation (), Wind River Systems, Inc. conversion tool: Quadralay WebWorks Publisher 4.0.11 template: CSS Template, Jan 1998 - Jefro --->⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -