From: Kyle Huey <me@kylehuey.com>
To: Kyle Huey <khuey@kylehuey.com>, linux-kernel@vger.kernel.org
Cc: Robert O'Callahan <robert@ocallahan.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH 1/2] perf/bpf: Allow a bpf program to suppress I/O signals.
Date: Mon, 4 Dec 2023 12:14:05 -0800 [thread overview]
Message-ID: <20231204201406.341074-2-khuey@kylehuey.com> (raw)
In-Reply-To: <20231204201406.341074-1-khuey@kylehuey.com>
Returning zero from a bpf program attached to a perf event already
suppresses any data output. This allows it to suppress I/O availability
signals too.
Signed-off-by: Kyle Huey <khuey@kylehuey.com>
---
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 b704d83a28b2..34d7b19d45eb 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -10417,8 +10417,10 @@ static void bpf_overflow_handler(struct perf_event *event,
rcu_read_unlock();
out:
__this_cpu_dec(bpf_prog_active);
- if (!ret)
+ if (!ret) {
+ event->pending_kill = 0;
return;
+ }
event->orig_overflow_handler(event, data, regs);
}
--
2.34.1
next prev parent reply other threads:[~2023-12-04 20:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 20:14 [PATCH 0/2] Combine perf and bpf for fast eval of hw breakpoint conditions Kyle Huey
2023-12-04 20:14 ` Kyle Huey [this message]
2023-12-04 22:18 ` [PATCH 1/2] perf/bpf: Allow a bpf program to suppress I/O signals Andrii Nakryiko
2023-12-05 11:16 ` Jiri Olsa
2023-12-05 18:07 ` Namhyung Kim
2023-12-05 18:16 ` Marco Elver
2023-12-05 18:23 ` Kyle Huey
2023-12-05 18:26 ` Namhyung Kim
2023-12-05 19:19 ` Kyle Huey
2023-12-04 20:14 ` [PATCH 2/2] selftest/bpf: Test returning zero from a perf bpf program suppresses SIGIO Kyle Huey
2023-12-04 22:14 ` Andrii Nakryiko
2023-12-05 18:21 ` Kyle Huey
2023-12-05 11:17 ` Jiri Olsa
2023-12-05 16:54 ` Yonghong Song
2023-12-05 17:52 ` Kyle Huey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231204201406.341074-2-khuey@kylehuey.com \
--to=me@kylehuey.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=khuey@kylehuey.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robert@ocallahan.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®