Lines Matching full:samples

21     2.3.3       Writing samples into buffer
22     2.3.4       Reading samples from buffer
144 threads in the system.   The perf samples are exclusively collected for
259 The option ``-C`` is used to collect samples on the list of CPUs, for
276 ``––per–thread`` are specified together, the samples are recorded only when
319 By using option ``–a`` or ``––all–cpus``, perf collects samples on all CPUs
332 are monitored during the running state and the samples are recorded into
391 In the Linux kernel, the PMU events can produce samples which are stored
393 samples by reading out data from the ring buffer and finally saves the
402 kernel wakes up the perf process to read samples from the ring buffer.
407                        / | Read samples
414              | Wake up tasks    | Store samples
424 multiple events might share the same ring buffer for recording samples,
430 one by one, if it finds any ring buffer containing samples it will read
431 out the samples for statistics or saving into the data file.  Given the
441 backward.  The forward writing saves samples from the beginning of the ring
495 2.3.3 Writing samples into buffer
514 2.3.4 Reading samples from buffer
558 writing the pointer ``data_tail``, perf tool first consumes samples and then
568 pointer is fetched before reading samples.
602 samples and every event format complies with the definition in the
608 regular profile samples that write to the regular ring buffer cause an
609 interrupt.  Tracing execution requires a high number of samples and
640 the system wide mode, however, the default mode records samples only for
648 mode; if there are any activities on one CPU, the AUX event samples and