| /linux/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
43 that hold open file descriptors (FDs) against BTF objects. On such kernels
47 Dump BTF entries from a given *BTF_SRC*.
49 When **id** is specified, BTF object with that ID will be loaded and all
50 its BTF types emitted.
52 When **map** is provided, it's expected that map has associated BTF object
53 with BTF types describing key and value. It's possible to select whether to
[all …]
|
| H A D | bpftool-prog.rst | 157 The **kernel_btf** option allows specifying an external BTF file to replace
158 the system's own vmlinux BTF file for CO-RE relocations. Note that any
159 other feature relying on BTF (such as fentry/fexit programs, struct_ops)
160 requires the BTF file for the actual kernel running on the host, often
247 the **bpf_trace_printk**\ () helper to log each step of loading BTF,
|
| H A D | bpftool.rst | 45 *BTF-COMMANDS* := { **show** | **list** | **dump** | **help** }
|
| /linux/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/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
93 It also chooses the fetch type from BTF information. For example, in the above
120 BTF also affects the ``$retval``. If user doesn't set any type, the retval
121 type is automatically picked from the BTF. If the function returns ``void``,
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
[all …]
|
| /linux/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/Documentation/bpf/ |
| 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
132 ``.BTF.ext`` sections. For cases like bcc where llvm ``ExecutionEngine RuntimeDyld``
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
[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 | 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.
|
| H A D | prog_lsm.rst | 43 This can be further simplified (if one has access to the BTF information at
|
| /linux/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/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.
74 [BTF](https://docs.kernel.org/bpf/btf.html) (i.e. with the BTF-related Kconfig
78 compiled with BTF as follows:
84 `bpftool` analyzes all of the BTF encodings in the binary, and produces a
233 vmlinux built with BTF, and with sched_ext support enabled. If you don't,
|
| /linux/arch/s390/configs/ |
| H A D | btf.config | 1 # Help: Enable BTF debug info
|
| /linux/include/asm-generic/ |
| H A D | vmlinux.lds.h | 563 BTF \
686 #define BTF \ macro
688 .BTF : AT(ADDR(.BTF) - LOAD_OFFSET) { \
689 BOUNDED_SECTION_BY(.BTF, _BTF) \
696 #define BTF macro
|
| /linux/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/scripts/ |
| H A D | Makefile.modfinal | 41 quiet_cmd_btf_ko = BTF [M] $@
44 printf "Skipping BTF generation for %s due to unavailability of vmlinux\n" $@ 1>&2; \
|
| H A D | link-vmlinux.sh | 212 info BTF .tmp_vmlinux1
|
| /linux/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/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/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/scripts/livepatch/ |
| H A D | klp-build | 786 objcopy --remove-section=.BTF "$kmod_file"
|
| /linux/tools/perf/Documentation/ |
| H A D | perf.data-file-format.txt | 364 Contains BPF Type Format (BTF). For more information about BTF, please
|
| /linux/lib/ |
| H A D | Kconfig.debug | 399 bool "Generate BTF type information"
407 Generate deduplicated BTF type information from DWARF debug info.
409 DWARF type info into equivalent deduplicated BTF type info.
429 bool "Generate BTF type information for kernel modules"
433 Generate compact split BTF type information for kernel modules.
436 bool "Allow loading modules with non-matching BTF type info"
439 For modules whose split BTF does not match vmlinux, load without
440 BTF rather than refusing to load. The default behavior with
441 module BTF enabled is to reject modules with such mismatches;
442 this option will still load module BTF where possible but ignore
[all …]
|