Blame view
Documentation/bpf/bpf_devel_QA.rst
26.2 KB
542228384 bpf, doc: convert... |
1 2 3 |
================================= HOWTO interact with BPF subsystem ================================= |
34f15bf31 bpf, doc: add faq... |
4 5 6 7 8 |
This document provides information for the BPF subsystem about various workflows related to reporting bugs, submitting patches, and queueing patches for stable kernels. For general information about submitting patches, please refer to |
542228384 bpf, doc: convert... |
9 |
`Documentation/process/`_. This document only describes additional specifics |
34f15bf31 bpf, doc: add faq... |
10 |
related to BPF. |
542228384 bpf, doc: convert... |
11 12 13 |
.. contents:: :local: :depth: 2 |
34f15bf31 bpf, doc: add faq... |
14 |
|
542228384 bpf, doc: convert... |
15 16 |
Reporting bugs ============== |
34f15bf31 bpf, doc: add faq... |
17 |
|
542228384 bpf, doc: convert... |
18 19 |
Q: How do I report bugs for BPF kernel code? -------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
20 |
A: Since all BPF kernel development as well as bpftool and iproute2 BPF |
542228384 bpf, doc: convert... |
21 22 23 |
loader development happens through the netdev kernel mailing list, please report any found issues around BPF to the following mailing list: |
34f15bf31 bpf, doc: add faq... |
24 |
|
542228384 bpf, doc: convert... |
25 |
netdev@vger.kernel.org |
34f15bf31 bpf, doc: add faq... |
26 |
|
542228384 bpf, doc: convert... |
27 |
This may also include issues related to XDP, BPF tracing, etc. |
34f15bf31 bpf, doc: add faq... |
28 |
|
542228384 bpf, doc: convert... |
29 30 |
Given netdev has a high volume of traffic, please also add the BPF maintainers to Cc (from kernel MAINTAINERS_ file): |
34f15bf31 bpf, doc: add faq... |
31 |
|
542228384 bpf, doc: convert... |
32 33 |
* Alexei Starovoitov <ast@kernel.org> * Daniel Borkmann <daniel@iogearbox.net> |
34f15bf31 bpf, doc: add faq... |
34 |
|
542228384 bpf, doc: convert... |
35 36 37 |
In case a buggy commit has already been identified, make sure to keep the actual commit authors in Cc as well for the report. They can typically be identified through the kernel's git tree. |
34f15bf31 bpf, doc: add faq... |
38 |
|
542228384 bpf, doc: convert... |
39 40 |
**Please do NOT report BPF issues to bugzilla.kernel.org since it is a guarantee that the reported issue will be overlooked.** |
34f15bf31 bpf, doc: add faq... |
41 |
|
542228384 bpf, doc: convert... |
42 43 |
Submitting patches ================== |
34f15bf31 bpf, doc: add faq... |
44 45 |
Q: To which mailing list do I need to submit my BPF patches? |
542228384 bpf, doc: convert... |
46 |
------------------------------------------------------------ |
34f15bf31 bpf, doc: add faq... |
47 |
A: Please submit your BPF patches to the netdev kernel mailing list: |
542228384 bpf, doc: convert... |
48 |
netdev@vger.kernel.org |
34f15bf31 bpf, doc: add faq... |
49 |
|
542228384 bpf, doc: convert... |
50 51 52 53 |
Historically, BPF came out of networking and has always been maintained by the kernel networking community. Although these days BPF touches many other subsystems as well, the patches are still routed mainly through the networking community. |
34f15bf31 bpf, doc: add faq... |
54 |
|
542228384 bpf, doc: convert... |
55 56 57 58 |
In case your patch has changes in various different subsystems (e.g. tracing, security, etc), make sure to Cc the related kernel mailing lists and maintainers from there as well, so they are able to review the changes and provide their Acked-by's to the patches. |
34f15bf31 bpf, doc: add faq... |
59 60 |
Q: Where can I find patches currently under discussion for BPF subsystem? |
542228384 bpf, doc: convert... |
61 |
------------------------------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
62 |
A: All patches that are Cc'ed to netdev are queued for review under netdev |
542228384 bpf, doc: convert... |
63 |
patchwork project: |
34f15bf31 bpf, doc: add faq... |
64 |
|
542228384 bpf, doc: convert... |
65 |
http://patchwork.ozlabs.org/project/netdev/list/ |
34f15bf31 bpf, doc: add faq... |
66 |
|
542228384 bpf, doc: convert... |
67 68 69 |
Those patches which target BPF, are assigned to a 'bpf' delegate for further processing from BPF maintainers. The current queue with patches under review can be found at: |
34f15bf31 bpf, doc: add faq... |
70 |
|
542228384 bpf, doc: convert... |
71 |
https://patchwork.ozlabs.org/project/netdev/list/?delegate=77147 |
34f15bf31 bpf, doc: add faq... |
72 |
|
542228384 bpf, doc: convert... |
73 74 75 76 77 |
Once the patches have been reviewed by the BPF community as a whole and approved by the BPF maintainers, their status in patchwork will be changed to 'Accepted' and the submitter will be notified by mail. This means that the patches look good from a BPF perspective and have been applied to one of the two BPF kernel trees. |
34f15bf31 bpf, doc: add faq... |
78 |
|
542228384 bpf, doc: convert... |
79 80 81 82 83 |
In case feedback from the community requires a respin of the patches, their status in patchwork will be set to 'Changes Requested', and purged from the current review queue. Likewise for cases where patches would get rejected or are not applicable to the BPF trees (but assigned to the 'bpf' delegate). |
34f15bf31 bpf, doc: add faq... |
84 85 |
Q: How do the changes make their way into Linux? |
542228384 bpf, doc: convert... |
86 |
------------------------------------------------ |
34f15bf31 bpf, doc: add faq... |
87 |
A: There are two BPF kernel trees (git repositories). Once patches have |
542228384 bpf, doc: convert... |
88 89 |
been accepted by the BPF maintainers, they will be applied to one of the two BPF trees: |
34f15bf31 bpf, doc: add faq... |
90 |
|
542228384 bpf, doc: convert... |
91 92 |
* https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/ * https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/ |
34f15bf31 bpf, doc: add faq... |
93 |
|
542228384 bpf, doc: convert... |
94 95 96 97 98 |
The bpf tree itself is for fixes only, whereas bpf-next for features, cleanups or other kind of improvements ("next-like" content). This is analogous to net and net-next trees for networking. Both bpf and bpf-next will only have a master branch in order to simplify against which branch patches should get rebased to. |
34f15bf31 bpf, doc: add faq... |
99 |
|
542228384 bpf, doc: convert... |
100 101 102 103 104 105 |
Accumulated BPF patches in the bpf tree will regularly get pulled into the net kernel tree. Likewise, accumulated BPF patches accepted into the bpf-next tree will make their way into net-next tree. net and net-next are both run by David S. Miller. From there, they will go into the kernel mainline tree run by Linus Torvalds. To read up on the process of net and net-next being merged into the mainline tree, see |
287f4fa99 docs: Update refe... |
106 |
the :ref:`netdev-FAQ` |
34f15bf31 bpf, doc: add faq... |
107 |
|
34f15bf31 bpf, doc: add faq... |
108 |
|
542228384 bpf, doc: convert... |
109 110 111 |
Occasionally, to prevent merge conflicts, we might send pull requests to other trees (e.g. tracing) with a small subset of the patches, but net and net-next are always the main trees targeted for integration. |
34f15bf31 bpf, doc: add faq... |
112 |
|
542228384 bpf, doc: convert... |
113 114 115 116 |
The pull requests will contain a high-level summary of the accumulated patches and can be searched on netdev kernel mailing list through the following subject lines (``yyyy-mm-dd`` is the date of the pull request):: |
34f15bf31 bpf, doc: add faq... |
117 |
|
542228384 bpf, doc: convert... |
118 119 |
pull-request: bpf yyyy-mm-dd pull-request: bpf-next yyyy-mm-dd |
34f15bf31 bpf, doc: add faq... |
120 |
|
542228384 bpf, doc: convert... |
121 122 |
Q: How do I indicate which tree (bpf vs. bpf-next) my patch should be applied to? --------------------------------------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
123 |
|
287f4fa99 docs: Update refe... |
124 125 |
A: The process is the very same as described in the :ref:`netdev-FAQ`, so please read up on it. The subject line must indicate whether the |
542228384 bpf, doc: convert... |
126 127 |
patch is a fix or rather "next-like" content in order to let the maintainers know whether it is targeted at bpf or bpf-next. |
34f15bf31 bpf, doc: add faq... |
128 |
|
542228384 bpf, doc: convert... |
129 130 |
For fixes eventually landing in bpf -> net tree, the subject must look like:: |
34f15bf31 bpf, doc: add faq... |
131 |
|
542228384 bpf, doc: convert... |
132 |
git format-patch --subject-prefix='PATCH bpf' start..finish |
34f15bf31 bpf, doc: add faq... |
133 |
|
542228384 bpf, doc: convert... |
134 135 |
For features/improvements/etc that should eventually land in bpf-next -> net-next, the subject must look like:: |
34f15bf31 bpf, doc: add faq... |
136 |
|
542228384 bpf, doc: convert... |
137 |
git format-patch --subject-prefix='PATCH bpf-next' start..finish |
34f15bf31 bpf, doc: add faq... |
138 |
|
542228384 bpf, doc: convert... |
139 140 141 142 143 |
If unsure whether the patch or patch series should go into bpf or net directly, or bpf-next or net-next directly, it is not a problem either if the subject line says net or net-next as target. It is eventually up to the maintainers to do the delegation of the patches. |
34f15bf31 bpf, doc: add faq... |
144 |
|
542228384 bpf, doc: convert... |
145 146 147 |
If it is clear that patches should go into bpf or bpf-next tree, please make sure to rebase the patches against those trees in order to reduce potential conflicts. |
34f15bf31 bpf, doc: add faq... |
148 |
|
542228384 bpf, doc: convert... |
149 150 151 |
In case the patch or patch series has to be reworked and sent out again in a second or later revision, it is also required to add a version number (``v2``, ``v3``, ...) into the subject prefix:: |
34f15bf31 bpf, doc: add faq... |
152 |
|
542228384 bpf, doc: convert... |
153 |
git format-patch --subject-prefix='PATCH net-next v2' start..finish |
34f15bf31 bpf, doc: add faq... |
154 |
|
542228384 bpf, doc: convert... |
155 156 157 |
When changes have been requested to the patch series, always send the whole patch series again with the feedback incorporated (never send individual diffs on top of the old series). |
34f15bf31 bpf, doc: add faq... |
158 159 |
Q: What does it mean when a patch gets applied to bpf or bpf-next tree? |
542228384 bpf, doc: convert... |
160 |
----------------------------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
161 |
A: It means that the patch looks good for mainline inclusion from |
542228384 bpf, doc: convert... |
162 |
a BPF point of view. |
34f15bf31 bpf, doc: add faq... |
163 |
|
542228384 bpf, doc: convert... |
164 165 166 167 168 169 170 171 172 173 174 175 |
Be aware that this is not a final verdict that the patch will automatically get accepted into net or net-next trees eventually: On the netdev kernel mailing list reviews can come in at any point in time. If discussions around a patch conclude that they cannot get included as-is, we will either apply a follow-up fix or drop them from the trees entirely. Therefore, we also reserve to rebase the trees when deemed necessary. After all, the purpose of the tree is to: i) accumulate and stage BPF patches for integration into trees like net and net-next, and |
34f15bf31 bpf, doc: add faq... |
176 |
|
542228384 bpf, doc: convert... |
177 178 179 180 181 182 |
ii) run extensive BPF test suite and workloads on the patches before they make their way any further. Once the BPF pull request was accepted by David S. Miller, then the patches end up in net or net-next tree, respectively, and make their way from there further into mainline. Again, see the |
287f4fa99 docs: Update refe... |
183 |
:ref:`netdev-FAQ` for additional information e.g. on how often they are |
542228384 bpf, doc: convert... |
184 185 186 187 |
merged to mainline. Q: How long do I need to wait for feedback on my BPF patches? ------------------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
188 |
A: We try to keep the latency low. The usual time to feedback will |
542228384 bpf, doc: convert... |
189 190 |
be around 2 or 3 business days. It may vary depending on the complexity of changes and current patch load. |
34f15bf31 bpf, doc: add faq... |
191 |
|
542228384 bpf, doc: convert... |
192 193 |
Q: How often do you send pull requests to major kernel trees like net or net-next? ---------------------------------------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
194 195 |
A: Pull requests will be sent out rather often in order to not |
542228384 bpf, doc: convert... |
196 |
accumulate too many patches in bpf or bpf-next. |
34f15bf31 bpf, doc: add faq... |
197 |
|
542228384 bpf, doc: convert... |
198 199 200 201 |
As a rule of thumb, expect pull requests for each tree regularly at the end of the week. In some cases pull requests could additionally come also in the middle of the week depending on the current patch load or urgency. |
34f15bf31 bpf, doc: add faq... |
202 203 |
Q: Are patches applied to bpf-next when the merge window is open? |
542228384 bpf, doc: convert... |
204 |
----------------------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
205 |
A: For the time when the merge window is open, bpf-next will not be |
542228384 bpf, doc: convert... |
206 |
processed. This is roughly analogous to net-next patch processing, |
287f4fa99 docs: Update refe... |
207 |
so feel free to read up on the :ref:`netdev-FAQ` about further details. |
34f15bf31 bpf, doc: add faq... |
208 |
|
542228384 bpf, doc: convert... |
209 210 211 |
During those two weeks of merge window, we might ask you to resend your patch series once bpf-next is open again. Once Linus released a ``v*-rc1`` after the merge window, we continue processing of bpf-next. |
34f15bf31 bpf, doc: add faq... |
212 |
|
542228384 bpf, doc: convert... |
213 214 |
For non-subscribers to kernel mailing lists, there is also a status page run by David S. Miller on net-next that provides guidance: |
34f15bf31 bpf, doc: add faq... |
215 |
|
542228384 bpf, doc: convert... |
216 |
http://vger.kernel.org/~davem/net-next.html |
34f15bf31 bpf, doc: add faq... |
217 |
|
542228384 bpf, doc: convert... |
218 219 |
Q: Verifier changes and test cases ---------------------------------- |
34f15bf31 bpf, doc: add faq... |
220 |
Q: I made a BPF verifier change, do I need to add test cases for |
542228384 bpf, doc: convert... |
221 |
BPF kernel selftests_? |
34f15bf31 bpf, doc: add faq... |
222 223 |
A: If the patch has changes to the behavior of the verifier, then yes, |
542228384 bpf, doc: convert... |
224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 |
it is absolutely necessary to add test cases to the BPF kernel selftests_ suite. If they are not present and we think they are needed, then we might ask for them before accepting any changes. In particular, test_verifier.c is tracking a high number of BPF test cases, including a lot of corner cases that LLVM BPF back end may generate out of the restricted C code. Thus, adding test cases is absolutely crucial to make sure future changes do not accidentally affect prior use-cases. Thus, treat those test cases as: verifier behavior that is not tracked in test_verifier.c could potentially be subject to change. Q: samples/bpf preference vs selftests? --------------------------------------- Q: When should I add code to `samples/bpf/`_ and when to BPF kernel selftests_ ? A: In general, we prefer additions to BPF kernel selftests_ rather than `samples/bpf/`_. The rationale is very simple: kernel selftests are regularly run by various bots to test for kernel regressions. The more test cases we add to BPF selftests, the better the coverage and the less likely it is that those could accidentally break. It is not that BPF kernel selftests cannot demo how a specific feature can be used. That said, `samples/bpf/`_ may be a good place for people to get started, so it might be advisable that simple demos of features could go into `samples/bpf/`_, but advanced functional and corner-case testing rather into kernel selftests. If your sample looks like a test case, then go for BPF kernel selftests instead! |
34f15bf31 bpf, doc: add faq... |
257 258 |
Q: When should I add code to the bpftool? |
542228384 bpf, doc: convert... |
259 |
----------------------------------------- |
34f15bf31 bpf, doc: add faq... |
260 |
A: The main purpose of bpftool (under tools/bpf/bpftool/) is to provide |
542228384 bpf, doc: convert... |
261 262 263 264 |
a central user space tool for debugging and introspection of BPF programs and maps that are active in the kernel. If UAPI changes related to BPF enable for dumping additional information of programs or maps, then bpftool should be extended as well to support dumping them. |
34f15bf31 bpf, doc: add faq... |
265 266 |
Q: When should I add code to iproute2's BPF loader? |
542228384 bpf, doc: convert... |
267 268 269 270 271 272 273 |
--------------------------------------------------- A: For UAPI changes related to the XDP or tc layer (e.g. ``cls_bpf``), the convention is that those control-path related changes are added to iproute2's BPF loader as well from user space side. This is not only useful to have UAPI changes properly designed to be usable, but also to make those changes available to a wider user base of major downstream distributions. |
34f15bf31 bpf, doc: add faq... |
274 275 |
Q: Do you accept patches as well for iproute2's BPF loader? |
542228384 bpf, doc: convert... |
276 |
----------------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
277 |
A: Patches for the iproute2's BPF loader have to be sent to: |
542228384 bpf, doc: convert... |
278 |
netdev@vger.kernel.org |
34f15bf31 bpf, doc: add faq... |
279 |
|
542228384 bpf, doc: convert... |
280 281 |
While those patches are not processed by the BPF kernel maintainers, please keep them in Cc as well, so they can be reviewed. |
34f15bf31 bpf, doc: add faq... |
282 |
|
542228384 bpf, doc: convert... |
283 284 |
The official git repository for iproute2 is run by Stephen Hemminger and can be found at: |
34f15bf31 bpf, doc: add faq... |
285 |
|
542228384 bpf, doc: convert... |
286 |
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/ |
34f15bf31 bpf, doc: add faq... |
287 |
|
542228384 bpf, doc: convert... |
288 289 290 291 292 293 294 295 |
The patches need to have a subject prefix of '``[PATCH iproute2 master]``' or '``[PATCH iproute2 net-next]``'. '``master``' or '``net-next``' describes the target branch where the patch should be applied to. Meaning, if kernel changes went into the net-next kernel tree, then the related iproute2 changes need to go into the iproute2 net-next branch, otherwise they can be targeted at master branch. The iproute2 net-next branch will get merged into the master branch after the current iproute2 version from master has been released. |
34f15bf31 bpf, doc: add faq... |
296 |
|
542228384 bpf, doc: convert... |
297 298 |
Like BPF, the patches end up in patchwork under the netdev project and are delegated to 'shemminger' for further processing: |
34f15bf31 bpf, doc: add faq... |
299 |
|
542228384 bpf, doc: convert... |
300 |
http://patchwork.ozlabs.org/project/netdev/list/?delegate=389 |
34f15bf31 bpf, doc: add faq... |
301 302 |
Q: What is the minimum requirement before I submit my BPF patches? |
542228384 bpf, doc: convert... |
303 |
------------------------------------------------------------------ |
34f15bf31 bpf, doc: add faq... |
304 |
A: When submitting patches, always take the time and properly test your |
542228384 bpf, doc: convert... |
305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 |
patches *prior* to submission. Never rush them! If maintainers find that your patches have not been properly tested, it is a good way to get them grumpy. Testing patch submissions is a hard requirement! Note, fixes that go to bpf tree *must* have a ``Fixes:`` tag included. The same applies to fixes that target bpf-next, where the affected commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is crucial in order to identify follow-up commits and tremendously helps for people having to do backporting, so it is a must have! We also don't accept patches with an empty commit message. Take your time and properly write up a high quality commit message, it is essential! Think about it this way: other developers looking at your code a month from now need to understand *why* a certain change has been done that way, and whether there have been flaws in the analysis or assumptions that the original author did. Thus providing a proper rationale and describing the use-case for the changes is a must. Patch submissions with >1 patch must have a cover letter which includes a high level description of the series. This high level summary will then be placed into the merge commit by the BPF maintainers such that it is also accessible from the git log for future reference. Q: Features changing BPF JIT and/or LLVM ---------------------------------------- |
34f15bf31 bpf, doc: add faq... |
332 |
Q: What do I need to consider when adding a new instruction or feature |
542228384 bpf, doc: convert... |
333 |
that would require BPF JIT and/or LLVM integration as well? |
34f15bf31 bpf, doc: add faq... |
334 335 |
A: We try hard to keep all BPF JITs up to date such that the same user |
542228384 bpf, doc: convert... |
336 337 338 |
experience can be guaranteed when running BPF programs on different architectures without having the program punt to the less efficient interpreter in case the in-kernel BPF JIT is enabled. |
34f15bf31 bpf, doc: add faq... |
339 |
|
542228384 bpf, doc: convert... |
340 341 342 343 344 |
If you are unable to implement or test the required JIT changes for certain architectures, please work together with the related BPF JIT developers in order to get the feature implemented in a timely manner. Please refer to the git log (``arch/*/net/``) to locate the necessary people for helping out. |
34f15bf31 bpf, doc: add faq... |
345 |
|
542228384 bpf, doc: convert... |
346 347 348 |
Also always make sure to add BPF test cases (e.g. test_bpf.c and test_verifier.c) for new instructions, so that they can receive broad test coverage and help run-time testing the various BPF JITs. |
34f15bf31 bpf, doc: add faq... |
349 |
|
542228384 bpf, doc: convert... |
350 351 352 |
In case of new BPF instructions, once the changes have been accepted into the Linux kernel, please implement support into LLVM's BPF back end. See LLVM_ section below for further information. |
34f15bf31 bpf, doc: add faq... |
353 |
|
542228384 bpf, doc: convert... |
354 355 |
Stable submission ================= |
34f15bf31 bpf, doc: add faq... |
356 357 |
Q: I need a specific BPF commit in stable kernels. What should I do? |
542228384 bpf, doc: convert... |
358 |
-------------------------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
359 |
A: In case you need a specific fix in stable kernels, first check whether |
542228384 bpf, doc: convert... |
360 |
the commit has already been applied in the related ``linux-*.y`` branches: |
34f15bf31 bpf, doc: add faq... |
361 |
|
542228384 bpf, doc: convert... |
362 |
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/ |
34f15bf31 bpf, doc: add faq... |
363 |
|
542228384 bpf, doc: convert... |
364 365 |
If not the case, then drop an email to the BPF maintainers with the netdev kernel mailing list in Cc and ask for the fix to be queued up: |
34f15bf31 bpf, doc: add faq... |
366 |
|
542228384 bpf, doc: convert... |
367 |
netdev@vger.kernel.org |
34f15bf31 bpf, doc: add faq... |
368 |
|
542228384 bpf, doc: convert... |
369 |
The process in general is the same as on netdev itself, see also the |
287f4fa99 docs: Update refe... |
370 |
:ref:`netdev-FAQ`. |
34f15bf31 bpf, doc: add faq... |
371 372 |
Q: Do you also backport to kernels not currently maintained as stable? |
542228384 bpf, doc: convert... |
373 |
---------------------------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
374 |
A: No. If you need a specific BPF commit in kernels that are currently not |
542228384 bpf, doc: convert... |
375 |
maintained by the stable maintainers, then you are on your own. |
34f15bf31 bpf, doc: add faq... |
376 |
|
542228384 bpf, doc: convert... |
377 |
The current stable and longterm stable kernels are all listed here: |
34f15bf31 bpf, doc: add faq... |
378 |
|
542228384 bpf, doc: convert... |
379 |
https://www.kernel.org/ |
34f15bf31 bpf, doc: add faq... |
380 |
|
542228384 bpf, doc: convert... |
381 382 383 |
Q: The BPF patch I am about to submit needs to go to stable as well ------------------------------------------------------------------- What should I do? |
34f15bf31 bpf, doc: add faq... |
384 385 |
A: The same rules apply as with netdev patch submissions in general, see |
287f4fa99 docs: Update refe... |
386 |
the :ref:`netdev-FAQ`. |
34f15bf31 bpf, doc: add faq... |
387 |
|
542228384 bpf, doc: convert... |
388 389 390 391 392 |
Never add "``Cc: stable@vger.kernel.org``" to the patch description, but ask the BPF maintainers to queue the patches instead. This can be done with a note, for example, under the ``---`` part of the patch which does not go into the git log. Alternatively, this can be done as a simple request by mail instead. |
34f15bf31 bpf, doc: add faq... |
393 |
|
542228384 bpf, doc: convert... |
394 395 |
Q: Queue stable patches ----------------------- |
34f15bf31 bpf, doc: add faq... |
396 |
Q: Where do I find currently queued BPF patches that will be submitted |
542228384 bpf, doc: convert... |
397 |
to stable? |
34f15bf31 bpf, doc: add faq... |
398 399 |
A: Once patches that fix critical bugs got applied into the bpf tree, they |
542228384 bpf, doc: convert... |
400 |
are queued up for stable submission under: |
34f15bf31 bpf, doc: add faq... |
401 |
|
542228384 bpf, doc: convert... |
402 |
http://patchwork.ozlabs.org/bundle/bpf/stable/?state=* |
34f15bf31 bpf, doc: add faq... |
403 |
|
542228384 bpf, doc: convert... |
404 405 |
They will be on hold there at minimum until the related commit made its way into the mainline kernel tree. |
34f15bf31 bpf, doc: add faq... |
406 |
|
542228384 bpf, doc: convert... |
407 408 |
After having been under broader exposure, the queued patches will be submitted by the BPF maintainers to the stable maintainers. |
34f15bf31 bpf, doc: add faq... |
409 |
|
542228384 bpf, doc: convert... |
410 411 |
Testing patches =============== |
34f15bf31 bpf, doc: add faq... |
412 |
|
b7a27c3aa bpf, doc: howto u... |
413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 |
Q: How to run BPF selftests --------------------------- A: After you have booted into the newly compiled kernel, navigate to the BPF selftests_ suite in order to test BPF functionality (current working directory points to the root of the cloned git tree):: $ cd tools/testing/selftests/bpf/ $ make To run the verifier tests:: $ sudo ./test_verifier The verifier tests print out all the current checks being performed. The summary at the end of running all tests will dump information of test successes and failures:: Summary: 418 PASSED, 0 FAILED In order to run through all BPF selftests, the following command is needed:: $ sudo make run_tests See the kernels selftest `Documentation/dev-tools/kselftest.rst`_ document for further documentation. |
34f15bf31 bpf, doc: add faq... |
439 |
Q: Which BPF kernel selftests version should I run my kernel against? |
542228384 bpf, doc: convert... |
440 441 442 443 |
--------------------------------------------------------------------- A: If you run a kernel ``xyz``, then always run the BPF kernel selftests from that kernel ``xyz`` as well. Do not expect that the BPF selftest from the latest mainline tree will pass all the time. |
34f15bf31 bpf, doc: add faq... |
444 |
|
542228384 bpf, doc: convert... |
445 446 447 448 |
In particular, test_bpf.c and test_verifier.c have a large number of test cases and are constantly updated with new BPF test sequences, or existing ones are adapted to verifier changes e.g. due to verifier becoming smarter and being able to better track certain things. |
34f15bf31 bpf, doc: add faq... |
449 |
|
542228384 bpf, doc: convert... |
450 451 |
LLVM ==== |
34f15bf31 bpf, doc: add faq... |
452 453 |
Q: Where do I find LLVM with BPF support? |
542228384 bpf, doc: convert... |
454 |
----------------------------------------- |
34f15bf31 bpf, doc: add faq... |
455 |
A: The BPF back end for LLVM is upstream in LLVM since version 3.7.1. |
542228384 bpf, doc: convert... |
456 457 458 |
All major distributions these days ship LLVM with BPF back end enabled, so for the majority of use-cases it is not required to compile LLVM by hand anymore, just install the distribution provided package. |
34f15bf31 bpf, doc: add faq... |
459 |
|
542228384 bpf, doc: convert... |
460 461 |
LLVM's static compiler lists the supported targets through ``llc --version``, make sure BPF targets are listed. Example:: |
34f15bf31 bpf, doc: add faq... |
462 463 464 465 466 467 468 469 470 471 472 473 474 475 |
$ llc --version LLVM (http://llvm.org/): LLVM version 6.0.0svn Optimized build. Default target: x86_64-unknown-linux-gnu Host CPU: skylake Registered Targets: bpf - BPF (host endian) bpfeb - BPF (big endian) bpfel - BPF (little endian) x86 - 32-bit X86: Pentium-Pro and above x86-64 - 64-bit X86: EM64T and AMD64 |
542228384 bpf, doc: convert... |
476 477 478 479 |
For developers in order to utilize the latest features added to LLVM's BPF back end, it is advisable to run the latest LLVM releases. Support for new BPF kernel features such as additions to the BPF instruction set are often developed together. |
34f15bf31 bpf, doc: add faq... |
480 |
|
542228384 bpf, doc: convert... |
481 |
All LLVM releases can be found at: http://releases.llvm.org/ |
34f15bf31 bpf, doc: add faq... |
482 483 |
Q: Got it, so how do I build LLVM manually anyway? |
542228384 bpf, doc: convert... |
484 |
-------------------------------------------------- |
34f15bf31 bpf, doc: add faq... |
485 |
A: You need cmake and gcc-c++ as build requisites for LLVM. Once you have |
542228384 bpf, doc: convert... |
486 487 |
that set up, proceed with building the latest LLVM and clang version from the git repositories:: |
34f15bf31 bpf, doc: add faq... |
488 489 490 491 492 493 494 495 496 497 |
$ git clone http://llvm.org/git/llvm.git $ cd llvm/tools $ git clone --depth 1 http://llvm.org/git/clang.git $ cd ..; mkdir build; cd build $ cmake .. -DLLVM_TARGETS_TO_BUILD="BPF;X86" \ -DBUILD_SHARED_LIBS=OFF \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_BUILD_RUNTIME=OFF $ make -j $(getconf _NPROCESSORS_ONLN) |
542228384 bpf, doc: convert... |
498 499 |
The built binaries can then be found in the build/bin/ directory, where you can point the PATH variable to. |
34f15bf31 bpf, doc: add faq... |
500 |
|
542228384 bpf, doc: convert... |
501 502 |
Q: Reporting LLVM BPF issues ---------------------------- |
34f15bf31 bpf, doc: add faq... |
503 |
Q: Should I notify BPF kernel maintainers about issues in LLVM's BPF code |
542228384 bpf, doc: convert... |
504 505 506 507 |
generation back end or about LLVM generated code that the verifier refuses to accept? A: Yes, please do! |
34f15bf31 bpf, doc: add faq... |
508 |
|
542228384 bpf, doc: convert... |
509 510 511 512 |
LLVM's BPF back end is a key piece of the whole BPF infrastructure and it ties deeply into verification of programs from the kernel side. Therefore, any issues on either side need to be investigated and fixed whenever necessary. |
34f15bf31 bpf, doc: add faq... |
513 |
|
542228384 bpf, doc: convert... |
514 515 |
Therefore, please make sure to bring them up at netdev kernel mailing list and Cc BPF maintainers for LLVM and kernel bits: |
34f15bf31 bpf, doc: add faq... |
516 |
|
542228384 bpf, doc: convert... |
517 518 519 |
* Yonghong Song <yhs@fb.com> * Alexei Starovoitov <ast@kernel.org> * Daniel Borkmann <daniel@iogearbox.net> |
34f15bf31 bpf, doc: add faq... |
520 |
|
542228384 bpf, doc: convert... |
521 |
LLVM also has an issue tracker where BPF related bugs can be found: |
34f15bf31 bpf, doc: add faq... |
522 |
|
542228384 bpf, doc: convert... |
523 |
https://bugs.llvm.org/buglist.cgi?quicksearch=bpf |
34f15bf31 bpf, doc: add faq... |
524 |
|
542228384 bpf, doc: convert... |
525 526 |
However, it is better to reach out through mailing lists with having maintainers in Cc. |
34f15bf31 bpf, doc: add faq... |
527 |
|
542228384 bpf, doc: convert... |
528 529 |
Q: New BPF instruction for kernel and LLVM ------------------------------------------ |
34f15bf31 bpf, doc: add faq... |
530 |
Q: I have added a new BPF instruction to the kernel, how can I integrate |
542228384 bpf, doc: convert... |
531 |
it into LLVM? |
34f15bf31 bpf, doc: add faq... |
532 |
|
542228384 bpf, doc: convert... |
533 534 535 536 |
A: LLVM has a ``-mcpu`` selector for the BPF back end in order to allow the selection of BPF instruction set extensions. By default the ``generic`` processor target is used, which is the base instruction set (v1) of BPF. |
34f15bf31 bpf, doc: add faq... |
537 |
|
542228384 bpf, doc: convert... |
538 539 540 |
LLVM has an option to select ``-mcpu=probe`` where it will probe the host kernel for supported BPF instruction set extensions and selects the optimal set automatically. |
34f15bf31 bpf, doc: add faq... |
541 |
|
542228384 bpf, doc: convert... |
542 |
For cross-compilation, a specific version can be select manually as well :: |
34f15bf31 bpf, doc: add faq... |
543 544 545 546 547 548 549 550 551 |
$ llc -march bpf -mcpu=help Available CPUs for this target: generic - Select the generic processor. probe - Select the probe processor. v1 - Select the v1 processor. v2 - Select the v2 processor. [...] |
542228384 bpf, doc: convert... |
552 553 554 555 |
Newly added BPF instructions to the Linux kernel need to follow the same scheme, bump the instruction set version and implement probing for the extensions such that ``-mcpu=probe`` users can benefit from the optimization transparently when upgrading their kernels. |
34f15bf31 bpf, doc: add faq... |
556 |
|
542228384 bpf, doc: convert... |
557 558 |
If you are unable to implement support for the newly added BPF instruction please reach out to BPF developers for help. |
34f15bf31 bpf, doc: add faq... |
559 |
|
542228384 bpf, doc: convert... |
560 561 |
By the way, the BPF kernel selftests run with ``-mcpu=probe`` for better test coverage. |
34f15bf31 bpf, doc: add faq... |
562 |
|
542228384 bpf, doc: convert... |
563 564 565 566 567 |
Q: clang flag for target bpf? ----------------------------- Q: In some cases clang flag ``-target bpf`` is used but in other cases the default clang target, which matches the underlying architecture, is used. What is the difference and when I should use which? |
6215ea6b7 bpf: add document... |
568 569 |
A: Although LLVM IR generation and optimization try to stay architecture |
542228384 bpf, doc: convert... |
570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 |
independent, ``-target <arch>`` still has some impact on generated code: - BPF program may recursively include header file(s) with file scope inline assembly codes. The default target can handle this well, while ``bpf`` target may fail if bpf backend assembler does not understand these assembly codes, which is true in most cases. - When compiled without ``-g``, additional elf sections, e.g., .eh_frame and .rela.eh_frame, may be present in the object file with default target, but not with ``bpf`` target. - The default target may turn a C switch statement into a switch table lookup and jump operation. Since the switch table is placed in the global readonly section, the bpf program will fail to load. The bpf target does not support switch table optimization. The clang option ``-fno-jump-tables`` can be used to disable switch table generation. - For clang ``-target bpf``, it is guaranteed that pointer or long / unsigned long types will always have a width of 64 bit, no matter whether underlying clang binary or default target (or kernel) is 32 bit. However, when native clang target is used, then it will compile these types based on the underlying architecture's conventions, meaning in case of 32 bit architecture, pointer or long / unsigned long types e.g. in BPF context structure will have width of 32 bit while the BPF LLVM back end still operates in 64 bit. The native target is mostly needed in tracing for the case of walking ``pt_regs`` or other kernel structures where CPU's register width matters. Otherwise, ``clang -target bpf`` is generally recommended. You should use default target when: - Your program includes a header file, e.g., ptrace.h, which eventually pulls in some header files containing file scope host assembly codes. - You can add ``-fno-jump-tables`` to work around the switch table issue. Otherwise, you can use ``bpf`` target. Additionally, you *must* use bpf target when: - Your program uses data structures with pointer or long / unsigned long types that interface with BPF helpers or context data structures. Access into these structures is verified by the BPF verifier and may result in verification failures if the native architecture is not aligned with the BPF architecture, e.g. 64-bit. An example of this is BPF_PROG_TYPE_SK_MSG require ``-target bpf`` .. Links .. _Documentation/process/: https://www.kernel.org/doc/html/latest/process/ .. _MAINTAINERS: ../../MAINTAINERS |
287f4fa99 docs: Update refe... |
621 |
.. _netdev-FAQ: ../networking/netdev-FAQ.rst |
542228384 bpf, doc: convert... |
622 623 |
.. _samples/bpf/: ../../samples/bpf/ .. _selftests: ../../tools/testing/selftests/bpf/ |
b7a27c3aa bpf, doc: howto u... |
624 625 |
.. _Documentation/dev-tools/kselftest.rst: https://www.kernel.org/doc/html/latest/dev-tools/kselftest.html |
6215ea6b7 bpf: add document... |
626 |
|
34f15bf31 bpf, doc: add faq... |
627 |
Happy BPF hacking! |