bpftool/Documentation/bpftool-prog.rst

76     Output will start with program ID followed by program type and zero or more
80     the total time spent running the program, and the number of times it was
83     program run. Activation or deactivation of the feature is performed via the
98     *PROG* must match a single program.
112     Dump jited image (host machine code) of the program.
115     be disassembled and printed to stdout. *PROG* must match a single program
125     Pin program *PROG* as *FILE*.
131     Load bpf program(s) from binary *OBJ* and pin as *PATH*. **bpftool prog
132     load** pins only the first program from the *OBJ* as *PATH*. **bpftool prog
134     is optional, if not specified program type will be inferred from section
141     **offload_dev** *NAME* is specified program will be loaded onto given
142     networking device (offload). If **xdpmeta_dev** *NAME* is specified program
147     If **autoattach** is specified program will be attached before pin. In that
148     case, only the link (representing the program attached to its hook) is
149     pinned, not the program as such, so the path won't show in **bpftool prog
152     object file, in particular, it's not supported for all program types. If a
153     program does not support autoattach, bpftool falls back to regular pinning
154     for that program instead.
160     Attach bpf program *PROG* (with type specified by *ATTACH_TYPE*). Most
165     Detach bpf program *PROG* (with type specified by *ATTACH_TYPE*). Most
177     Run BPF program *PROG* in the kernel testing infrastructure for BPF,
178     meaning that the program works on the data and context provided by the
200     Not all program types support test run. Among those which do, not all of
202     perform checks on program types.
205     Profile *METRICs* for bpf program *PROG* for *DURATION* seconds or until
227     Load program as a "loader" program. This is useful to debug the generation
233     messages are generated, and the execution of the loader program will use