Searched refs:histograms (Results 1 – 8 of 8) sorted by relevance
/linux/Documentation/userspace-api/media/v4l/ |
A D | pixfmt-meta-vsp1-hgo.rst | 21 histograms. 23 The HGO can compute histograms independently per channel, on the maximum of the 29 to compute three 64-bins histograms. RGB, YCbCr and HSV image formats are
|
/linux/tools/perf/util/ |
A D | annotate.h | 272 struct sym_hist *histograms; member 331 return ((void *)src->histograms) + (src->sizeof_sym_hist * idx); in annotated_source__histogram()
|
A D | annotate.c | 771 zfree(&src->histograms); in annotated_source__delete() 803 src->histograms = calloc(nr_hists, sizeof_sym_hist) ; in annotated_source__alloc_histograms() 804 return src->histograms ? 0 : -1; in annotated_source__alloc_histograms() 825 memset(notes->src->histograms, 0, in symbol__annotate_zero_histograms() 950 if (notes->src->histograms == NULL) { in symbol__hists()
|
/linux/Documentation/trace/ |
A D | histogram-design.rst | 10 histograms work and how the individual pieces map to the data 31 Basic histograms 34 First, basic histograms. Below is pretty much the simplest thing you 35 can do with histograms - create one with a single key on a single 79 which all histograms have, regardless of whether they define that 95 lock-free hash table used to implement histograms (see 883 Fields on other trace event's histograms can be used as well. In that 1615 histograms, and aliases, both described below through example tests 1618 Test of field variables on other histograms 1625 histogram can't be used, as existing histograms are immutable, a new [all …]
|
A D | boottime-trace.rst | 14 filter and actions, histograms, kprobe-events and synthetic-events,
|
A D | histogram.rst | 11 aggregate trace event data into histograms. For information on 1239 contents of all five histograms:: 1608 further combined histograms, thus providing a chain of related 1609 histograms, which is important for some applications. 1618 An example of a histogram that combines data from other histograms 1651 'combination' histograms mentioned previously. 1662 histograms as if it were any other event field; it isn't an actual 2400 The above created a synthetic event called "latency" and two histograms
|
/linux/tools/perf/Documentation/ |
A D | perf-report.txt | 368 address to build the histograms. To generate meaningful output, the 407 to build the histograms. To generate meaningful output, the perf.data
|
/linux/kernel/trace/ |
A D | Kconfig | 1034 running histograms.
|
Completed in 25 milliseconds