[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240830232910.1839548-4-namhyung@kernel.org>
Date: Fri, 30 Aug 2024 16:29:09 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>
Cc: Kan Liang <kan.liang@...ux.intel.com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Stephane Eranian <eranian@...gle.com>,
Ravi Bangoria <ravi.bangoria@....com>
Subject: [RFC/PATCH 3/4] perf/core: Account dropped samples from BPF
Like in the software events, the BPF overflow handler can drop samples
by returning 0. Let's count the dropped samples here too.
Signed-off-by: Namhyung Kim <namhyung@...nel.org>
---
kernel/events/core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 8250e76f6335..ba1f6b51ea26 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -9808,8 +9808,10 @@ static int __perf_event_overflow(struct perf_event *event,
ret = __perf_event_account_interrupt(event, throttle);
- if (event->prog && !bpf_overflow_handler(event, data, regs))
+ if (event->prog && !bpf_overflow_handler(event, data, regs)) {
+ atomic64_inc(&event->dropped_samples);
return ret;
+ }
/*
* XXX event_limit might not quite work as expected on inherited
--
2.46.0.469.g59c65b2a67-goog
Powered by blists - more mailing lists