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?
94 Q: LD_ABS and LD_IND instructions vs C code
97 Q: How come LD_ABS and LD_IND instruction are present in BPF whereas
104 Q: BPF instructions mapping not one-to-one to native CPU
106 Q: It seems not all BPF instructions are one-to-one to native CPU.
112 Q: why BPF_DIV instruction doesn't map to x64 div?
118 Q: why there is no BPF_SDIV for signed divide operation?
123 Q: Why BPF has implicit prologue and epilogue?
132 Q: Why BPF_JLT and BPF_JLE instructions were not introduced in the beginning?
143 Q: BPF 32-bit subregister requirements
145 Q: BPF 32-bit subregisters have a requirement to zero upper 32-bits of BPF
156 Q: Does BPF have a stable ABI?
167 Q: How much stack space a BPF program uses?
173 Q: Can BPF be offloaded to HW?
177 Q: Does classic BPF interpreter still exist?
181 Q: Can BPF call arbitrary kernel functions?
186 Q: Can BPF overwrite arbitrary kernel memory?
195 Q: Can BPF overwrite arbitrary user memory?
205 Q: bpf_trace_printk() helper warning
207 Q: When bpf_trace_printk() helper is used the kernel prints nasty
216 Q: New functionality via kernel modules?
218 Q: Can BPF functionality such as new program or map types, new