/openbmc/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 39 specified, show information only about given BTF object, 40 otherwise list all BTF objects currently loaded on the 44 processes that hold open file descriptors (FDs) against BTF 49 Dump BTF entries from a given *BTF_SRC*. 51 When **id** is specified, BTF object with that ID will be 52 loaded and all its BTF types emitted. 55 associated BTF object with BTF types describing key and [all …]
|
H A D | bpftool-gen.rst | 41 and instruction sections, .BTF and .BTF.ext (if present in 42 any of the input files) data are combined together. .BTF 45 BTF information. 179 Generate a minimum BTF file as *OUTPUT*, derived from a given 180 *INPUT* BTF file, containing all needed BTF types so one, or 185 BTF files to be able to calculate CO-RE relocations. 187 Usually, an external BTF file is built from existing kernel 191 The min_core_btf feature builds smaller BTF files, customized 434 Now, the "5.4.0-smaller.btf" file may be used by libbpf as an external BTF file 436 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** }
|
/openbmc/linux/Documentation/bpf/ |
H A D | btf.rst | 2 BPF Type Format (BTF) 8 BTF (BPF Type Format) is the metadata format which encodes the debug info 9 related to BPF program/map. The name BTF was used initially to describe data 10 types. The BTF was later extended to include function info for defined 18 The BTF specification contains two parts, 19 * BTF kernel API 20 * BTF ELF file format 23 verifies the BTF info before using it. The ELF file format is a user space 26 The type and string sections are part of the BTF kernel API, describing the 32 2. BTF Type and String Encoding [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 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 | kfuncs.rst | 42 "Global kfuncs as their definitions will be in BTF"); 95 ID in program's BTF and return a sized pointer to it. Each type ID will have a 163 This set encodes the BTF ID of each kfunc listed above, and encodes the flags 213 BTF objects have been passed in their unmodified form (that is, at a zero 222 Pointers to non-BTF objects (e.g. scalar pointers) may also be passed to 265 that it appears in BTF. For example, ``BTF_TYPE_SAFE_TRUSTED(struct socket)`` 347 The verifier will always enforce that the BTF type of a pointer passed to a
|
H A D | linux-notes.rst | 43 On Linux, this integer is a BTF ID.
|
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.
|
/openbmc/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).
|
/openbmc/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. 69 BTF arguments 71 BTF (BPF Type Format) argument allows user to trace function and tracepoint 74 If user only specify the BTF argument, the event's argument name is also 81 It also chooses the fetch type from BTF information. For example, in the above 108 BTF also affects the ``$retval``. If user doesn't set any type, the retval 109 type is automatically picked from the BTF. If the function returns ``void``, 134 For these BTF arguments and fields, ``:string`` and ``:ustring`` change the 135 behavior. If these are used for BTF argument or field, it checks whether [all …]
|
/openbmc/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
|
/openbmc/linux/tools/testing/selftests/bpf/ |
H A D | DENYLIST.s390x | 3 bloom_filter_map # failed to find kernel BTF type ID of '__x64_sys_getpgid'… 25 user_ringbuf # failed to find kernel BTF type ID of '__s390x_sys_prctl'…
|
H A D | README.rst | 235 either crash when compiling these tests, or generate an incorrect BTF. 243 to generate extern function in BTF. It was introduced in `Clang 13`__. 249 libbpf: failed to find BTF for extern 'tcp_slow_start' [25] section: -2 274 generate valid BTF information for weak variables. Please make sure you use
|
/openbmc/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
|
/openbmc/linux/arch/s390/configs/ |
H A D | btf.config | 1 # Help: Enable BTF debug info
|
/openbmc/linux/include/asm-generic/ |
H A D | vmlinux.lds.h | 529 BTF \ 630 * .BTF 633 #define BTF \ macro 634 .BTF : AT(ADDR(.BTF) - LOAD_OFFSET) { \ 635 BOUNDED_SECTION_BY(.BTF, _BTF) \ 642 #define BTF macro
|
/openbmc/linux/scripts/ |
H A D | link-vmlinux.sh | 135 ${OBJCOPY} --only-section=.BTF --set-section-flags .BTF=alloc,readonly \
|
H A D | Makefile.modfinal | 40 quiet_cmd_btf_ko = BTF [M] $@
|
/openbmc/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; \
|
/openbmc/qemu/qapi/ |
H A D | ebpf.json | 11 # map description(BTF). Overall, eBPF object should contain the
|
/openbmc/linux/samples/bpf/ |
H A D | Makefile | 223 BTF_PAHOLE_PROBE := $(shell $(BTF_PAHOLE) --help 2>&1 | grep BTF) 227 $(LLVM_READELF) -S ./llvm_btf_verify.o | grep BTF; \
|
/openbmc/linux/Documentation/bpf/standardization/ |
H A D | instruction-set.rst | 361 BPF_CALL 0x8 0x2 call helper function by BTF ID see `Helper functions`_ 403 Platforms that support the BPF Type Format (BTF) support identifying 404 a helper function by a BTF ID encoded in the imm field, where the BTF ID
|