Lines Matching refs:tracepoint

14 A tracepoint placed in code provides a hook to call a function (probe)
15 that you can provide at runtime. A tracepoint can be "on" (a probe is
16 connected to it) or "off" (no probe is attached). When a tracepoint is
20 and adds a data structure in a separate section).  When a tracepoint
21 is "on", the function you provide is called each time the tracepoint
24 the tracepoint site).
28 which prototypes are described in a tracepoint declaration placed in a
38 - A tracepoint definition, placed in a header file.
39 - The tracepoint statement, in C code.
41 In order to use tracepoints, you should include linux/tracepoint.h.
51 #include <linux/tracepoint.h>
82   function called by this tracepoint.
90 Connecting a function (probe) to a tracepoint is done by providing a
91 probe (function to call) for the specific tracepoint through
100 The tracepoint mechanism supports inserting multiple instances of the
101 same tracepoint, but a single definition must be made of a given
102 tracepoint name over all the kernel to make sure no type conflict will
114 If the tracepoint has to be used in kernel modules, an
118 If you need to do a bit of work for a tracepoint parameter, and
119 that work is only used for the tracepoint, that work can be encapsulated
132 All trace_<tracepoint>() calls have a matching trace_<tracepoint>_enabled()
133 function defined that returns true if the tracepoint is enabled and
134 false otherwise. The trace_<tracepoint>() should always be within the
135 block of the if (trace_<tracepoint>_enabled()) to prevent races between
136 the tracepoint being enabled and the check being seen.
138 The advantage of using the trace_<tracepoint>_enabled() is that it uses
139 the static_key of the tracepoint to allow the if statement to be implemented