Lines Matching refs:a
16 A tracepoint placed in code provides a hook to call a function (probe)
17 that you can provide at runtime. A tracepoint can be "on" (a probe is
18 connected to it) or "off" (no probe is attached). When a tracepoint is
19 "off" it has no effect, except for adding a tiny time penalty
20 (checking a condition for a branch) and space penalty (adding a few
22 and adds a data structure in a separate section). When a tracepoint
30 which prototypes are described in a tracepoint declaration placed in a
40 - A tracepoint definition, placed in a header file.
93 Connecting a function (probe) to a tracepoint is done by providing a
95 register_trace_subsys_eventname(). Removing a probe is done through
104 same tracepoint, but a single definition must be made of a given
112 The naming scheme "subsys_event" is suggested here as a convention
121 If you need to do a bit of work for a tracepoint parameter, and
135 All trace_<tracepoint>() calls have a matching trace_<tracepoint>_enabled()
148 for a series of articles with more details.
150 If you require calling a tracepoint from a header file, it is not
152 function call, as tracepoints in header files can have side effects if a
153 header is included from a file that has CREATE_TRACE_POINTS set, as
158 In a C file::