Lines Matching full:events

2 Notes on Analysing Behaviour Using Events and Tracepoints
13 Simplistically, tracepoints represent important events that can be
16 gathering and interpreting these events. Lacking any current Best Practises,
23 2. Listing Available Events
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
52 3. Enabling Events
58 See Documentation/trace/events.rst 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
93 By specifying the -a switch and analysing sleep, the system-wide events
115 Documentation/trace/ftrace.rst describes how to enable events on a per-thread
121 Events can be activated and tracked for the duration of a process on a local
140 Documentation/trace/ftrace.rst covers in-depth how to filter events in
170 aggregation of discrete events, then a script would need to be developed.
172 Using --repeat, it is also possible to view how events are fluctuating over
191 When events are enabled the events that are triggering can be read from
197   - Deriving a higher-level event from a series of lower-level events.
198   - Calculating latencies between two events
205 Simplistically, the script just reads STDIN and counts up events but it
208   - Derive high-level events from many low-level events. If a number of pages
216     that if large numbers of events are coming from very short-lived
224 were generating events within the kernel. To begin this sort of analysis, the
263 According to this, the vast majority of events triggered on events
292 So, almost half of the events are occurring in a library. To get an idea which