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
1133 into the histogram. In order to avoid having to set everything up
1134 again, we can just clear the histogram first::
1177 disables both the histogram and the event log, and what you end up
1243 # event histogram
1270 # event histogram
1307 # event histogram
1319 # event histogram
1343 # event histogram
1355 histogram data. This capability is mostly useful for combining the
1359 field in the shared 'foo' histogram data::
1366 You can see that they're updating common histogram data by reading
1372 # event histogram
1424 # event histogram
1477 And here's an example that shows how to combine histogram data from
1493 # event histogram
1606 one or more other events and create a histogram using that data. Data
1607 from an inter-event histogram can in turn become the source for
1618 An example of a histogram that combines data from other histograms
1619 into a useful chain would be a 'wakeupswitch latency' histogram that
1620 combines a 'wakeup latency' histogram and a 'switch latency'
1621 histogram.
1625 continually updated sums associated with that key. A histogram
1631 events to be referenced and combined into a multi-event histogram
1637 requires the introduction of support for histogram 'variables'.
1643 - A histogram consisting of inter-event quantities isn't logically a
1644 histogram on either event (so having the 'hist' file for either
1645 event host the histogram output doesn't really make sense). To
1646 address the idea that the histogram is associated with a
1653 - A set of 'actions' can be associated with histogram entries -
1669 histogram, the trace buffer is automatically switched over to using
1684 event that has a matching key - if a variable is saved for a histogram
1702 creates a variable named 'ts0' for a histogram entry with the key
1716 will also be summed as a normal histogram value would (though for a
1745 thing but without the values being summed in the histogram::
1848 A histogram can now be defined for the new synthetic event::
1855 Like any other event, once a histogram is enabled for the event, the
1860 # event histogram
1908 # event histogram
1939 conditionally) whenever a histogram entry is added or updated.
1941 When a histogram entry is added or updated, a hist trigger 'handler'
1987 and the histogram entry would be added or updated. It causes the
2021 multiple histogram keys are used, they all must match in the specified
2055 Creating and displaying a histogram based on those events is now
2063 wakeup_new_test synthetic events which should result in histogram
2070 produce a 'wakeup_latency' histogram.
2094 We also need to create a histogram on the wakeup_latency synthetic
2109 whenever the value of 'var' associated with a histogram entry
2116 reference. When the histogram is displayed, additional fields
2138 When the histogram is displayed, the max value and the saved
2162 whenever the value of 'var' associated with a histogram entry
2171 the histogram. The key of the specific trace event that caused
2175 to locate the corresponding bucket in the histogram for even more
2200 When the histogram is displayed, for each bucket the max value
2271 whenever the value of 'var' associated with a histogram entry
2278 histogram is displayed, additional fields displaying the saved
2284 whenever the value of 'var' associated with a histogram entry
2297 histogram for even more detail.
2315 When the histogram is displayed, for each bucket the tracked value
2392 We can make a histogram from this::
2404 parameter. Finally, a histogram is added to the latency synthetic event to
2422 Then we can see the histogram created by this with::
2425 # event histogram
2722 interesting, we can mix the histogram between events that happened in the
2738 # event histogram
2908 woken up, but it does show us a nice histogram of how long it took from