From: Benjamin Tissoires <bentiss@kernel.org>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
bpf@vger.kernel.org, Benjamin Tissoires <bentiss@kernel.org>
Subject: [PATCH RFC HID 0/7] Use the new __s_async for HID-BPF
Date: Wed, 08 May 2024 12:26:35 +0200 [thread overview]
Message-ID: <20240508-hid_bpf_async_fun-v1-0-558375a25657@kernel.org> (raw)
This is not meant to be applied as of now.
This is just to show what I meant for [0].
And of course, this doesn't even compile because you need [0] to be
applied and the branch for-6.10/hid-bpf on the hid tree.
The purpose is to remove the bpf_tail_call from the preloaded bpf at
boot time.
Cheers,
Benjamin
[0] https://lore.kernel.org/bpf/20240507-bpf_async-v1-0-b4df966096d8@kernel.org/v
Signed-off-by: Benjamin Tissoires <bentiss@kernel.org>
---
Benjamin Tissoires (7):
HID: bpf: change the prog run logic
selftests/hid: fix bpf programs for the new attachment logic
HID: bpf: allow for sleepable bpf hooks
HID: add source argument to HID low level functions
WIP: add HID-BPF hooks for hid_hw_raw_requests
WIP: selftests/hid: add tests for hid_hw_raw_request HID-BPF hooks
HID: bpf: prevent infinite recursions with hid_hw_raw_requests hooks
drivers/hid/bpf/entrypoints/Makefile | 93 --------
drivers/hid/bpf/entrypoints/README | 4 -
drivers/hid/bpf/entrypoints/entrypoints.bpf.c | 25 --
drivers/hid/bpf/entrypoints/entrypoints.lskel.h | 248 --------------------
drivers/hid/bpf/hid_bpf_dispatch.c | 252 +++++++++++----------
drivers/hid/bpf/hid_bpf_dispatch.h | 12 +-
drivers/hid/bpf/hid_bpf_jmp_table.c | 199 ++++------------
drivers/hid/hid-core.c | 91 +++++---
drivers/hid/hidraw.c | 10 +-
include/linux/hid.h | 6 +
include/linux/hid_bpf.h | 33 ++-
tools/testing/selftests/hid/hid_bpf.c | 61 ++++-
tools/testing/selftests/hid/progs/hid.c | 91 +++++---
.../testing/selftests/hid/progs/hid_bpf_helpers.h | 60 ++++-
14 files changed, 449 insertions(+), 736 deletions(-)
---
base-commit: 89ea968a9d759f71ac7b8d50949a8e5e5bcb1111
change-id: 20240508-hid_bpf_async_fun-25a8b97b5352
Best regards,
--
Benjamin Tissoires <bentiss@kernel.org>
next reply other threads:[~2024-05-08 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 10:26 Benjamin Tissoires [this message]
2024-05-08 10:26 ` [PATCH RFC HID 1/7] HID: bpf: change the prog run logic Benjamin Tissoires
2024-05-08 10:26 ` [PATCH RFC HID 2/7] selftests/hid: fix bpf programs for the new attachment logic Benjamin Tissoires
2024-05-08 10:26 ` [PATCH RFC HID 3/7] HID: bpf: allow for sleepable bpf hooks Benjamin Tissoires
2024-05-08 10:26 ` [PATCH RFC HID 4/7] HID: add source argument to HID low level functions Benjamin Tissoires
2024-05-08 10:26 ` [PATCH RFC HID 5/7] WIP: add HID-BPF hooks for hid_hw_raw_requests Benjamin Tissoires
2024-05-08 10:26 ` [PATCH RFC HID 6/7] WIP: selftests/hid: add tests for hid_hw_raw_request HID-BPF hooks Benjamin Tissoires
2024-05-08 10:26 ` [PATCH RFC HID 7/7] HID: bpf: prevent infinite recursions with hid_hw_raw_requests hooks Benjamin Tissoires
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=20240508-hid_bpf_async_fun-v1-0-558375a25657@kernel.org \
--to=bentiss@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).