Lines Matching +full:in +full:- +full:functions

7 In the example of the wip.dot monitor created on [1], it will look like::
50 Tracing callback functions
51 --------------------------
53 The first three functions are the starting point of the callback *handler
54 functions* for each of the three events from the wip model. The developer
74 In this case, the kernel event translates one to one with the automata
81 Initially, the *model* is placed in the initial state. However, the *system*
82 might or might not be in the initial state. The monitor cannot start
84 Otherwise, the monitor and the system could be out-of-sync.
92 "da_handle_start_event_$(MONITOR_NAME)(event)", in this case::
112 enable and disable functions
113 ----------------------------
115 dot2k automatically creates two special functions::
120 These functions are called when the monitor is enabled and disabled,
127 For the wip case, these functions were named::
132 But no change was required because: by default, these functions *attach* and
136 -----------------------
138 To complete the instrumentation, the *handler functions* need to be attached to a
143 adds "rv_attach_trace_probe()" function call for each model event in the enable phase, as
165 [1] The wip model is presented in::
169 The wip monitor is presented in::