Lines Matching refs:events

13 Simplistically, tracepoints represent important events that can be
16 gathering and interpreting these events. Lacking any current Best Practises,
29 All possible events are visible from /sys/kernel/debug/tracing/events. Simply
32   $ find /sys/kernel/debug/tracing/events -type d
34 will give a fair indication of the number of events available.
39 Discovery and enumeration of all counters and events, including tracepoints,
40 are available with the perf tool. Getting a list of available events is a
58 See Documentation/trace/events.txt for a proper description on how events
59 can be enabled system-wide. A short example of enabling all events related
62   $ for i in `find /sys/kernel/debug/tracing/events -name "enable" | grep mm_`; do echo 1 > $i; done
92 By specifying the -a switch and analysing sleep, the system-wide events
113 Documentation/trace/ftrace.txt describes how to enable events on a per-thread
137 Documentation/trace/ftrace.txt covers in-depth how to filter events in
166 aggregation of discrete events, then a script would need to be developed.
168 Using --repeat, it is also possible to view how events are fluctuating over
186 When events are enabled the events that are triggering can be read from
192   o Deriving a higher-level event from a series of lower-level events.
193   o Calculating latencies between two events
200 Simplistically, the script just reads STDIN and counts up events but it
203   o Derive high-level events from many low-level events. If a number of pages
211     that if large numbers of events are coming from very short-lived
219 were generating events within the kernel. To begin this sort of analysis, the
256 According to this, the vast majority of events triggered on events
283 So, almost half of the events are occurring in a library. To get an idea which