From: Samuel Wu <wusamuel@google.com>
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>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: Samuel Wu <wusamuel@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [PATCH bpf-next v5 0/2] Add wakeup_source iterators
Date: Wed, 25 Feb 2026 13:08:16 -0800 [thread overview]
Message-ID: <20260225210820.177674-1-wusamuel@google.com> (raw)
This patch series introduces BPF iterators for wakeup_source, enabling
BPF programs to efficiently traverse a device's wakeup sources.
Currently, inspecting wakeup sources typically involves reading interfaces
like /sys/class/wakeup/* or debugfs. The repeated syscalls to query the
sysfs nodes is inefficient, as there can be hundreds of wakeup_sources, and
each wakeup source have multiple stats, with one sysfs node per stat.
debugfs is unstable and insecure.
The iterators utilize pre-existing wakeup_sources_walk_* functions to
traverse over the SRCU that backs the list of wakeup_sources.
Changes in v5:
- Add CORE definitions for *__local variables to fix s390 build per bpf-ci
- v4 link: https://lore.kernel.org/all/20260211235055.239024-1-wusamuel@google.com/
Changes in v4:
- Proper init of variables in ws_iter_check_sleep_times() test per bpf-ci
- Remove PM patch since it's already part of rebase
- v3 link: https://lore.kernel.org/all/20260124012133.2451708-1-wusamuel@google.com/
Changes in v3:
- Update wakeup_sources_walk_start() to handle an empty list per bpf-ci
- Simplify read of a struct's field in BPF program selftest per Andrii
- Drop open coded iterators for wakeup_sources
- Fix condition from !get_ws_iter_stream to get_ws_iter_stream in selftest
- Read event_count instead of wakeup_count in selftest
- v2 link: https://lore.kernel.org/all/20260108225523.3268383-1-wusamuel@google.com/
Changes in v2:
- Guard BPF Makefile with CONFIG_PM_SLEEP to fix build errors
- Update copyright from 2025 to 2026
- v1 link: https://lore.kernel.org/all/20251204025003.3162056-1-wusamuel@google.com/
Samuel Wu (2):
bpf: Add wakeup_source iterator
selftests/bpf: Add tests for wakeup_sources
kernel/bpf/Makefile | 3 +
kernel/bpf/wakeup_source_iter.c | 103 ++++++
tools/testing/selftests/bpf/config | 1 +
.../bpf/prog_tests/wakeup_source_iter.c | 300 ++++++++++++++++++
.../selftests/bpf/progs/wakeup_source_iter.c | 80 +++++
5 files changed, 487 insertions(+)
create mode 100644 kernel/bpf/wakeup_source_iter.c
create mode 100644 tools/testing/selftests/bpf/prog_tests/wakeup_source_iter.c
create mode 100644 tools/testing/selftests/bpf/progs/wakeup_source_iter.c
--
2.53.0.473.g4a7958ca14-goog
next reply other threads:[~2026-02-25 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 21:08 Samuel Wu [this message]
2026-02-25 21:08 ` [PATCH bpf-next v5 1/2] bpf: Add wakeup_source iterator Samuel Wu
2026-02-25 22:03 ` bot+bpf-ci
2026-02-25 22:35 ` Samuel Wu
2026-02-25 21:08 ` [PATCH bpf-next v5 2/2] selftests/bpf: Add tests for wakeup_sources Samuel Wu
2026-03-05 1:31 ` [PATCH bpf-next v5 0/2] Add wakeup_source iterators Samuel Wu
2026-03-06 23:28 ` Kumar Kartikeya Dwivedi
2026-03-07 20:17 ` Kumar Kartikeya Dwivedi
2026-03-11 0:23 ` Samuel Wu
2026-03-11 9:06 ` Kumar Kartikeya Dwivedi
2026-03-12 17:13 ` Samuel Wu
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=20260225210820.177674-1-wusamuel@google.com \
--to=wusamuel@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@android.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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