Changes in libbpf_version.h

74975e13 - libbpf: start v1.6 development cycle

Tue, 29 Oct 2024 18:40:45 +0000

libbpf: start v1.6 development cycleWith libbpf v1.5.0 release out, start v1.6 dev cycle.Signed-off-by: Andrii Nakryiko Link: https://lore.kernel.org/r/20241029184045.581537-1-andrii@kernel.orgSigned-off-by: Alexei Starovoitov List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h

5bd2ed65 - libbpf: Start v1.5 development cycle

Sat, 06 Apr 2024 09:15:41 +0000

libbpf: Start v1.5 development cycleBump libbpf.map to v1.5.0 to start a new libbpf version cycle.Signed-off-by: Andrea Righi Signed-off-by: Andrii Nakryiko Link: https://lore.kernel.org/bpf/20240406092005.92399-2-andrea.righi@canonical.com List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h

b8d78cb2 - libbpf: Start v1.4 development cycle

Thu, 23 Nov 2023 00:04:39 +0000

libbpf: Start v1.4 development cycleBump libbpf.map to v1.4.0 to start a new libbpf version cycle.Signed-off-by: Eduard Zingerman Signed-off-by: Daniel Borkmann Link: https://lore.kernel.org/bpf/20231123000439.12025-1-eddyz87@gmail.com List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h

2b001b94 - libbpf: Start v1.3 development cycle

Tue, 23 May 2023 17:00:11 +0000

libbpf: Start v1.3 development cycleBump libbpf.map to v1.3.0 to start a new libbpf version cycle.Signed-off-by: Andrii Nakryiko Signed-off-by: Daniel Borkmann Link: https://lore.kernel.org/bpf/20230523170013.728457-3-andrii@kernel.org List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h

4ec38eda - libbpf: start v1.2 development cycle

Wed, 21 Dec 2022 18:00:49 +0000

libbpf: start v1.2 development cycleBump current version for new development cycle to v1.2.Signed-off-by: Andrii Nakryiko Acked-by: Stanislav Fomichev Link: https://lore.kernel.org/r/20221221180049.853365-1-andrii@kernel.orgSigned-off-by: Martin KaFai Lau List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h

b66ccae0 - bpf: Add libbpf logic for user-space ring buffer

Tue, 20 Sep 2022 00:00:59 +0000

bpf: Add libbpf logic for user-space ring bufferNow that all of the logic is in place in the kernel to support user-spaceproduced ring buffers, we can add the user-space logic to libbpf. Thispatch therefore adds the following public symbols to libbpf:struct user_ring_buffer *user_ring_buffer__new(int map_fd, const struct user_ring_buffer_opts *opts);void *user_ring_buffer__reserve(struct user_ring_buffer *rb, __u32 size);void *user_ring_buffer__reserve_blocking(struct user_ring_buffer *rb, __u32 size, int timeout_ms);void user_ring_buffer__submit(struct user_ring_buffer *rb, void *sample);void user_ring_buffer__discard(struct user_ring_buffer *rb,void user_ring_buffer__free(struct user_ring_buffer *rb);A user-space producer must first create a struct user_ring_buffer * objectwith user_ring_buffer__new(), and can then reserve samples in thering buffer using one of the following two symbols:void *user_ring_buffer__reserve(struct user_ring_buffer *rb, __u32 size);void *user_ring_buffer__reserve_blocking(struct user_ring_buffer *rb, __u32 size, int timeout_ms);With user_ring_buffer__reserve(), a pointer to a 'size' region of the ringbuffer will be returned if sufficient space is available in the buffer.user_ring_buffer__reserve_blocking() provides similar semantics, but willblock for up to 'timeout_ms' in epoll_wait if there is insufficient spacein the buffer. This function has the guarantee from the kernel that it willreceive at least one event-notification per invocation tobpf_ringbuf_drain(), provided that at least one sample is drained, and theBPF program did not pass the BPF_RB_NO_WAKEUP flag to bpf_ringbuf_drain().Once a sample is reserved, it must either be committed to the ring bufferwith user_ring_buffer__submit(), or discarded withuser_ring_buffer__discard().Signed-off-by: David Vernet Signed-off-by: Andrii Nakryiko Link: https://lore.kernel.org/bpf/20220920000100.477320-4-void@manifault.com List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h

e2371b16 - libbpf: start 1.0 development cycle

Wed, 18 May 2022 18:59:14 +0000

libbpf: start 1.0 development cycleStart libbpf 1.0 development cycle by adding LIBBPF_1.0.0 section tolibbpf.map file and marking all current symbols as local. As we removeall the deprecated APIs we'll populate global list before the final 1.0release.Signed-off-by: Andrii Nakryiko Link: https://lore.kernel.org/r/20220518185915.3529475-3-andrii@kernel.orgSigned-off-by: Alexei Starovoitov List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h

697f104d - libbpf: Support custom SEC() handlers

Sat, 05 Mar 2022 01:01:28 +0000

libbpf: Support custom SEC() handlersAllow registering and unregistering custom handlers for BPF program.This allows user applications and libraries to plug into libbpf'sdeclarative SEC() definition handling logic. This allows to offloadcomplex and intricate custom logic into external libraries, but stillprovide a great user experience.One such example is USDT handling library, which has a lot of code andcomplexity which doesn't make sense to put into libbpf directly, but itwould be really great for users to be able to specify BPF programs withsomething like SEC("usdt/::")and have correct BPF program type set (BPF_PROGRAM_TYPE_KPROBE, as it isuprobe) and even support BPF skeleton's auto-attach logic.In some cases, it might be even good idea to override libbpf's defaulthandling, like for SEC("perf_event") programs. With custom library, it'spossible to extend logic to support specifying perf event specificationright there in SEC() definition without burdening libbpf with lots ofcustom logic or extra library dependecies (e.g., libpfm4). With currentpatch it's possible to override libbpf's SEC("perf_event") handling andspecify a completely custom ones.Further, it's possible to specify a generic fallback handling for anySEC() that doesn't match any other custom or standard libbpf handlers.This allows to accommodate whatever legacy use cases there might be, ifnecessary.See doc comments for libbpf_register_prog_handler() andlibbpf_unregister_prog_handler() for detailed semantics.This patch also bumps libbpf development version to v0.8 and adds newAPIs there.Signed-off-by: Andrii Nakryiko Signed-off-by: Alexei Starovoitov Tested-by: Alan Maguire Reviewed-by: Alan Maguire Link: https://lore.kernel.org/bpf/20220305010129.1549719-3-andrii@kernel.org List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h

dbdd2c7f - libbpf: Add API to get/set log_level at per-program level

Wed, 01 Dec 2021 23:28:17 +0000

libbpf: Add API to get/set log_level at per-program levelAdd bpf_program__set_log_level() and bpf_program__log_level() to fetchand adjust log_level sent during BPF_PROG_LOAD command. This allows toselectively request more or less verbose output in BPF verifier log.Also bump libbpf version to 0.7 and make these APIs the first in v0.7.Signed-off-by: Andrii Nakryiko Signed-off-by: Alexei Starovoitov Link: https://lore.kernel.org/bpf/20211201232824.3166325-3-andrii@kernel.org List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h

2f383041 - libbpf: Make libbpf_version.h non-auto-generated

Mon, 13 Sep 2021 22:23:09 +0000

libbpf: Make libbpf_version.h non-auto-generatedTurn previously auto-generated libbpf_version.h header into a normalheader file. This prevents various tricky Makefile integration issues,simplifies the overall build process, but also allows to further extendit with some more versioning-related APIs in the future.To prevent accidental out-of-sync versions as defined by libbpf.map andlibbpf_version.h, Makefile checks their consistency at build time.Simultaneously with this change bump libbpf.map to v0.6.Also undo adding libbpf's output directory into include path forkernel/bpf/preload, bpftool, and resolve_btfids, which is not necessarybecause libbpf_version.h is just a normal header like any other.Fixes: 0b46b7550560 ("libbpf: Add LIBBPF_DEPRECATED_SINCE macro for scheduling API deprecations")Signed-off-by: Andrii Nakryiko Signed-off-by: Alexei Starovoitov Link: https://lore.kernel.org/bpf/20210913222309.3220849-1-andrii@kernel.org List of files: /linux-6.15/tools/lib/bpf/libbpf_version.h