Lines Matching refs:histogram
18 A histogram trigger command is an event trigger command that
51 its histogram data will be shared with other triggers of the same
144 raw hitcount in the histogram. This option requires at least one
1142 into the histogram. In order to avoid having to set everything up
1143 again, we can just clear the histogram first::
1186 disables both the histogram and the event log, and what you end up
1252 # event histogram
1279 # event histogram
1316 # event histogram
1328 # event histogram
1352 # event histogram
1364 histogram data. This capability is mostly useful for combining the
1368 field in the shared 'foo' histogram data::
1375 You can see that they're updating common histogram data by reading
1381 # event histogram
1433 # event histogram
1486 And here's an example that shows how to combine histogram data from
1502 # event histogram
1615 one or more other events and create a histogram using that data. Data
1616 from an inter-event histogram can in turn become the source for
1627 An example of a histogram that combines data from other histograms
1628 into a useful chain would be a 'wakeupswitch latency' histogram that
1629 combines a 'wakeup latency' histogram and a 'switch latency'
1630 histogram.
1634 continually updated sums associated with that key. A histogram
1640 events to be referenced and combined into a multi-event histogram
1646 requires the introduction of support for histogram 'variables'.
1652 - A histogram consisting of inter-event quantities isn't logically a
1653 histogram on either event (so having the 'hist' file for either
1654 event host the histogram output doesn't really make sense). To
1655 address the idea that the histogram is associated with a
1662 - A set of 'actions' can be associated with histogram entries -
1678 histogram, the trace buffer is automatically switched over to using
1693 event that has a matching key - if a variable is saved for a histogram
1711 creates a variable named 'ts0' for a histogram entry with the key
1725 will also be summed as a normal histogram value would (though for a
1754 thing but without the values being summed in the histogram::
1859 A histogram can now be defined for the new synthetic event::
1866 Like any other event, once a histogram is enabled for the event, the
1871 # event histogram
1919 # event histogram
1994 histogram::
1999 # event histogram
2101 conditionally) whenever a histogram entry is added or updated.
2103 When a histogram entry is added or updated, a hist trigger 'handler'
2149 and the histogram entry would be added or updated. It causes the
2183 multiple histogram keys are used, they all must match in the specified
2217 Creating and displaying a histogram based on those events is now
2225 wakeup_new_test synthetic events which should result in histogram
2232 produce a 'wakeup_latency' histogram.
2256 We also need to create a histogram on the wakeup_latency synthetic
2271 whenever the value of 'var' associated with a histogram entry
2278 reference. When the histogram is displayed, additional fields
2300 When the histogram is displayed, the max value and the saved
2324 whenever the value of 'var' associated with a histogram entry
2333 the histogram. The key of the specific trace event that caused
2337 to locate the corresponding bucket in the histogram for even more
2362 When the histogram is displayed, for each bucket the max value
2433 whenever the value of 'var' associated with a histogram entry
2440 histogram is displayed, additional fields displaying the saved
2446 whenever the value of 'var' associated with a histogram entry
2459 histogram for even more detail.
2477 When the histogram is displayed, for each bucket the tracked value
2554 We can make a histogram from this::
2566 parameter. Finally, a histogram is added to the latency synthetic event to
2584 Then we can see the histogram created by this with::
2587 # event histogram
2884 interesting, we can mix the histogram between events that happened in the
2900 # event histogram
3070 woken up, but it does show us a nice histogram of how long it took from