Lines Matching refs:events
504 observes these interferences' entry events. When a noise happens
543 events can be used to trace the source of interference from NMI,
562 bool "Trace process context switches and events"
576 Basic tracer to catch the syscall entry and exit events.
679 This traces the events of likely and unlikely condition
683 events into a running trace buffer to see when and where the
684 events happened, as well as their results.
716 bool "Enable fprobe-based dynamic events"
722 This allows user to add tracing events on the function entry and
723 exit via ftrace interface. The syntax is same as the kprobe events
724 and the kprobe events on function entry and exit will be
725 transparently converted to this fprobe events.
731 bool "Support BTF function arguments for probe events"
742 bool "Enable kprobes-based dynamic events"
748 This allows the user to add tracing events (similar to tracepoints)
752 Those events can be inserted wherever kprobes can probe, and record
759 bool "Do NOT protect notrace function from kprobe events"
765 using kprobe events.
768 functions are protected from kprobe-events to prevent an infinite
773 events on ftrace functions for debugging ftrace by itself.
779 bool "Enable uprobes-based dynamic events"
789 This allows the user to add tracing events on top of userspace
790 dynamic events (similar to tracepoints) on the fly via the trace
791 events interface. Those events can be inserted wherever uprobes
797 bool "Enable event-based dynamic events"
804 Eprobes are dynamic events that can be placed on other existing
805 events. It can be used to limit what fields are recorded in
817 tracepoint events.
870 bool "Synthetic trace events"
875 Synthetic events are user-defined trace events that can be
876 used to combine data from other trace events or in fact any
877 data source. Synthetic events can be generated indirectly
881 See Documentation/trace/events.rst or
887 bool "User trace events"
891 User trace events are user-defined trace events that
893 events are generated by writing to a tracefs file. User
894 processes can determine if their tracing events should be
970 10 seconds. Each interval it will print out the number of events
979 bool "Show eval mappings for trace events"
982 The "print fmt" of the trace events will show the enum/sizeof names
1084 bool "Run selftest on trace events"
1088 This option performs a test on all trace events in the system.
1090 will trigger events (not necessarily the event it enables)
1091 This may take some time run as there are a lot of events.
1094 bool "Run selftest on syscall events"
1103 events
1125 a thread per cpu. Each thread will write various size events
1148 events on a sub buffer matches the current time stamp.
1155 NOTE: This adds significant overhead to recording of events,
1200 for the generated sample events.
1212 for the generated kprobe events.