| IntervalZero.com | Support | Give Feedback |
|
|
|
There are several events that RTX Time View can monitor. You can use these events in two ways: as triggers or as items that RTX Time View collects in its log file.
When specifying a trigger, you specify a single event that acts as the trigger. If you are using the RTX Time View command line, you specify the trigger using its unsigned integer value ID. If you are using the RTX Time View user interface, you choose the event from a set of menus.
When specifying which events to collect in the log file, you specify collections of events called event groups. All of the events in a specified group are logged as they occur. If you are using the RTX Time View command line, you specify a group by its group number. If you are using the RTX Time View user interface, you specify groups using filters.
Tables of events that RTX Time View can monitor are available here. Because they would be prohibitively long, not all of the events listed appear in the menus; events that do appear are marked in italics. All of the groups listed in the event ID tables are available from both the command line and user interface versions of RTX Time View.
|
NOTE: All events monitored and logged by RTX Time View are in RTSS context only. Traced items are written to the RTX Time View data file by the thread that encountered the activity. This will primarily occur immediately after the event occurs, but could be delayed when a priority inversion protocol is active. When a thread has its priority raised to allow it to complete use of a mutex needed by a higher priority thread, the higher priority thread will preempt as soon as the priority is lowered during the release of the mutex in the first thread. In this case, the demoted thread will not get a chance to call the trace function that will log the priority demotion until it has another opportunity to run. As a result, RTX Time View data will show the priority demotion occurring later than it actually did. |