23 loader development happens through the bpf kernel mailing list,
27  bpf@vger.kernel.org
49 A: Please submit your BPF patches to the bpf kernel mailing list:
51  bpf@vger.kernel.org
65 Those patches which target BPF, are assigned to a 'bpf' delegate for
81 the 'bpf' delegate).
89  * https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/
90  * https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/
92 The bpf tree itself is for fixes only, whereas bpf-next for features,
94 analogous to net and net-next trees for networking. Both bpf and
95 bpf-next will only have a master branch in order to simplify against
98 Accumulated BPF patches in the bpf tree will regularly get pulled
100 into the bpf-next tree will make their way into net-next tree. net and
117   pull-request: bpf yyyy-mm-dd
118   pull-request: bpf-next yyyy-mm-dd
120 Q: How do I indicate which tree (bpf vs. bpf-next) my patch should be applied to?
126 maintainers know whether it is targeted at bpf or bpf-next.
128 For fixes eventually landing in bpf -> net tree, the subject must
131   git format-patch --subject-prefix='PATCH bpf' start..finish
134 bpf-next -> net-next, the subject must look like::
136   git format-patch --subject-prefix='PATCH bpf-next' start..finish
138 If unsure whether the patch or patch series should go into bpf
139 or net directly, or bpf-next or net-next directly, it is not a
144 If it is clear that patches should go into bpf or bpf-next tree,
152   git format-patch --subject-prefix='PATCH bpf-next v2' start..finish
158 Q: What does it mean when a patch gets applied to bpf or bpf-next tree?
166 On the bpf kernel mailing list reviews can come in at any point
195 accumulate too many patches in bpf or bpf-next.
202 Q: Are patches applied to bpf-next when the merge window is open?
204 A: For the time when the merge window is open, bpf-next will not be
209 your patch series once bpf-next is open again. Once Linus released
210 a ``v*-rc1`` after the merge window, we continue processing of bpf-next.
235 Q: samples/bpf preference vs selftests?
237 Q: When should I add code to `samples/bpf/`_ and when to BPF kernel
241 `samples/bpf/`_. The rationale is very simple: kernel selftests are
249 That said, `samples/bpf/`_ may be a good place for people to get started,
251 `samples/bpf/`_, but advanced functional and corner-case testing rather
259 A: The main purpose of bpftool (under tools/bpf/bpftool/) is to provide
309 Note, fixes that go to bpf tree *must* have a ``Fixes:`` tag included.
310 The same applies to fixes that target bpf-next, where the affected
311 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is
399 A: Once patches that fix critical bugs got applied into the bpf tree, they
402   http://patchwork.ozlabs.org/bundle/bpf/stable/?state=*
419   $ cd tools/testing/selftests/bpf/
442 tools/testing/selftests/bpf as closely as possible.
445 discussed in `Documentation/bpf/btf.rst`_ - pahole version 1.16
489          bpf        - BPF (host endian)
547   https://bugs.llvm.org/buglist.cgi?quicksearch=bpf
568      $ llc -march bpf -mcpu=help
588 Q: clang flag for target bpf?
590 Q: In some cases clang flag ``-target bpf`` is used but in other cases the
599   while ``bpf`` target may fail if bpf backend assembler does not
604   with default target, but not with ``bpf`` target.
608   in the global readonly section, the bpf program will fail to load.
609   The bpf target does not support switch table optimization.
613 - For clang ``-target bpf``, it is guaranteed that pointer or long /
623   Otherwise, ``clang -target bpf`` is generally recommended.
632 Otherwise, you can use ``bpf`` target. Additionally, you *must* use bpf target
640   BPF_PROG_TYPE_SK_MSG require ``-target bpf``
647 .. _samples/bpf/: ../../samples/bpf/  argument
648 .. _selftests: ../../tools/testing/selftests/bpf/  argument
651 .. _Documentation/bpf/btf.rst: btf.rst  argument