Lines Matching refs:object
21 *COMMAND* := { **object** | **skeleton** | **help** }
26 | **bpftool** **gen object** *OUTPUT_FILE* *INPUT_FILE* [*INPUT_FILE*...]
34 bpftool gen object *OUTPUT_FILE* *INPUT_FILE* [*INPUT_FILE*...]
36 resulting *OUTPUT_FILE*. All the files involved are BPF ELF object files.
39 object files, but in addition to combining data and instruction sections,
46 compiled files that are then linked into a single resulting BPF object
57 side. Generated code is tailored to specific input BPF object *FILE*,
66 within BPF object. When requested, supported BPF programs will be
78 BPF object is loaded and verified by kernel. For non-read-only variables,
82 During skeleton generation, contents of source BPF object *FILE* is
84 This ensures skeleton and BPF object file are matching 1-to-1 and always
90 skeleton API to create and load BPF object, and later use libbpf APIs to
94 prefixed with object name. Object name can either be derived from object
95 file name, i.e., if BPF object file name is **example.o**, BPF object name
98 provided (assuming **example** as the object name):
115 already loaded BPF object. Only BPF programs of types supported by libbpf
124 skeleton and BPF object.
126 If BPF object has global variables, corresponding structs with memory
140 object file used to generate them is already loaded into a *bpf_object* by
163 loading an eBPF object, has to rely on external BTF files to be able to
275 **$ bpftool gen object example.bpf.o example1.bpf.o example2.bpf.o example3.bpf.o**
278 *example3.bpf.c* individually and then statically links respective object
279 files into the final BPF ELF object file *example.bpf.o*.
459 when loading the "one.bpf.o" object into the "5.4.0-example" kernel. Note that