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
1132 into the histogram. In order to avoid having to set everything up
1133 again, we can just clear the histogram first::
1176 disables both the histogram and the event log, and what you end up
1242 # event histogram
1269 # event histogram
1306 # event histogram
1318 # event histogram
1342 # event histogram
1354 histogram data. This capability is mostly useful for combining the
1358 field in the shared 'foo' histogram data::
1365 You can see that they're updating common histogram data by reading
1371 # event histogram
1423 # event histogram
1476 And here's an example that shows how to combine histogram data from
1492 # event histogram
1605 one or more other events and create a histogram using that data. Data
1606 from an inter-event histogram can in turn become the source for
1617 An example of a histogram that combines data from other histograms
1618 into a useful chain would be a 'wakeupswitch latency' histogram that
1619 combines a 'wakeup latency' histogram and a 'switch latency'
1620 histogram.
1624 continually updated sums associated with that key. A histogram
1630 events to be referenced and combined into a multi-event histogram
1636 requires the introduction of support for histogram 'variables'.
1642 - A histogram consisting of inter-event quantities isn't logically a
1643 histogram on either event (so having the 'hist' file for either
1644 event host the histogram output doesn't really make sense). To
1645 address the idea that the histogram is associated with a
1652 - A set of 'actions' can be associated with histogram entries -
1668 histogram, the trace buffer is automatically switched over to using
1683 event that has a matching key - if a variable is saved for a histogram
1701 creates a variable named 'ts0' for a histogram entry with the key
1715 will also be summed as a normal histogram value would (though for a
1744 thing but without the values being summed in the histogram::
1826 A histogram can now be defined for the new synthetic event::
1837 Like any other event, once a histogram is enabled for the event, the
1844 conditionally) whenever a histogram entry is added or updated.
1846 When a histogram entry is added or updated, a hist trigger 'handler'
1892 and the histogram entry would be added or updated. It causes the
1926 multiple histogram keys are used, they all must match in the specified
1960 Creating and displaying a histogram based on those events is now
1968 wakeup_new_test synthetic events which should result in histogram
1975 produce a 'wakeup_latency' histogram.
1999 We also need to create a histogram on the wakeup_latency synthetic
2014 whenever the value of 'var' associated with a histogram entry
2021 reference. When the histogram is displayed, additional fields
2043 When the histogram is displayed, the max value and the saved
2067 whenever the value of 'var' associated with a histogram entry
2076 the histogram. The key of the specific trace event that caused
2080 to locate the corresponding bucket in the histogram for even more
2105 When the histogram is displayed, for each bucket the max value
2176 whenever the value of 'var' associated with a histogram entry
2183 histogram is displayed, additional fields displaying the saved
2189 whenever the value of 'var' associated with a histogram entry
2202 histogram for even more detail.
2220 When the histogram is displayed, for each bucket the tracked value
2297 We can make a histogram from this::
2309 parameter. Finally, a histogram is added to the latency synthetic event to
2327 Then we can see the histogram created by this with::
2330 # event histogram
2627 interesting, we can mix the histogram between events that happened in the
2643 # event histogram
2813 woken up, but it does show us a nice histogram of how long it took from