Searched refs:total_lost (Results 1 – 8 of 8) sorted by relevance
14 * total_lost tells exactly how many events the kernel in fact lost, i.e. it is40 u64 total_lost; member
2065 evlist__stats(evlist)->total_lost += event->lost.lost; in __perf_session__process_pipe_events()
64 unsigned long long total_lost; member
165 hm->total_lost++; in xfs_healthmon_bump_lost()1083 hm->total_lost); in xfs_healthmon_show_fdinfo()
8370 unsigned long total_lost = 0; in test_ringbuffer() 8399 total_lost += lost; in test_ringbuffer() 8419 pr_info(" lost events: %ld\n", total_lost); in test_ringbuffer() 8420 pr_info(" total events: %ld\n", total_lost + total_read); in test_ringbuffer() 8423 if (total_lost) { in test_ringbuffer() 8431 if (RB_WARN_ON(buffer, total_lost + total_read != total_events)) in test_ringbuffer() 8372 unsigned long total_lost = 0; test_ringbuffer() local
862 evlist__stats(evsel->evlist)->total_lost += event->lost.lost; in perf_top__process_lost()
1868 kwork->nr_lost_events = evlist__stats(session->evlist)->total_lost; in sig_handler()
2225 sched->nr_lost_events = evlist__stats(session->evlist)->total_lost; in timehist_print_sample() 3678 sched->nr_lost_events = evlist__stats(evlist)->total_lost; in perf_sched__replay()