forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next
Daniel Borkmann says: ==================== pull-request: bpf-next 2020-02-21 The following pull-request contains BPF updates for your *net-next* tree. We've added 25 non-merge commits during the last 4 day(s) which contain a total of 33 files changed, 2433 insertions(+), 161 deletions(-). The main changes are: 1) Allow for adding TCP listen sockets into sock_map/hash so they can be used with reuseport BPF programs, from Jakub Sitnicki. 2) Add a new bpf_program__set_attach_target() helper for adding libbpf support to specify the tracepoint/function dynamically, from Eelco Chaudron. 3) Add bpf_read_branch_records() BPF helper which helps use cases like profile guided optimizations, from Daniel Xu. 4) Enable bpf_perf_event_read_value() in all tracing programs, from Song Liu. 5) Relax BTF mandatory check if only used for libbpf itself e.g. to process BTF defined maps, from Andrii Nakryiko. 6) Move BPF selftests -mcpu compilation attribute from 'probe' to 'v3' as it has been observed that former fails in envs with low memlock, from Yonghong Song. ==================== Signed-off-by: David S. Miller <[email protected]>
- Loading branch information
Showing
33 changed files
with
2,433 additions
and
161 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,11 +20,11 @@ Reporting bugs | |
Q: How do I report bugs for BPF kernel code? | ||
-------------------------------------------- | ||
A: Since all BPF kernel development as well as bpftool and iproute2 BPF | ||
loader development happens through the netdev kernel mailing list, | ||
loader development happens through the bpf kernel mailing list, | ||
please report any found issues around BPF to the following mailing | ||
list: | ||
|
||
netdev@vger.kernel.org | ||
bpf@vger.kernel.org | ||
|
||
This may also include issues related to XDP, BPF tracing, etc. | ||
|
||
|
@@ -46,17 +46,12 @@ Submitting patches | |
|
||
Q: To which mailing list do I need to submit my BPF patches? | ||
------------------------------------------------------------ | ||
A: Please submit your BPF patches to the netdev kernel mailing list: | ||
A: Please submit your BPF patches to the bpf kernel mailing list: | ||
|
||
[email protected] | ||
|
||
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. | ||
[email protected] | ||
|
||
In case your patch has changes in various different subsystems (e.g. | ||
tracing, security, etc), make sure to Cc the related kernel mailing | ||
networking, 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. | ||
|
||
|
@@ -168,7 +163,7 @@ a BPF point of view. | |
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 | ||
On the bpf 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 | ||
|
@@ -494,15 +489,15 @@ A: You need cmake and gcc-c++ as build requisites for LLVM. Once you have | |
that set up, proceed with building the latest LLVM and clang version | ||
from the git repositories:: | ||
|
||
$ 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" \ | ||
$ git clone https://github.com/llvm/llvm-project.git | ||
$ mkdir -p llvm-project/llvm/build/install | ||
$ cd llvm-project/llvm/build | ||
$ cmake .. -G "Ninja" -DLLVM_TARGETS_TO_BUILD="BPF;X86" \ | ||
-DLLVM_ENABLE_PROJECTS="clang" \ | ||
-DBUILD_SHARED_LIBS=OFF \ | ||
-DCMAKE_BUILD_TYPE=Release \ | ||
-DLLVM_BUILD_RUNTIME=OFF | ||
$ make -j $(getconf _NPROCESSORS_ONLN) | ||
$ ninja | ||
|
||
The built binaries can then be found in the build/bin/ directory, where | ||
you can point the PATH variable to. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.