forked from ~ljy/RK356X_SDK_RELEASE
kernel/Documentation/bpf/bpf_devel_QA.rst
.. .. @@ -20,11 +20,11 @@ 20 20 Q: How do I report bugs for BPF kernel code? 21 21 -------------------------------------------- 22 22 A: Since all BPF kernel development as well as bpftool and iproute2 BPF 23 23 24 24 please report any found issues around BPF to the following mailing 25 25 list: 26 26 27 27 28 28 29 29 This may also include issues related to XDP, BPF tracing, etc. 30 30 .. .. @@ -46,17 +46,12 @@ 46 46 47 47 Q: To which mailing list do I need to submit my BPF patches? 48 48 ------------------------------------------------------------ 49 49 50 50 51 52 53 54 55 56 51 57 52 58 53 In case your patch has changes in various different subsystems (e.g. 59 54 60 55 lists and maintainers from there as well, so they are able to review 61 56 the changes and provide their Acked-by's to the patches. 62 57 .. .. @@ -65,13 +60,13 @@ 65 60 A: All patches that are Cc'ed to netdev are queued for review under netdev 66 61 patchwork project: 67 62 68 63 69 64 70 65 Those patches which target BPF, are assigned to a 'bpf' delegate for 71 66 further processing from BPF maintainers. The current queue with 72 67 patches under review can be found at: 73 68 74 69 75 70 76 71 Once the patches have been reviewed by the BPF community as a whole 77 72 and approved by the BPF maintainers, their status in patchwork will be .. .. @@ -154,7 +149,7 @@ 154 149 again in a second or later revision, it is also required to add a 155 150 version number (``v2``, ``v3``, ...) into the subject prefix:: 156 151 157 152 158 153 159 154 When changes have been requested to the patch series, always send the 160 155 whole patch series again with the feedback incorporated (never send .. .. @@ -168,7 +163,7 @@ 168 163 Be aware that this is not a final verdict that the patch will 169 164 automatically get accepted into net or net-next trees eventually: 170 165 171 166 172 167 in time. If discussions around a patch conclude that they cannot 173 168 get included as-is, we will either apply a follow-up fix or drop 174 169 them from the trees entirely. Therefore, we also reserve to rebase .. .. @@ -442,6 +437,21 @@ 442 437 See the kernels selftest `Documentation/dev-tools/kselftest.rst`_ 443 438 document for further documentation. 444 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 445 455 Q: Which BPF kernel selftests version should I run my kernel against? 446 456 --------------------------------------------------------------------- 447 457 A: If you run a kernel ``xyz``, then always run the BPF kernel selftests .. .. @@ -469,17 +479,18 @@ 469 479 470 480 $ llc --version 471 481 LLVM (http://llvm.org/): 472 482 473 483 Optimized build. 474 484 Default target: x86_64-unknown-linux-gnu 475 485 Host CPU: skylake 476 486 477 487 Registered Targets: 478 479 480 481 482 488 489 490 491 492 493 483 494 484 495 For developers in order to utilize the latest features added to LLVM's 485 496 BPF back end, it is advisable to run the latest LLVM releases. Support .. .. @@ -494,18 +505,22 @@ 494 505 that set up, proceed with building the latest LLVM and clang version 495 506 from the git repositories:: 496 507 497 498 499 500 501 508 509 510 511 512 502 513 -DBUILD_SHARED_LIBS=OFF \ 503 514 -DCMAKE_BUILD_TYPE=Release \ 504 515 -DLLVM_BUILD_RUNTIME=OFF 505 516 506 517 507 518 The built binaries can then be found in the build/bin/ directory, where 508 519 you can point the PATH variable to. 520 521 522 523 509 524 510 525 Q: Reporting LLVM BPF issues 511 526 ---------------------------- .. .. @@ -633,5 +648,6 @@ 633 648 .. _selftests: ../../tools/testing/selftests/bpf/ 634 649 .. _Documentation/dev-tools/kselftest.rst: 635 650 https://www.kernel.org/doc/html/latest/dev-tools/kselftest.html 651 636 652 637 653 Happy BPF hacking!
