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
1144   into the histogram.  In order to avoid having to set everything up
1145   again, we can just clear the histogram first::
1188   disables both the histogram and the event log, and what you end up
1254     # event histogram
1281     # event histogram
1318     # event histogram
1330     # event histogram
1354     # event histogram
1366   histogram data.  This capability is mostly useful for combining the
1370   field in the shared 'foo' histogram data::
1377   You can see that they're updating common histogram data by reading
1383     # event histogram
1435     # event histogram
1488   And here's an example that shows how to combine histogram data from
1504     # event histogram
1617 one or more other events and create a histogram using that data.  Data
1618 from an inter-event histogram can in turn become the source for
1629 An example of a histogram that combines data from other histograms
1630 into a useful chain would be a 'wakeupswitch latency' histogram that
1631 combines a 'wakeup latency' histogram and a 'switch latency'
1632 histogram.
1636 continually updated sums associated with that key.  A histogram
1642 events to be referenced and combined into a multi-event histogram
1648     requires the introduction of support for histogram 'variables'.
1654   - A histogram consisting of inter-event quantities isn't logically a
1655     histogram on either event (so having the 'hist' file for either
1656     event host the histogram output doesn't really make sense).  To
1657     address the idea that the histogram is associated with a
1664   - A set of 'actions' can be associated with histogram entries -
1680 histogram, the trace buffer is automatically switched over to using
1695 event that has a matching key - if a variable is saved for a histogram
1713 creates a variable named 'ts0' for a histogram entry with the key
1727 will also be summed as a normal histogram value would (though for a
1756 thing but without the values being summed in the histogram::
1820 A histogram can now be defined for the new synthetic event::
1831 Like any other event, once a histogram is enabled for the event, the
1838 histogram entry is added or updated.
1854     histogram entry would be added or updated.  It causes the named
1899     Creating and displaying a histogram based on those events is now
1907     wakeup_new_test synthetic events which should result in histogram
1914     produce a 'wakeup_latency' histogram.
1938     We also need to create a histogram on the wakeup_latency synthetic
1953     whenever the value of 'var' associated with a histogram entry
1960     reference.  When the histogram is displayed, additional fields
1982     When the histogram is displayed, the max value and the saved
2028 We can make a histogram from this::
2040 parameter. Finally, a histogram is added to the latency synthetic event to
2058 Then we can see the histogram created by this with::
2061  # event histogram
2358 interesting, we can mix the histogram between events that happened in the
2374  # event histogram
2544 woken up, but it does show us a nice histogram of how long it took from