Lines Matching refs:bpf
23 loader development happens through the bpf kernel mailing list,
27 bpf@vger.kernel.org
49 A: BPF CI is GitHub based and hosted at https://github.com/kernel-patches/bpf.
58 - Clone the fork locally, check out a new branch tracking either the bpf-next
59 or bpf branch, and apply your to-be-tested patches on top of it
62 kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively
68 Note furthermore that both base branches (bpf-next_base and bpf_base) will be
76 A: Please submit your BPF patches to the bpf kernel mailing list:
78 bpf@vger.kernel.org
92 Those patches which target BPF, are assigned to a 'bpf' delegate for
108 the 'bpf' delegate).
116 * https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/
117 * https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/
119 The bpf tree itself is for fixes only, whereas bpf-next for features,
121 analogous to net and net-next trees for networking. Both bpf and
122 bpf-next will only have a master branch in order to simplify against
125 Accumulated BPF patches in the bpf tree will regularly get pulled
127 into the bpf-next tree will make their way into net-next tree. net and
145 pull-request: bpf yyyy-mm-dd
146 pull-request: bpf-next yyyy-mm-dd
148 Q: How do I indicate which tree (bpf vs. bpf-next) my patch should be applied to?
155 maintainers know whether it is targeted at bpf or bpf-next.
157 For fixes eventually landing in bpf -> net tree, the subject must
160 git format-patch --subject-prefix='PATCH bpf' start..finish
163 bpf-next -> net-next, the subject must look like::
165 git format-patch --subject-prefix='PATCH bpf-next' start..finish
167 If unsure whether the patch or patch series should go into bpf
168 or net directly, or bpf-next or net-next directly, it is not a
173 If it is clear that patches should go into bpf or bpf-next tree,
181 git format-patch --subject-prefix='PATCH bpf-next v2' start..finish
187 Q: What does it mean when a patch gets applied to bpf or bpf-next tree?
195 On the bpf kernel mailing list reviews can come in at any point
225 accumulate too many patches in bpf or bpf-next.
232 Q: Are patches applied to bpf-next when the merge window is open?
234 A: For the time when the merge window is open, bpf-next will not be
240 your patch series once bpf-next is open again. Once Linus released
241 a ``v*-rc1`` after the merge window, we continue processing of bpf-next.
266 Q: samples/bpf preference vs selftests?
268 Q: When should I add code to ``samples/bpf/`` and when to BPF kernel
272 ``samples/bpf/``. The rationale is very simple: kernel selftests are
280 That said, ``samples/bpf/`` may be a good place for people to get started,
282 ``samples/bpf/``, but advanced functional and corner-case testing rather
290 A: The main purpose of bpftool (under tools/bpf/bpftool/) is to provide
340 Note, fixes that go to bpf tree *must* have a ``Fixes:`` tag included.
341 The same applies to fixes that target bpf-next, where the affected
342 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is
431 A: Once patches that fix critical bugs got applied into the bpf tree, they
434 http://patchwork.ozlabs.org/bundle/bpf/stable/?state=*
451 $ cd tools/testing/selftests/bpf/
474 tools/testing/selftests/bpf as closely as possible.
477 discussed in Documentation/bpf/btf.rst - pahole version 1.16
485 commit 21507cd3e97b ("pahole: add libbpf as submodule under lib/bpf").
534 bpf - BPF (host endian)
595 https://bugs.llvm.org/buglist.cgi?quicksearch=bpf
616 $ llc -march bpf -mcpu=help
636 Q: clang flag for target bpf?
638 Q: In some cases clang flag ``--target=bpf`` is used but in other cases the
647 while ``bpf`` target may fail if bpf backend assembler does not
652 with default target, but not with ``bpf`` target.
656 in the global readonly section, the bpf program will fail to load.
657 The bpf target does not support switch table optimization.
661 - For clang ``--target=bpf``, it is guaranteed that pointer or long /
671 Otherwise, ``clang --target=bpf`` is generally recommended.
680 Otherwise, you can use ``bpf`` target. Additionally, you *must* use bpf target
688 BPF_PROG_TYPE_SK_MSG require ``--target=bpf``
693 …ttps://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/bpf/