Lines Matching full:kernel

20 tree](https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next) under
22 libbpf changes should be sent to [BPF mailing list](http://vger.kernel.org/vger-lists.html#bpf),
43 All general BPF questions, including kernel functionality, libbpf APIs and
44 their application, should be sent to bpf@vger.kernel.org mailing list. You can
45 subscribe to it [here](http://vger.kernel.org/vger-lists.html#bpf) and search
46 its archive [here](https://lore.kernel.org/bpf/). Please search the archive
50 bpf@vger.kernel.org is monitored by many more people and they will happily try
93 being deployed to target servers and doesn't rely on kernel-devel headers
96 It does rely on kernel to be built with [BTF type
97 information](https://www.kernel.org/doc/html/latest/bpf/btf.html), though.
98 Some major Linux distributions come with kernel BTF already built in:
102   - Arch Linux (from kernel 5.7.1.arch1-1)
103   - Manjaro (from kernel 5.4 if compiled after 2021-06-18)
107 If your kernel doesn't come with BTF built-in, you'll need to build custom
108 kernel. You'll need:
111   - kernel built with `CONFIG_DEBUG_INFO_BTF=y` option;
112   - you can check if your kernel has BTF built-in by looking for
113     `/sys/kernel/btf/vmlinux` file:
116 $ ls -la /sys/kernel/btf/vmlinux
117 -r--r--r--. 1 root root 3541561 Jun  2 18:16 /sys/kernel/btf/vmlinux
152 Benefits of packaging from the mirror over packaging from kernel sources:
154   - No ties to any specific kernel, transparent handling of older kernels.
155     Libbpf is designed to be kernel-agnostic and work across multitude of
156     kernel versions. It has built-in mechanisms to gracefully handle older
159     kernel version and can/should be packaged and versioned independently.
175 All the gory details of syncing can be found in `scripts/sync-kernel.sh`
180 [bpf-next](https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/)'s