Lines Matching refs:Q
2 BPF Design Q&A
18 Q: Is BPF a generic instruction set similar to x64 and arm64?
22 Q: Is BPF a generic virtual machine ?
29 Q: Why C calling convention was chosen?
39 Q: Can multiple return values be supported in the future?
43 Q: Can more than 5 function arguments be supported in the future?
49 Q: Can BPF programs access instruction pointer or return address?
53 Q: Can BPF programs access stack pointer ?
62 Q: Does C-calling convention diminishes possible use cases?
74 Q: Does it mean that 'innovative' extensions to BPF code are disallowed?
83 Q: Can loops be supported in a safe way?
90 Q: What are the verifier limits?
119 Q: LD_ABS and LD_IND instructions vs C code
122 Q: How come LD_ABS and LD_IND instruction are present in BPF whereas
129 Q: BPF instructions mapping not one-to-one to native CPU
131 Q: It seems not all BPF instructions are one-to-one to native CPU.
137 Q: Why BPF_DIV instruction doesn't map to x64 div?
143 Q: Why there is no BPF_SDIV for signed divide operation?
148 Q: Why BPF has implicit prologue and epilogue?
157 Q: Why BPF_JLT and BPF_JLE instructions were not introduced in the beginning?
168 Q: BPF 32-bit subregister requirements
170 Q: BPF 32-bit subregisters have a requirement to zero upper 32-bits of BPF
201 Q: Does BPF have a stable ABI?
211 Q: Are tracepoints part of the stable ABI?
217 Q: How much stack space a BPF program uses?
223 Q: Can BPF be offloaded to HW?
227 Q: Does classic BPF interpreter still exist?
231 Q: Can BPF call arbitrary kernel functions?
236 Q: Can BPF overwrite arbitrary kernel memory?
245 Q: Can BPF overwrite arbitrary user memory?
255 Q: New functionality via kernel modules?
257 Q: Can BPF functionality such as new program or map types, new
262 Q: Directly calling kernel function is an ABI?
264 Q: Some kernel functions (e.g. tcp_slow_start) can be called