From: Puranjay Mohan <puranjay@kernel.org>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
puranjay12@gmail.com
Subject: [PATCH bpf-next v2 0/2] Implement mechanism to signal other threads
Date: Thu, 26 Sep 2024 11:53:26 +0000 [thread overview]
Message-ID: <20240926115328.105634-1-puranjay@kernel.org> (raw)
This set implements a kfunc called bpf_send_signal_remote() that is similar
to sigqueue() as it can send a signal along with a cookie to a thread or
thread group.
The send_signal selftest has been updated to also test this new kfunc under
all contexts.
Changes in v2:
v1: https://lore.kernel.org/bpf/20240724113944.75977-1-puranjay@kernel.org/
- Convert to a kfunc
- Add mechanism to send a cookie with the signal.
Puranjay Mohan (2):
bpf: implement bpf_send_signal_remote() kfunc
selftests/bpf: Augment send_signal test with remote signaling
kernel/trace/bpf_trace.c | 78 +++++++++-
.../selftests/bpf/prog_tests/send_signal.c | 133 +++++++++++++-----
.../bpf/progs/test_send_signal_kern.c | 35 ++++-
3 files changed, 207 insertions(+), 39 deletions(-)
--
2.40.1
next reply other threads:[~2024-09-26 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 11:53 Puranjay Mohan [this message]
2024-09-26 11:53 ` [PATCH bpf-next v2 1/2] bpf: implement bpf_send_signal_remote() kfunc Puranjay Mohan
2024-09-29 17:13 ` Alexei Starovoitov
2024-09-30 21:48 ` Andrii Nakryiko
2024-09-30 21:52 ` Andrii Nakryiko
2024-10-01 8:39 ` Puranjay Mohan
2024-10-01 8:38 ` Puranjay Mohan
2024-09-26 11:53 ` [PATCH bpf-next v2 2/2] selftests/bpf: Augment send_signal test with remote signaling Puranjay Mohan
2024-09-29 17:17 ` Alexei Starovoitov
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=20240926115328.105634-1-puranjay@kernel.org \
--to=puranjay@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=puranjay12@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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