Lines Matching refs:BTF

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
54     dump only BTF type(s) associated with key (**key**), value (**value**),
55     both key and value (**kv**), or all BTF types present in associated BTF
58     When **prog** is provided, it's expected that program has associated BTF
59     object with BTF types.
61     When specifying *FILE*, an ELF file is expected, containing .BTF section
62     with well-defined BTF binary format data, typically produced by clang or
72     (such as the "key", "value", or "kv" arguments when dumping BTF for a map).
83     Pass a base BTF object. Base BTF objects are typically used with BTF
85     required by modules, BTF objects for modules are "split", they are
86     built incrementally on top of the kernel (vmlinux) BTF object. So the
87     base BTF reference should usually point to the kernel BTF.
89     When the main BTF object to process (for example, the module BTF to
92     BTF object is passed through other handles, this option becomes
109 This gives an example of default output for all supported BTF kinds.
195 The following commands print BTF types associated with specified map's key,
196 value, both key and value, and all BTF types, respectively. By default, both