Changes in Makefile

b2128290c29902315e632ea59e0504d6bc9e9b42 - Merge remote-tracking branch 'drm/drm-next' into msm-next-backmerge

Sat, 18 Jul 2026 17:06:55 +0200

Merge remote-tracking branch 'drm/drm-next' into msm-next-backmergeBackmerge of drm-next, mainly to pick up dt bindings docs updates toavoid conflicts.Signed-off-by: Rob Clark List of files: /linux/tools/testing/selftests/bpf/Makefile

637315cb400eed1dbe721954fea437a61a2d65b2 - Merge tag 'kvm-riscv-7.3-1' of https://github.com/kvm-riscv/linux into HEAD

Tue, 18 Aug 2026 13:07:31 +0200

Merge tag 'kvm-riscv-7.3-1' of https://github.com/kvm-riscv/linux into HEADKVM/riscv changes for 7.3- Svadu/Zicfiss/Zicfilp FWFT support for Guest- Use try_cmpxchg for IMSIC MRIF RMW- More arch-specific tracepoints in KVM RISC-V- Eager Page Splitting for KVM RISC-V- Optimize hfence request handling for SMP Guests- Improve dirty log clearing by skipping zero bits in mask- Guard HFENCE range loops against overflow- CPU PM notifiers in KVM RISC-V for non-retentive idle states- Fix kernel-mode vector context save/restore for Guest List of files: /linux/tools/testing/selftests/bpf/Makefile

473f6c8f437b049f8ec015d57cd59bb983b1d85c - Merge tag 'perf-tools-for-v7.3-2026-08-21' of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools

Sat, 22 Aug 2026 17:47:50 +0200

Merge tag 'perf-tools-for-v7.3-2026-08-21' of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-toolsPull perf tools updates from Namhyung Kim: "perf c2c: - Add 'function view' in perf c2c report TUI (switched by pressing 'TAB' in the cacheline view) to organize samples around functions rather than cachelines in 3-level hierarchy: Level 1: Read-side function (sorted by estimated Cycles %) Level 2: Contending writer functions (sorted by Store count) Level 3: Shared cacheline addresses Users can navigate the entries and fold/unfold using 'e' key. An example output would look like below: Shared Data Functions Table (19 entries, sorted on Cycles %) Cycles Store % count Function / Contending function / Cacheline ---------------------------------------------------------------------- + 35.67% 876 + [k] cpupri_set + 24.31% 424 + [k] pull_rt_task - 16.53% 555 - [k] dequeue_pushable_task 145 - [k] pull_rt_task 145 0xff2d0082809da080 139 - [k] enqueue_pushable_task 70 0xff2d00a2071f9640 69 0xff2d0082809da000 python module support: - Extend "perf" python module so that it can be fully functional. The goal is to run scripts directly, not by 'perf script' command. This would give better performance as well as more control to build standalone programs with UI. - Add LiveSession helper (perf_live.py) to enable live event collection directly from Python using perf.evlist and perf.parse_events. perf stat: - Add --hide-zero-events option to suppress zero-count events - Reject conflicting --field-separator and --json-output options - Fix duplicate event output with --for-each-cgroup perf sched latency: - Add -H/--histogram and --hist-mode (log|linear) options to show scheduler wait latency histograms - Add --time option to filter analysis by time span in 'perf sched latency' ARM CoreSight: - Synthesize callchains for instruction samples from CoreSight trace using thread stack ('--itrace=g...') - Support call indentation ('perf script -F +callindent') to display call depth hierarchy on branch samples - Decode ETE (Embedded Trace Extension) exception packets Build system: - Add 'make install-build-deps' target to install required packages - Parallelize JSON and metric pre-computation in jevents.py for faster builds Vendor event/metric updates: - Add Intel Nova Lake events and update tables for existing models - Update AMD Zen 5 and Zen 6 core events - Update Arm64 Tegra410 metrics and PowerPC hcalls Internal changes and fixes: - Harden trace-event and synthetic event parsing against corrupted data - Fix unwinding of multi-threaded processes in libdw unwinder - Fix memory leaks in various commands and python bindings - Speed up 'perf test' shell tests"* tag 'perf-tools-for-v7.3-2026-08-21' of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools: (232 commits) perf vendor events arm64: Fix Tegra410 Olympus event 0x0197 perf vendor events arm64: fix swapped MetricGroup for Tegra410 L1 prefetcher metrics perf evlist: Warn when 'sleep' workload is used without system-wide (-a) option perf c2c: document function view in perf-c2c man page perf c2c: add function view browser UI and cacheline detail perf c2c: build and finalize the function view hierarchy perf c2c: add function view hierarchy entry creation perf c2c: add function view stats merge and memory management perf c2c: add HPP list parsing for function view columns perf c2c: add column rendering for function view perf c2c: add function view model skeleton perf c2c: extract shared data structures into util/c2c.h perf test sample-parsing: Validate PERF_FORMAT_GROUP values without LOST perf dso: Replace assert with runtime check in dso__read_symbol() perf dso: Guard against cache underflow on short reads in dso_cache__memcpy() perf dso: Use stored fd error instead of stale errno in file_read() and file_size() perf dso: Guard close() against invalid fd in dso__decompress_kmodule_path() perf dso: Guard against errno==0 when dso__get_filename() returns NULL perf build: install-build-deps: add RHEL family devel package mapping perf build: Remove leftover feature tests for removed cxx and clang support ... List of files: /linux/tools/testing/selftests/bpf/Makefile

b2d4225695e6977cd7802fe425d8caa5822a5e7d - tools/build: selftests: Remove some duplicate toolchain definitions

Wed, 15 Jul 2026 16:53:51 +0200

tools/build: selftests: Remove some duplicate toolchain definitionsTry to remove some, but not all duplicate toolchain definitions. Inthese instances, their makefiles already includetools/scripts/Makefile.include which defines these in a consistent way.STRIP is the only one that was set with an '=', but I don't think itwas significant so that difference can be dropped.Signed-off-by: James Clark Reviewed-by: Ian Rogers Acked-by: Ihor Solodrai Acked-by: Kumar Kartikeya Dwivedi Signed-off-by: Namhyung Kim List of files: /linux/tools/testing/selftests/bpf/Makefile

efe86f088f48f18c27b648e5724048947f3b7fb4 - Merge drm/drm-next into drm-xe-next

Tue, 14 Jul 2026 15:40:31 +0200

Merge drm/drm-next into drm-xe-nextSync some i915/display changesSigned-off-by: Rodrigo Vivi List of files: /linux/tools/testing/selftests/bpf/Makefile

6d177908bad5992e17669030db41caab88041d5e - Merge drm/drm-next into drm-intel-next

Tue, 30 Jun 2026 14:55:43 +0200

Merge drm/drm-next into drm-intel-nextSync with v7.2-rc1.Signed-off-by: Jani Nikula List of files: /linux/tools/testing/selftests/bpf/Makefile

827b9aabd3ea3e96d5e48abed9f44dbd1e550d4e - Merge drm/drm-next into drm-misc-next

Tue, 30 Jun 2026 10:16:00 +0200

Merge drm/drm-next into drm-misc-nextBackmerging to get drm-misc-next to v7.2-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/testing/selftests/bpf/Makefile

7dd19adaaac9a161723a24de7c270861063ec6ac - Merge tag 'v7.2-rc1' into drm-rust-next

Sun, 28 Jun 2026 22:39:43 +0200

Merge tag 'v7.2-rc1' into drm-rust-nextMerge v7.2-rc1 into drm-rust-next to start the next cycle.Devres now requires T: 'static, which conflicts with shmem::Object usingDevres> without that bound. Resolve by adding 'staticas a supertrait to DriverObject and DeviceContext, which does notrestrict any current use cases since DriverObject is always implementedon owned, refcounted types and DeviceContext is a sealed marker traitwith only unit-type implementors.If DriverObject (or DeviceContext) ever becomes lifetime-parameterized(e.g. via a GAT for TTM backed objects), the 'static supertrait can berelaxed at that point.Signed-off-by: Danilo Krummrich List of files: /linux/tools/testing/selftests/bpf/Makefile

5a8cd539ac19f7a68e68e1d25ef9ca2ff55b8500 - Merge tag 'bpf-next-7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next

Thu, 20 Aug 2026 16:36:20 +0200

Merge tag 'bpf-next-7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-nextPull bpf updates from Daniel Borkmann: "Major changes: - Redesign the verifier error reporting: failures now carry source and instruction annotations along with the causal event history that led to them, making program rejections far easier to debug and repair (Kumar Kartikeya Dwivedi) - Add arena argument support to kfuncs and struct_ops through the new __arena and __arena__nullable suffixes (Tejun Heo, Puranjay Mohan, Kumar Kartikeya Dwivedi, Ihor Solodrai) - Signed BPF program loader rework to accommodate both BPF and security community needs where the kernel runs the signature verification at BPF_PROG_LOAD time before the LSM admission hook (Daniel Borkmann) - Add a set of ksock kfuncs which let BPF LSM and syscall programs create, connect and send on UDP sockets in order to emit telemetry data (Mahe Tardy) - Unify helper and kfunc call argument verification and classify kfunc arguments purely from BTF into a generated bpf_func_proto which is computed once at add-call time (Amery Hung) Other features and fixes: - Enable EXECMEM_ROX_CACHE for BPF allocations on x86 (Mike Rapoport) - Add bidirectional VLAN support to bpf_fib_lookup() through the new BPF_FIB_LOOKUP_VLAN and BPF_FIB_LOOKUP_VLAN_INPUT flags (Avinash Duduskar) - Infer zext_dst from static register liveness analysis to fix 32-bit zero-extension semantics, and remove the artificial limitations on pointer types eligible for spilling (Eduard Zingerman) - Inline the numeric open-coded iterator kfuncs so that bpf_for() loops no longer pay a kfunc call on every iteration (Puranjay Mohan) - Add an arena-based bitmap data structure to libarena along with serial and parallel selftests (Emil Tsalapatis) - Teach resolve_btfids to discover kfuncs from the kernel's BTF ID sets and to emit kfunc BTF decl tags, reducing the kernel build's dependency on pahole features (Ihor Solodrai) - Add BPF_F_ADJ_ROOM_DECAP_* flags to bpf_skb_adjust_room() so that tunnel decapsulation can update the GSO and encapsulation state of the skb (Nick Hudson) - Fix the ring buffer pending_pos walk and the available-data accounting on 32-bit position wrap (Israel Téllez García) - Add memory usage accounting for arena maps and fix an mmap_lock deadlock on arena lock failure (Jiayuan Chen) - Add tracing_multi link info support to the kernel UAPI and bpftool, and refactor the stack map code to run with preemption disabled (Jiri Olsa) - Support BPF_F_EGRESS in bpf_redirect_peer() to emit the skb in the egress direction of the target's peer device (Jordan Rife) - Add a KF_SPINLOCK_SAFE kfunc flag so that providers, in particular modules, can declare kfuncs safe to call under bpf_spin_lock instead of relying on the verifier's hard-coded allowlist (Kaitao Cheng) - Introduce global percpu data for BPF programs with libbpf probing and bpftool skeleton support, and stop exposing uninitialized kernel heap memory when copying per-CPU map values (Leon Hwang) - Add s390 JIT support for load-acquire and store-release instructions (Maxim Khmelevskii) - Fix a CFI mismatch in the task work callback and an arm64 KASAN false positive after bpf_throw() (Mykyta Yatsenko) - Reject writes through untrusted BTF pointers and bound the rdonly/rdwr_buf_size kfunc arguments (Nicholas Dudar) - Invalidate RCU pointers only after the final spin unlock and account for preempt and IRQ disabled regions as overlapping RCU protection (Ning Ding) - Support mixing bpf2bpf calls and tail calls on RV64, add signed operations and 32-bit atomics to the RV32 JIT, and add timed may_goto support (Pu Lehui, Kuan-Wei Chiu, Feng Jiang) - Fix a use-after-free on mm_struct in bpf_find_vma() for foreign tasks and an mmap_lock leak in the irq_work path (Sanghyun Park) - Populate mmap-able BPF array map memory lazily which makes mmap() O(1) instead of proportional to the map size (Song Liu) - Introduce a jit_required flag and reject programs with inlined helpers when no JIT is available, where the interpreter would otherwise jump into an invalid address (Tiezhu Yang) - Fix the x86 JIT per-CPU address resolution into an extended register where the REX prefix dropped the high destination register bit (Vineet Gupta) - Reject MEM_ALLOC BTF accesses past object bounds, arena frees below the arena base, and mixed arena and ordinary atomic paths (Yiyang Chen) - Fix the trampoline handling of 128-bit arguments and of return values larger than 8 bytes (Yonghong Song) - Ensure that any fault prone load is rewritten with exception table handling, and fix the arena load-acquire and atomic fetch handling in the x86, arm64, riscv and s390 JITs (Daniel Borkmann) - Many more fixes and cleanups across the verifier, arena, trampolines, sockmap, cgroup, ring buffer, x86/arm64/riscv/s390 JITs, libbpf, bpftool, resolve_btfids and selftests"* tag 'bpf-next-7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next: (373 commits) selftests/bpf: Add tests for a store on a fault prone qdisc pointer selftests/bpf: Add tests for fault prone loads out of RCU pointers selftests/bpf: Add tests for pointer type merge at a shared load selftests/bpf: Remove duplicate copies of the arena spinlock qnodes selftests/bpf: Retry stat generation in cgroup_iter_memcg selftests/bpf: Test pseudo-function policy diagnostics bpf: Distinguish function references in policy diagnostics bpf: Preserve source attribution without source text selftests/bpf: Test kfunc argument diagnostics bpf: Correct kfunc argument diagnostics bpf: Use canonical stack argument names in diagnostics bpf: Preserve R0 lineage across helper calls selftests/bpf: Exercise negative optlen in cgroup getsockopt hook bpf: Reject negative optlen in cgroup getsockopt hook selftests/bpf: tc_tunnel - validate decap GSO and encapsulation state bpf: Clear decap state on skb_adjust_room shrink path bpf: Allow new DECAP flags and add guard rails bpf: Add BPF_F_ADJ_ROOM_DECAP_* flags for tunnel decapsulation bpf: Refactor masks for ADJ_ROOM flags and encap validation bpf: Name the enum for BPF_FUNC_skb_adjust_room flags ... List of files: /linux/tools/testing/selftests/bpf/Makefile

fab183d632628381b466a41479489541ac0e29a0 - sched_ext: Merge branch 'for-7.3-arena-args' into for-7.3

Mon, 17 Aug 2026 23:20:34 +0200

sched_ext: Merge branch 'for-7.3-arena-args' into for-7.3Pull to receive the __arena argument conversion: 67f1f4a48c24 ("sched_ext: Pass kernel arena pointers to ops_cid callbacks") a8dc810968af ("sched_ext: Convert sub-cap kfuncs to __arena cmask arguments") a05c5b5cb5cf ("sched_ext: Convert scx_bpf_cid_override() to __arena array arguments")along with the bpf-next branch carrying the __arena argument support theydepend on.Conflict in kernel/sched/ext/ext.c between: c384ab8a0b13 ("sched_ext: Move the config-off sub-cap kfunc stubs into sub.c")and: a8dc810968af ("sched_ext: Convert sub-cap kfuncs to __arena cmask arguments")which updated the stubs in their old ext.c location. Resolved by keepingext.c without the stubs and applying the prototype conversion to therelocated stubs in sub.c.Signed-off-by: Tejun Heo List of files: /linux/tools/testing/selftests/bpf/Makefile

a2b83a8c8430b5a4cb43a1671c62535afcfce78d - selftests/bpf: Fix selftest build after filter.h update

Fri, 14 Aug 2026 19:35:21 +0200

selftests/bpf: Fix selftest build after filter.h updateUpstream commit 7a1f400ff5e5 ("tools: Ensure tools copy oflinux/filter.h exports the UAPI") caused selftests/bpf build tofail [1] with: In file included from progs/arena_atomics.c:9: /codebuild/output/src2365462129/src/actions-runner/_work/bpf/bpf/tools/testing/selftests/bpf/../../../include/linux/filter.h:9:10: fatal error: 'uapi/linux/filter.h' file not found 9 | #include | ^~~~~~~~~~~~~~~~~~~~~ 1 error generated. CLNG-BPF [test_progs] bind_perm.bpf.o make: *** [Makefile:888: /codebuild/output/src2365462129/src/actions-runner/_work/bpf/bpf/tools/testing/selftests/bpf/arena_atomics.bpf.o] Error 1 make: *** Waiting for unfinished jobs.... GEN-OBJ [libarena] libarena.bpf.o GEN-SKEL [libarena] libarena.skel.h make: Leaving directory '/codebuild/output/src2365462129/src/actions-runner/_work/bpf/bpf/tools/testing/selftests/bpf' Process completed with exit code 2.BPF selftest programs include the tools header directly, butBPF_CFLAGS only exposes tools/include/uapi. Compiler therefore cannotresolve the nested UAPI include.Add tools/include after tools/include/uapi in BPF_CFLAGS. Thispreserves the existing UAPI header precedence while allowing toolsheaders to include uapi headers.[1] https://github.com/kernel-patches/bpf/actions/runs/31806678733/job/94787271162Fixes: 7a1f400ff5e5 ("tools: Ensure tools copy of linux/filter.h exports the UAPI")Signed-off-by: Ihor Solodrai Signed-off-by: Andrii Nakryiko Link: https://lore.kernel.org/bpf/20260814173522.2783625-1-ihor.solodrai@linux.dev List of files: /linux/tools/testing/selftests/bpf/Makefile

806c1a185215382fab5a7fafc74e30070b2fb043 - Merge branch 'bpf-introduce-global-percpu-data'

Thu, 13 Aug 2026 19:27:41 +0200

Merge branch 'bpf-introduce-global-percpu-data'Leon Hwang says:====================bpf: Introduce global percpu dataThis patch set introduces global percpu data, similar to commit6316f78306c1 ("Merge branch 'support-global-data'"), to reduce restrictionsin C for BPF programs.With this enhancement, it becomes possible to define and use global percpuvariables, like the DEFINE_PER_CPU() macro in the kernelinclude/linux/percpu-defs.h.The section name for global peurcpu data is ".percpu". Even though, a one-bytepercpu variable (e.g., char run SEC(".percpu") = 0;) can trigger a crashwith Clang 17 [1], users are expected to use such small variables as globalpercpu data with newer Clang versions, which don't have the issue.The idea stems from the bpfsnoop [2], which itself was inspired byretsnoop [3]. During testing of bpfsnoop on the v6.6 kernel, two LBR(Last Branch Record) entries were observed related to thebpf_get_smp_processor_id() helper.Since commit 1ae6921009e5 ("bpf: inline bpf_get_smp_processor_id() helper"),the bpf_get_smp_processor_id() helper has been inlined on x86_64, reducingthe overhead and consequently minimizing these two LBR records.However, the introduction of global percpu data offers a more robustsolution. By leveraging the percpu_array map and percpu instruction,global percpu data can be implemented intrinsically.This feature also facilitates sharing percpu information between tailcallers and callees or between freplace callers and callees through ashared global percpu variable. Previously, this was achieved using a1-entry percpu_array map, which this patch set aims to improve upon.Links:[1] https://lore.kernel.org/bpf/fd1b3f58-c27f-403d-ad99-644b7d06ecb3@linux.dev/[2] https://github.com/bpfsnoop/bpfsnoop[3] https://github.com/anakryiko/retsnoopChanges:v11 -> v12:* Improve feature check in bpf_object__create_maps() in libbpf.* Add percpu_array map support in bpf_map__set_value_size() in libbpf.* Exercise bpf_map__set_value_size() in selftest.* Drop dead warning in bpf_object__populate_internal_map() in libbpf. (Sashiko)* v11: https://lore.kernel.org/bpf/20260806163125.11172-1-leon.hwang@linux.dev/v10 -> v11:* Drop env->prog->jit_requested check when inlining insns for global percpu data.* Do not autocreate percpu_array map when kernel does not have global percpu data support in libbpf.* Check map->btf_value_type_id in bpftool's is_skel_data().* Exercise bpf_map__lookup_elem() in selftest.* Collect Reviewed-by tags from Emil, thanks.* Drop all duplicate blank lines in kernel/bpf/*.c. (Emil)* Factor out check_map_mem_read() helper. (Emil)* Check bpf_jit_supports_percpu_insn() first in percpu_array_map_direct_value_addr/meta(). (Emil)* Add comment for 'map->libbpf_type == LIBBPF_MAP_PERCPU' in libbpf's map_is_mmapable(). (Emil)* Init update_flags as a const var in libbpf's bpf_object__populate_internal_map(). (Emil)* Keep is_mmapable_map() beyond is_skel_data() in bpftool. (Emil)* Add 'run' and 'cpu_id' in selftest. (Emil)* Drop subskel test. Verify the generated subskel manually. (Emil)* Add comment to the raw insns in selftest. (Emil)* v10: https://lore.kernel.org/bpf/20260715153254.92010-1-leon.hwang@linux.dev/v9 -> v10:* Rebase latest bpf-next tree to resolve code conflict in verifier in patch #1.* v9: https://lore.kernel.org/bpf/20260713154024.30851-1-leon.hwang@linux.dev/v8 -> v9:* Use real name for percpu data maps in libbpf in patch #4.* Add long map name test in patch #6.* Move parse_cpu_mask_file() to test_percpu_data_on_cpus() in test in patch #6.* Validate map type in get_map_ident() for percpu data maps in patch #5.* Update code comment in verifier in patch #2. (per Andrii)* Pass 'type' to internal_map_name in libbpf in patch #4. (per Andrii)* Factor out the helper is_skel_data() in bpftool in patch #5. (per Quentin and Andrii)* v8: https://lore.kernel.org/bpf/20260629152406.52582-1-leon.hwang@linux.dev/v7 -> v8:* Send patch #1 and #2 separately that fix interpreter fallback issues. (Andrii)* Use 'array->elem_size' to avoid 'range' local variable in percpu_array_map_direct_value_meta(). (Andrii)* Keep original map name for percpu data's map in libbpf. (Andrii)* Factor out helper bpf_map_is_skel_data() in bpftool. (Andrii)* Update commit message of direct access read-only percpu_array map. (Andrii)* Add test to verify that it is disallowed to directly write data of read-only percpu_array map. (Andrii)* Drop unused 'num_cpus' in test. (bot+bpf-ci)* Factor out helper test_percpu_data_on_cpus() in test. (bot+bpf-ci)* v7: https://lore.kernel.org/bpf/20260622143557.22955-1-leon.hwang@linux.dev/v6 -> v7:* Use tgt_endian() in bpf_gen__map_update_elem() in patch #6. (Sashiko)* Use sizeof(args) in verifier_snprintf test in patch #10. (Sashiko)* Drop xlated test of v6. (Alexei)* v6: https://lore.kernel.org/bpf/20260615152646.27639-1-leon.hwang@linux.dev/v5 -> v6:* Prevent running user addr_space_cast and addr_percpu insns in interpreter. (Sashiko)* Cast __percpu pointer to u64 with (__force unsigned long). (lkp)* Exclude BPF_MAP_TYPE_PERCPU_ARRAY in check_mem_access() before calling bpf_map_direct_read(), and add a test to verify it. (Sashiko, bot+bpf-ci)* Skip percpu data variables for subskeleton in bpftool. (Sashiko)* Protect skel->percpu using mprotect(..., PROT_READ) in light skeleton. (Sashiko, bot+bpf-ci)* Drop roundup() in tests. (Sashiko)* Call test_global_percpu_data_verifier_log() without test__start_subtest(). (Sashiko)* Cast insn->imm to __u64 with (__u32) in xlated test. (Sashiko)* Check cnt using the new idx in xlated test. (Sashiko)* v5: https://lore.kernel.org/bpf/20260608145113.65857-1-leon.hwang@linux.dev/v4 -> v5:* Add prog->jit_requested check to prevent running percpu data in interpreter in patch #1.* Factor out verifier log tests using its own patch.* Address comments from Alexei: * Move map_type check from check_mem_access() to bpf_map_direct_read() in patch #2. * Move BPF_MAP_TYPE_INSN_ARRAY map_type check from const_reg_xfer() to bpf_map_direct_read() in patch #2. * Add a test to verify that the off of xlated ldimm64 insn matches the off encoded in the ELF ldimm64 insn. * Drop patch #5 of v4.* Address reviews from Sashiko: * Update commit message of patch #6 to indicate that maps.percpu->mmaped has been marked as read-only in libbpf. * Lookup elem on specified CPU using BPF_F_CPU in tests. * Drop unnecessary err == -EOPNOTSUPP in test. * Locate target field using its offset in the iter test.* v4: https://lore.kernel.org/bpf/20260414132421.63409-1-leon.hwang@linux.dev/v3 -> v4:* Drop duplicate blank lines in verifier.* Add percpu data feature probe in libbpf.* Update percpu_array map using BPF_F_ALL_CPUS flag for lskel, if no cpu flag is set.* Add two tests to verify verifier log.* Add a test to verify mov64_percpu_reg instruction.* Add a test to verify bpf_iter for percpu data map.* Update percpu_array map using BPF_F_ALL_CPUS flag in libbpf (per Alexei and Andrii).* Address comments from Andrii: * Use .percpu as section identifier. * Use bpf_jit_supports_percpu_insn() instead of CONFIG_SMP. * Drop bpf_map__is_internal_percpu() API. * Drop unnecessary __aligned(8) in libbpf, verified by selftest. * Make mmap data read-only after loading prog.v3: https://lore.kernel.org/bpf/20250526162146.24429-1-leon.hwang@linux.dev/v2 -> v3: * Use ".data..percpu" as PERCPU_DATA_SEC. * Address comment from Alexei: * Add u8, array of ints and struct { .. } vars to selftest.v2: https://lore.kernel.org/bpf/20250213161931.46399-1-leon.hwang@linux.dev/v1 -> v2: * Address comments from Andrii: * Use LIBBPF_MAP_PERCPU and SEC_PERCPU. * Reuse mmaped of libbpf's struct bpf_map for .percpu map data. * Set .percpu struct pointer to NULL after loading skeleton. * Make sure value size of .percpu map is __aligned(8). * Use raw_tp and opts.cpu to test global percpu variables on all CPUs. * Address comments from Alexei: * Test non-zero offset of global percpu variable. * Test case about BPF_PSEUDO_MAP_IDX_VALUE.v1: https://lore.kernel.org/bpf/20250127162158.84906-1-leon.hwang@linux.dev/rfc -> v1: * Address comments from Andrii: * Keep one image of global percpu variable for all CPUs. * Reject non-ARRAY map in bpf_map_direct_read(), check_reg_const_str(), and check_bpf_snprintf_call() in verifier. * Split out libbpf changes from kernel-side changes. * Use ".percpu" as PERCPU_DATA_SEC. * Use enum libbpf_map_type to distinguish BSS, DATA, RODATA and PERCPU_DATA. * Avoid using errno for checking err from libbpf_num_possible_cpus(). * Use "map '%s': " prefix for error message.rfc: https://lore.kernel.org/bpf/20250113152437.67196-1-leon.hwang@linux.dev/====================Link: https://patch.msgid.link/20260813152324.97937-1-leon.hwang@linux.devSigned-off-by: Andrii Nakryiko List of files: /linux/tools/testing/selftests/bpf/Makefile

4c9241bd731a0205cee2c4a4fa0abe866c767e2f - selftests/bpf: Add tests to verify global percpu data

Thu, 13 Aug 2026 17:23:20 +0200

selftests/bpf: Add tests to verify global percpu dataIf the arch, like s390x, does not support percpu insn, these cases won'ttest global percpu data by checking FEAT_PERCPU_DATA support.The following APIs have been tested for global percpu data:1. bpf_map__set_initial_value()2. bpf_map__initial_value()3. bpf_map__set_value_size()4. generated percpu struct pointer pointing to internal map's mmaped data5. bpf_map__lookup_elem() for global percpu data map6. bpf_map_lookup_elem_flags() for global percpu data mapAt the same time, the case is also tested with 'bpftool gen skeleton -L'.Assisted-by: Codex:gpt-5.5-xhighSigned-off-by: Leon Hwang Signed-off-by: Andrii Nakryiko Link: https://lore.kernel.org/bpf/20260813152324.97937-8-leon.hwang@linux.dev List of files: /linux/tools/testing/selftests/bpf/Makefile

872a8f6b08069d1b4bfb9bf968dc629ab6998908 - Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next into for-7.3-arena-args

Tue, 11 Aug 2026 00:38:03 +0200

Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next into for-7.3-arena-argsPull bpf-next d114bb989367 ("Merge branch'add-arena-argument-support-to-kfuncs-and-struct_ops'") to make the __arenaand __arena__nullable kfunc and struct_ops argument suffixes available. Thesuffixed arguments will be used to convert sched_ext kfuncs and struct_opscallbacks that currently pass arena pointers as scalars and rebase them byhand. List of files: /linux/tools/testing/selftests/bpf/Makefile

5b91f44f5b3c1c0249f75de5d30b85e2302ab2d3 - Merge branch 'bpf-inline-the-numeric-open-coded-iterator-kfuncs'

Wed, 05 Aug 2026 19:44:36 +0200

Merge branch 'bpf-inline-the-numeric-open-coded-iterator-kfuncs'Puranjay Mohan says:====================bpf: Inline the numeric open-coded iterator kfuncsThe bpf_for(i, start, end) macro is BPF's open-coded numeric iterator. Itexpands into calls to three kfuncs: bpf_iter_num_new() to set the iteratorup, bpf_iter_num_next() once per iteration, and bpf_iter_num_destroy() totear it down. The verifier emits these as ordinary kfunc calls, so abpf_for() loop pays function-call overhead on setup, teardown, and -- mostimportantly -- on every single iteration via bpf_iter_num_next().All three kfuncs are tiny and only touch the 8-byte on-stack iterator state(struct bpf_iter_num_kern { int cur; int end; }). That makes them goodcandidates for inlining, the same way several other special kfuncs arealready open-coded in bpf_fixup_kfunc_call(). This series replaces each ofthe three calls with an equivalent inline BPF instruction sequence: - bpf_iter_num_new(): the end - start range check is done with 32-bit arithmetic (start <= end is checked first, so the distance fits in a u32) and range-checked against BPF_MAX_LOOPS as unsigned. This avoids the cpuv4 sign-extension insns that some JITs do not implement. Returns the same -EINVAL / -E2BIG / 0 as the kfunc. - bpf_iter_num_next(): the hot path. cur and end are int, so the kfunc's s->cur + 1 >= s->end test is an ordinary signed 32-bit compare and the inlined code needs no sign extension. - bpf_iter_num_destroy(): the stack slot is no longer tracked as iterator state once destroy() returns, so nothing needs to be written to it. Both the kfunc and the inlined form become a no-op, which just drops the call.The emitted instructions are plain BPF and remain valid for theinterpreter, so interpreter fallback stays correct and no jit_requiredmarking is needed.Benchmark (./bench -p 1 --nr_loops 1000000 {bpf-loop,bpf-for}): +--------+---------------------+---------------------+---------------------+ | arch | bpf_loop | bpf_for non-inlined | bpf_for inlined | +--------+---------------------+---------------------+---------------------+ | x86-64 | 4252 M/s (0.24 ns) | 3608 M/s (0.28 ns) | 7417 M/s (0.13 ns) | +--------+---------------------+---------------------+---------------------+ | arm64 | 649 M/s (1.54 ns) | 548 M/s (1.82 ns) | 546 M/s (1.83 ns) | +--------+---------------------+---------------------+---------------------+On x86-64 removing the per-iteration call roughly doubles bpf_for()throughput. On arm64 it is neutral, and rather than guess why this waschecked with perf: inlining removes ~28% of the executed instructions (thecall) but leaves the cycle count unchanged -- IPC drops from ~4.2 to ~3.0and backend stalls rise from ~50% to ~66%. The loop is bound by the latencyof the iterator's on-stack counter, not by call overhead:bpf_iter_num_next() loads s->cur from the stack, increments it and stores itback each iteration, and the next iteration's load depends on that store.The removed call instructions were executing in the shadow of thatstore->load stall and were never on the critical path.A small userspace microbenchmark isolates the effect: a same-addressstore->load->add round-trip (the shape of the on-stack counter) costs~6 cycles/iteration on the tested arm64 core but ~1 cycle on x86-64, wherethe core collapses the same-address round-trip into a register move (memoryrenaming / store-to-load-forwarding elimination). So on x86-64 the loop isnot latency-bound and the per-iteration call dominates -- removing it is the~2x win -- whereas on arm64 the call fits entirely inside the store->loadstall the loop already has, so adding or removing it changes nothing.bpf_loop() is shown for reference only; it is a different construct (acallback invoked per iteration) and this series does not change it. Itscounter lives in a register rather than on the stack, so on arm64 it avoidsthe store->load latency above and is faster than bpf_for() there.Changelog:v4: https://lore.kernel.org/all/20260729203633.213973-1-puranjay@kernel.org/Changes in v5:- Inline the new()/next()/destroy() sequences directly in bpf_fixup_kfunc_call() instead of via helper functions (Andrii Nakryiko)- Trim the code comments; keep the explanation in the bpf_iter.c kfuncs and leave only brief comments at the inline sites, and shorten the bpf_iter_num_destroy() kfunc to /* no-op */ (Andrii Nakryiko)- Reword the patch 1 comment so it no longer forward-references the inlined bpf_iter_num_next(), which is only added later in the series (bpf-ci)- Switch the bpf_iter_num_next() comment to the networking multi-line stylev3: https://lore.kernel.org/all/20260722132424.450230-1-puranjay@kernel.org/Changes in v4:- Drop the "elide range checks for constant bounds" patch (Andrii Nakryiko)- bpf_iter_num_new(): range-check the distance against BPF_MAX_LOOPS with an unsigned compare (Andrii Nakryiko)- bpf_iter_num_destroy(): make it a no-op in both the kfunc and the inlined form instead of zeroing the iterator state (Andrii Nakryiko)- New patch: fix the misleading overflow comment in bpf_iter_num_next() and drop the redundant (s64) cast; the int wraparound is intentional and load-bearing (Andrii Nakryiko)- bpf_for benchmark: nr_loops is int, matching what bpf_for() expects (Andrii Nakryiko)- Corroborate the arm64/x86 benchmark difference with perf counters and a store-to-load-forwarding microbenchmark (Kumar Kartikeya Dwivedi, Andrii Nakryiko)v2: https://lore.kernel.org/bpf/20260717120215.2171057-1-puranjay@kernel.org/Changes in v3:- Elide the range checks in bpf_iter_num_new() when start and end are constant, marking the registers precise so paths reaching the call with different constants are not pruned (Eduard Zingerman)- Add __xlated selftests pinning the inlined new()/next()/destroy() shapes (Eduard Zingerman)- Use the insn_buf[i++] idiom in the inline helpers (Eduard Zingerman)- Pick up Acked-by on patch 3v1: https://lore.kernel.org/all/20260715130430.318421-1-puranjay@kernel.org/Changes in v2:- Don't emit sign-extending (movsx) moves; some JITs (e.g. x86-32, mips32, sparc64) decode them as a plain move and would miscompile the range check====================Link: https://patch.msgid.link/20260804134601.2305303-1-puranjay@kernel.orgSigned-off-by: Andrii Nakryiko List of files: /linux/tools/testing/selftests/bpf/Makefile

5a1de41147b0b604e49144671937e9178bf5b5c1 - selftests/bpf: Add bpf_for() benchmark

Tue, 04 Aug 2026 15:45:58 +0200

selftests/bpf: Add bpf_for() benchmarkAdd a bpf_for() benchmark modelled on bench_bpf_loop so the per-iterationiterator cost can be measured and compared against bpf_loop. It runs anempty bpf_for(i, 0, nr_loops) loop 1000 times per trigger and accountsnr_loops hits per outer iteration: $ ./bench -p 1 --nr_loops 1000 bpf-forSigned-off-by: Puranjay Mohan Signed-off-by: Andrii Nakryiko Link: https://lore.kernel.org/bpf/20260804134601.2305303-7-puranjay@kernel.org List of files: /linux/tools/testing/selftests/bpf/Makefile

e2baf9cc374d5374e28702cb40e78551e82dd183 - selftests/xsk: Decouple xskxceiver and xdp apps from test_progs objects

Tue, 28 Jul 2026 13:50:36 +0200

selftests/xsk: Decouple xskxceiver and xdp apps from test_progs objectsBuild xskxceiver, xdp_hw_metadata, and xdp_features from explicit sourcelists instead of reusing helper objects produced by test_progs rules.Reusing shared objects such as network_helpers.o and xsk.o can pull intest_progs-only dependency chains and trigger unrelated libarena buildswhen invoking a single target.Keep these standalone binaries self-contained so each target builds onlyits own required sources and BPF skeleton dependencies.Signed-off-by: Tushar Vyavahare Signed-off-by: Andrii Nakryiko Tested-by: Maciej Fijalkowski Reviewed-by: Maciej Fijalkowski Link: https://lore.kernel.org/bpf/20260728115036.2049536-1-tushar.vyavahare@intel.com List of files: /linux/tools/testing/selftests/bpf/Makefile

7c25590d03abcb5424723f90641fda5b6cefffc8 - Merge branch 'selftests-bpf-a-few-edge-case-fixes'

Tue, 21 Jul 2026 19:27:15 +0200

Merge branch 'selftests-bpf-a-few-edge-case-fixes'Ricardo B. Marlière says:====================selftests/bpf: A few edge case fixesHi,Please consider merging the following fixes, found by means of targetingBPF selftests through openQA [1].[1]: e.g. https://openqa.opensuse.org/tests/60877031/4 ("libbpf: Search /lib64 and /lib in resolve_full_path()")- Hit by testing an older SLES root filesystem.2/4 ("selftests/bpf: Fix lsm_bdev dev_t encoding mismatch")- https://openqa.opensuse.org/tests/6087703/logfile?filename=test_progs.tap.txt#line-27063/4 ("selftests/bpf: Install resolve_btfids.test.o.BTF where the test expects it")- https://openqa.opensuse.org/tests/6087703/logfile?filename=test_progs.tap.txt#line-33324/4 ("selftests/bpf: Install bpftool where test_progs expects to find it")- https://openqa.opensuse.org/tests/6087703/logfile?filename=test_progs.tap.txt#line-806- https://openqa.opensuse.org/tests/6087703#step/test_bpftool_build_sh/1- https://openqa.opensuse.org/tests/6087703#step/test_doc_build_sh/1The build process is done at runtime with BPF_STRICT_BUILD=0:https://openqa.opensuse.org/tests/6087703/logfile?filename=serial_terminal.txt#line-1937Assisted-by: Claude Sonnet 5Signed-off-by: Ricardo B. Marlière ---Changes in v2:- Squashed first 2 commits- Removed redundant copy of bpftool due to TEST_GEN_PROGS_EXTENDED- Installed *.BTF instead of only resolve_btfids.test.o.BTF- Link to v1: https://patch.msgid.link/20260710-selftests-bpf_fixes-v1-0-aa24dfd6f4f9@suse.comTo: Andrii Nakryiko To: Eduard Zingerman To: Alexei Starovoitov To: Daniel Borkmann To: Kumar Kartikeya Dwivedi To: Martin KaFai Lau To: Song Liu To: Yonghong Song To: Jiri Olsa To: Emil Tsalapatis To: Shuah Khan To: "Alexis Lothoré (eBPF Foundation)" To: Ihor Solodrai To: Christian Brauner Cc: bpf@vger.kernel.orgCc: linux-kselftest@vger.kernel.orgCc: linux-kernel@vger.kernel.org---Ricardo B. Marlière (3): selftests/bpf: Fix make install target selftests/bpf: Fix lsm_bdev dev_t encoding mismatch libbpf: Search /lib64 and /lib in resolve_full_path() tools/lib/bpf/libbpf.c | 3 ++- tools/testing/selftests/bpf/Makefile | 7 ++++--- tools/testing/selftests/bpf/prog_tests/lsm_bdev.c | 3 ++- 3 files changed, 8 insertions(+), 5 deletions(-)---base-commit: 1590cf0329716306e948a8fc29f1d3ee87d3989fchange-id: 20260710-selftests-bpf_fixes-06e9a2eb3c67Best regards,--Ricardo B. Marlière ====================Link: https://patch.msgid.link/20260720-selftests-bpf_fixes-v2-0-b450eda93dfe@suse.comSigned-off-by: Kumar Kartikeya Dwivedi List of files: /linux/tools/testing/selftests/bpf/Makefile

0b236ac75d04a235f3574a2208941b22c1e7a965 - selftests/bpf: Fix make install target

Mon, 20 Jul 2026 13:13:07 +0200

selftests/bpf: Fix make install targetAfter "make install", test_progs fails because two files end up in thewrong place:- bpftool: TEST_GEN_PROGS_EXTENDED flattens it into $(INSTALL_PATH), losing the tools/sbin/ prefix that detect_bpftool_path() expects. Remove it from TEST_GEN_PROGS_EXTENDED and install it explicitly under tools/sbin/ instead.- *.BTF: resolve_btfids writes resolve_btfids.test.o.BTF as a side-effect of the build but INSTALL_RULE never copies it over. Install all *.BTF files alongside the rest of the per-flavor output.Fixes: f21fae577446 ("selftests/bpf: Add a few helpers for bpftool testing")Fixes: 522397d05e7d ("resolve_btfids: Change in-place update with raw binary output")Signed-off-by: Ricardo B. Marlière Acked-by: Ihor Solodrai Link: https://lore.kernel.org/bpf/20260720-selftests-bpf_fixes-v2-1-b450eda93dfe@suse.comSigned-off-by: Kumar Kartikeya Dwivedi List of files: /linux/tools/testing/selftests/bpf/Makefile

0eaed89c18aeedf0898baf2dbf5ff027c6795152 - Merge tag 'timers-v7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux into timers/clocksource

Mon, 17 Aug 2026 10:29:52 +0200

Merge tag 'timers-v7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux into timers/clocksource - Use designated initializers for sh_mtu2, sh_cmt, and sh_tmu, and drop the unused initializer in the platform_device_id table for sh_mtu2 (Uwe Kleine-König) - Remove redundant dev_err()/dev_err_probe() messages when devm_request_*_irq() fails, as the helper already logs an error message (Pan Chuang) - Fix a boot hang on Allwinner D1 when a forced minimum delta is used with the sun4i timer (Felix Yan) - Fix an IRQ leak in the cpuhp_setup_state() error path by freeing the IRQ on failure in the NXP PIT driver (WenTao Liang) - Fix incorrect unmapping of shared MMIO between the clocksource and clockevent drivers. If one of them fails to initialize, the error path unmaps the shared MMIO region, leaving the other driver with an invalid mapping on clps711x (Guangshuo Li) - Make the samsung_pwm driver compatible with PREEMPT_RT by replacing regular spinlocks with raw_spinlock_t in atomic contexts (Marek Szyprowski) - Use __raw_readl() and __raw_writel() instead of ioread32() and iowrite32() to support SWAP_IO_SPACE in the rtl-otto driver (Rustam Adilov) - Fix a missing clk_disable_unprepare() call in the timer initialization error path of the Armada driver (Yuho Choi)Link: https://lore.kernel.org/lkml/75feea31-683d-45a1-87f4-ab045e0152ae@oss.qualcomm.com List of files: /linux/tools/testing/selftests/bpf/Makefile