| /linux-6.15/tools/bpf/bpftool/Documentation/ |
| H A D | bpftool-btf.rst | 7 tool for inspection of BTF data 23 BTF COMMANDS 38 Show information about loaded BTF objects. If a BTF ID is specified, show 39 information only about given BTF object, otherwise list all BTF objects 47 Dump BTF entries from a given *BTF_SRC*. 50 its BTF types emitted. 55 both key and value (**kv**), or all BTF types present in associated BTF 59 object with BTF types. 83 Pass a base BTF object. Base BTF objects are typically used with BTF 87 base BTF reference should usually point to the kernel BTF. [all …]
|
| H A D | bpftool-gen.rst | 40 .BTF and .BTF.ext (if present in any of the input files) data are combined 41 together. .BTF data is deduplicated, so all the common types across 42 *INPUT_FILE*'s will only be represented once in the resulting BTF 158 Generate a minimum BTF file as *OUTPUT*, derived from a given *INPUT* BTF 159 file, containing all needed BTF types so one, or more, given eBPF objects 163 loading an eBPF object, has to rely on external BTF files to be able to 166 Usually, an external BTF file is built from existing kernel DWARF data 170 The min_core_btf feature builds smaller BTF files, customized to one or 458 Now, the "5.4.0-smaller.btf" file may be used by libbpf as an external BTF file 460 the generated BTF file won't allow other eBPF objects to be loaded, just the
|
| H A D | bpftool.rst | 45 *BTF-COMMANDS* := { **show** | **list** | **dump** | **help** }
|
| /linux-6.15/Documentation/bpf/ |
| H A D | btf.rst | 2 BPF Type Format (BTF) 19 * BTF kernel API 20 * BTF ELF file format 600 3. BTF Kernel API 764 4.1 .BTF section 924 base BTF refers to it using its base BTF ID, and split BTF IDs start 930 .BTF.base section is to make split BTF more resilient for cases where 968 If we relocate the split BTF later using the following new base BTF:: 981 Note that we had to update BTF ID and start BTF ID for the split BTF. 991 5. Using BTF [all …]
|
| H A D | llvm_reloc.rst | 114 4 R_BPF_64_NODYLD32 .BTF[.ext] data 32 r_offset S + A 131 But ``R_BPF_64_NODYLD32`` specifically refers to relocations in ``.BTF`` and 134 to actual function/variable address. Otherwise, ``.BTF`` and ``.BTF.ext`` 233 The .BTF/.BTF.ext sections has R_BPF_64_NODYLD32 relocations:: 235 Relocation section '.rel.BTF' at offset 0x538 contains 1 entries: 239 Relocation section '.rel.BTF.ext' at offset 0x548 contains 2 entries: 252 related to ELF relocations and are encoded in .BTF.ext section. 254 information on .BTF.ext structure. 364 * ``type_id`` - BTF type ID of the "root" (containing) entity of a 367 * ``access_str_off`` - offset into corresponding .BTF string section. [all …]
|
| H A D | drgn.rst | 35 List BPF programs (full names are obtained from BTF):: 71 that has BTF id 16 in BPF program id 650, name ``test_pkt_access``.
|
| H A D | linux-notes.rst | 43 On Linux, this integer is a BTF ID.
|
| H A D | kfuncs.rst | 93 ID in program's BTF and return a sized pointer to it. Each type ID will have a 185 This set encodes the BTF ID of each kfunc listed above, and encodes the flags 235 BTF objects have been passed in their unmodified form (that is, at a zero 244 Pointers to non-BTF objects (e.g. scalar pointers) may also be passed to 287 that it appears in BTF. For example, ``BTF_TYPE_SAFE_TRUSTED(struct socket)`` 369 The verifier will always enforce that the BTF type of a pointer passed to a
|
| H A D | prog_lsm.rst | 43 This can be further simplified (if one has access to the BTF information at
|
| H A D | bpf_design_QA.rst | 310 values (when using BTF support for BPF maps). This allows to use helpers for 312 pointers to some kernel types (with __kptr_untrusted and __kptr BTF tags). Will the 338 in BTF with 'bpf\_' prefix.
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-btf | 6 Contains BTF type information and related data for kernel and 14 Read-only binary attribute exposing kernel's own BTF type 24 Read-only binary attribute exposing kernel module's BTF type 25 information as an add-on to the kernel's BTF (/sys/kernel/btf/vmlinux).
|
| /linux-6.15/Documentation/trace/ |
| H A D | fprobetrace.rst | 44 ARG : Fetch "ARG" function argument using BTF (only for function 61 (\*1) This is available only when BTF is enabled. 81 BTF arguments 83 BTF (BPF Type Format) argument allows user to trace function and tracepoint 86 If user only specify the BTF argument, the event's argument name is also 120 BTF also affects the ``$retval``. If user doesn't set any type, the retval 146 For these BTF arguments and fields, ``:string`` and ``:ustring`` change the 147 behavior. If these are used for BTF argument or field, it checks whether 149 or not. If not, it rejects applying the string types. Also, with the BTF 152 dereference operator according to the BTF type. e.g. :: [all …]
|
| /linux-6.15/Documentation/admin-guide/media/ |
| H A D | tuner-cardlist.rst | 92 84 Sony BTF-Pxn01Z 97 89 Sony BTF-PG472Z PAL/SECAM 98 90 Sony BTF-PK467Z NTSC-M-JP 99 91 Sony BTF-PB463Z NTSC-M
|
| /linux-6.15/scripts/ |
| H A D | link-vmlinux.sh | 117 info BTF "${btf_data}" 125 ${OBJCOPY} --only-section=.BTF --set-section-flags .BTF=alloc,readonly \
|
| H A D | Makefile.modfinal | 37 quiet_cmd_btf_ko = BTF [M] $@
|
| /linux-6.15/Documentation/bpf/libbpf/ |
| H A D | libbpf_naming_convention.rst | 52 All objects and corresponding functions other than BTF related should go 53 to ``libbpf.h``. BTF types and functions should go to ``btf.h``. 158 * @brief **btf__new()** creates a new instance of a BTF object from the raw 159 * bytes of an ELF's BTF section 162 * @return new BTF object instance which has to be eventually freed with
|
| H A D | libbpf_overview.rst | 141 BPF CO-RE brings together BTF type information, libbpf, and the compiler to 145 To make BPF programs portable libbpf relies on the BTF type information of the 146 running kernel. Kernel also exposes this self-describing authoritative BTF 149 You can generate the BTF information for the running kernel with the following 157 (:doc:`BTF types <../btf>`) that the running kernel uses. Including 162 recorded BTF type and relocation information and matching them to BTF
|
| /linux-6.15/arch/s390/configs/ |
| H A D | btf.config | 1 # Help: Enable BTF debug info
|
| /linux-6.15/tools/sched_ext/ |
| H A D | README.md | 33 missing some features such as BTF type tags which are necessary for using 38 You may need pahole in order to generate BTF from DWARF. 81 [BTF](https://docs.kernel.org/bpf/btf.html) (i.e. with the BTF-related Kconfig 85 compiled with BTF as follows: 91 `bpftool` analyzes all of the BTF encodings in the binary, and produces a 240 vmlinux built with BTF, and with sched_ext support enabled. If you don't,
|
| /linux-6.15/include/asm-generic/ |
| H A D | vmlinux.lds.h | 545 BTF \ 669 #define BTF \ macro 670 .BTF : AT(ADDR(.BTF) - LOAD_OFFSET) { \ 671 BOUNDED_SECTION_BY(.BTF, _BTF) \ 678 #define BTF macro
|
| /linux-6.15/samples/hid/ |
| H A D | Makefile | 86 BTF_PAHOLE_PROBE := $(shell $(BTF_PAHOLE) --help 2>&1 | grep BTF) 90 $(LLVM_READELF) -S ./llvm_btf_verify.o | grep BTF; \
|
| /linux-6.15/tools/testing/selftests/bpf/ |
| H A D | README.rst | 265 either crash when compiling these tests, or generate an incorrect BTF. 273 to generate extern function in BTF. It was introduced in `Clang 13`__. 279 libbpf: failed to find BTF for extern 'tcp_slow_start' [25] section: -2 304 generate valid BTF information for weak variables. Please make sure you use
|
| /linux-6.15/samples/bpf/ |
| H A D | Makefile | 203 BTF_PAHOLE_PROBE := $(shell $(BTF_PAHOLE) --help 2>&1 | grep BTF) 207 $(LLVM_READELF) -S ./llvm_btf_verify.o | grep BTF; \
|
| /linux-6.15/Documentation/bpf/standardization/ |
| H A D | instruction-set.rst | 509 …CALL 0x8 0x2 call helper function by BTF ID {CALL, K, JMP} only, see `Helper func… 563 Platforms that support the BPF Type Format (BTF) support identifying 564 a helper function by a BTF ID encoded in the 'imm' field, where the BTF ID 565 identifies the helper name and type. Further documentation of BTF
|
| /linux-6.15/tools/perf/Documentation/ |
| H A D | perf-trace.txt | 244 by default and use BTF when available, as well as use functions to do pretty 250 printers. This option is intended for testing BTF integration in perf trace. btf_dump-based
|