📄 x-glossary.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> Glossary </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-timestamp.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><img border="0" src="icons/blank.gif"><a href="x-timestamp6.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="wvGuideIX.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h1 class="H1num" align="right"><i><a name="93398">H</a></i></h1></font><font face="Helvetica, sans-serif" class="sans"><h1 class="H1name" align="right"><i><a name="93400"> Glossary</a></i></h1></font><dl class="margin"></dl><h4 class="Subtitle" align="right"><font face="Helvetica, sans-serif" size="-1" class="sans"><i></i></font></h4><p class="BodyLeft"><a name="92051"> </a></p><dl class="margin"><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="92622">additional instrumentation event-logging level (AIL level) </a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="92624"> </a>This WindView event-logging level works a little differently from the CSE level or the TST level. When this level is selected, WindView gathers all the information included in the other two levels, as well as additional information about particular objects that you have instrumented. Instrumenting an object causes WindView to log all operations on the object, including creation, gives or sends, takes or receives, and deletion. Events are generated for these operations whether or not they result in task state transitions, context switches, or neither; for example, a <b class="routine"><i class="routine">semTake</i></b><b>( )</b> of a semaphore that is available is logged at this level.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="92646">AIL level</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="92648"> </a>See <i class="textVariable">additional instrumentation event-logging level</i>. </p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89861">analysis pack</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89862"> </a>Analysis packs are preprogrammed functions which calculate analog information for event logs. For example, there is an analysis pack to measure and display how much system memory is allocated at a given moment. </p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="92127">application code</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="92129"> </a>Application code is any user-supplied code in the real-time system.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="92132">auxiliary clock</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89873"> </a>Many target boards include an auxiliary clock which, when enabled, runs continually and emits a periodic interrupt. In a VxWorks application, the application code can use the auxiliary clock unless it is being used by the timestamp driver. See also system clock.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89879">binary semaphore</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89881"> </a>A binary semaphore may be viewed as a cell in memory that can be full or empty. A binary semaphore is useful for both mutual exclusion and synchronization.</p><dd><p class="Body"><a name="89883"> </a>For mutual exclusion, you create a binary semaphore with an initial state of full to "guard" a resource. When a task needs to use the resource, it attempts to take the semaphore; when the task is finished with the resource, it gives the semaphore. Other tasks cannot use the resource until the semaphore is again available. (Note that VxWorks also offers another type of semaphore that may be more appropriate for some applications: a specialized mutual exclusion semaphore.)</p><dd><p class="Body"><a name="89888"> </a>For synchronization, the binary semaphore is created with an initial state of empty. A task waits to synchronize with another task or an ISR by attempting to take the semaphore. When the other task or ISR gives the semaphore, the original task is again able to execute. Thus, the original task and the "giving" task or ISR are synchronized. See also counting semaphore.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89893">blocked</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89895"> </a>See pended state.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89898">Board Support Package (BSP)</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89900"> </a>The BSP provides the interface between VxWorks and a specific target board. This includes hardware initialization, interrupt handling, chip device drivers, hardware clock and timer management, mapping of local and bus memory spaces, and memory sizing.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89903">breakpoint</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89904"> </a>A breakpoint is a location in a program at which the debugger will stop the application. This allows you to examine the stack, values of particular variables, and other items of interest. See also eventpoint.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89908">chained trigger</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89910"> </a>A chained trigger is enabled by another trigger's firing.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89912">collecting event data</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89914"> </a>See event collection.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89917">context</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89921"> </a>See context switch, current context, task context.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89924">Context Attributes dialog box</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89927"> </a>The <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Context Attributes</font></b> dialog box displays a list of all tasks in the real-time system, along with their task IDs and their associated CPU number if the log includes multiple CPUs. You can also use this dialog box to select which tasks are displayed in the view graph. </p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89932">context state</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89934"> </a>See task state.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89937">Context State Summary window</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89938"> </a>The <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Context State Summary</font></b> window shows summary statistics about a selected task during a specified interval. These statistics include a count, minimum, maximum, average, and total time the task spent in each state during the interval. Open this window by selecting <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Information</font></b> from the task pop-up menu. </p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89943">Context State Information window</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89944"> </a>The <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Context State Information</font></b> window displays information about the context that generated a selected event. Open this window by selecting <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Context State </font></b>from the event pop-up menu. </p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89950">context switch</a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89951"> </a>A context switch is an operation performed by a multitasking operating system in which the current thread of execution is switched for another. Examples of this are one task preempting another, a task delaying itself or pending on a resource (making the processor available for another thread of execution), or a task being interrupted by an ISR. See also current context, task context.</p></dl><dd><font face="Helvetica, sans-serif" size="-1" class="sans"><h5 class="HU"><i><a name="89960">context switch event-logging level (CSE level) </a></i></h5></font><dl class="margin"><dd><p class="Body"><a name="89962"> </a>This WindView event-logging level shows the current context and where it is switched. The current context is shown as a solid, horizontal line (<img class="figure" border="0" src="images/x-glossary0.gif">). When a context switch occurs, a dotted, vertical line connects the previous context's line to the current context's line.</p><dd><p class="Body"><a name="89967"> </a>The following events are also shown at CSE level:</p></dl><dl class="margin"><p class="listspace"><ul class="Dash" type="circle"><li><a name="89972"> </a>Every entry and exit of an ISR, shown as up and down triangular arrows (<img class="figure" border="0" src="images/x-glossary1.gif"> and <img class="figure" border="0" src="images/x-glossary2.gif">). (Not displayed by default.)</li></ul></p><p class="listspace"><ul class="Dash" type="circle"><li><a name="89977"> </a>Every program error that results in an exception that is handled by a default exception handler, shown as a bomb (<img class="figure" border="0" src="images/x-glossary3.gif">).</li></ul></p><p class="listspace"><ul class="Dash" type="circle"><li><a name="89982"> </a>Periods of task preemption locking, that is, intervals bounded by calls to the routines <b class="routine"><i class="routine">taskLock</i></b><b>( )</b> and <b class="routine"><i class="routine">taskUnlock</i></b><b>( )</b>, shown as a line of dotted squares <b>( )</b></li></ul>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -