Searched refs:total_lost (Results 1 – 7 of 7) sorted by relevance
14 * total_lost tells exactly how many events the kernel in fact lost, i.e. it is40 u64 total_lost; member
1500 evlist->stats.total_lost += event->lost.lost; in machines__deliver_event()
154 hm->total_lost++; in xfs_healthmon_bump_lost()1066 hm->total_lost); in xfs_healthmon_show_fdinfo()
7736 unsigned long total_lost = 0; in test_ringbuffer() local7765 total_lost += lost; in test_ringbuffer()7785 pr_info(" lost events: %ld\n", total_lost); in test_ringbuffer()7786 pr_info(" total events: %ld\n", total_lost + total_read); in test_ringbuffer()7789 if (total_lost) { in test_ringbuffer()7797 if (RB_WARN_ON(buffer, total_lost + total_read != total_events)) in test_ringbuffer()
863 evsel->evlist->stats.total_lost += event->lost.lost; in perf_top__process_lost()
1830 kwork->nr_lost_events = session->evlist->stats.total_lost; in perf_kwork__read_events()
1955 sched->nr_lost_events = session->evlist->stats.total_lost; in perf_sched__read_events()3386 sched->nr_lost_events = evlist->stats.total_lost; in perf_sched__timehist()