Lines Matching refs:programs

32 A: Because BPF programs are designed to run in the linux kernel
49 Q: Can BPF programs access instruction pointer or return address?
53 Q: Can BPF programs access stack pointer ?
69 BPF programs and programs call kernel helpers with zero overhead,
71 for JITed BPF programs that are indistinguishable from
112 versions will accept all bpf programs that were accepted by
155 workaround would be acceptable. Turned out that programs lose performance
174 programs for 32-bit architectures.
198 A: YES. BPF instructions, arguments to BPF programs, set of helper
200 of ABI. However there is one specific exception to tracing programs
213 subject to change and can break with newer kernels. BPF programs need to change
220 newer kernels. BPF programs need to change accordingly when this happens.
234 A: NO. Classic BPF programs are converted into extend BPF instructions.
238 A: NO. BPF programs can only call specific functions exposed as BPF helpers or
245 Tracing bpf programs can *read* arbitrary memory with bpf_probe_read()
246 and bpf_probe_read_str() helpers. Networking programs cannot read
254 Tracing BPF programs can overwrite the user memory
258 Tracing BPF programs are root only.
268 added to by modules. However, modules can expose functionality to BPF programs
275 by BPF programs.  Do these kernel functions become an ABI?
279 The kernel function protos will change and the bpf programs will be
285 programs and they have to be adjusted accordingly. See
290 Q: BPF programs can be attached to many kernel functions.  Do these
295 The kernel function prototypes will change, and BPF programs attaching to
297 should be used in order to make it easier to adapt your BPF programs to
331 kernel releases. The users must adapt their BPF programs to the new changes and
332 update them to make sure their programs continue to work correctly.
335 order to introduce more special fields in the future. Hence, user programs must