Age | Commit message (Collapse) | Author |
|
mainline-adbd-release
Change-Id: Id15f6fe0b3b758cd93b601eda0908fdebc8a479f
|
|
a56611f62a am: c2146834c2
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052236
Change-Id: I5d2ae66ed1b1df106679f0455c02c8a9cfc40513
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
c209d5184c am: f8d3d1d682 am: 5669ac1c10
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052235
Change-Id: I4dd7f3fa827c11df134c41a41b4aa3f890466b7a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
9ea0fe0760 am: 39756b8a77 am: a1b07ca191
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052234
Change-Id: I020579412faae34431fbb6a9f3db9be44addc0bb
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
am: f8a37723ec am: 5cca59d08a
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052233
Change-Id: Ifa7ee6a55e450a646f2ba3bcf0423139800a508a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
a56611f62a
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052236
Change-Id: I88f3a0d6dcb7453b15a71d9c530b8683bfbebf50
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
c209d5184c am: f8d3d1d682
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052235
Change-Id: I1751a58a9fec35897005f14e12642c3c87c5f930
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
9ea0fe0760 am: 39756b8a77
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052234
Change-Id: I2b840a0a240f154ab483dfea75805ec38432cd8b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
am: f8a37723ec
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052233
Change-Id: Ib34e3e1de86d691ccb59b4798f2887a54da88680
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052236
Change-Id: I421a8f2f38b02d268cdfeac16246b42b4a909d8a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
c209d5184c
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052235
Change-Id: I99f77cd1800063c9aaf4084a8ffc3fdb9f21c95e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052234
Change-Id: Ib10d340886cfd5b278953081ed133700c01d5999
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052233
Change-Id: Ib9981a33d1bf7cd20a368dd01499eca5b84aa158
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052236
Change-Id: I4540cbf2ca9a6e21307281a8822bb4ff71dec62f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052235
Change-Id: Ia039bfd656d0d04a8725f65f7081d6fab5364382
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052234
Change-Id: Ie71ded1b322ec2b35d45d2b9d6719dda1591d546
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2052233
Change-Id: Ibf61deadbdbaac618d9d388eb9dafd38fbaf55d1
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Build 7 more tools confirmed to build & run successfully on android
Test: m drsnoop fsdist fsslower oomkill solisten tcprtt vfsstat
Test: run tools
Signed-off-by: Connor O'Brien <connoro@google.com>
Change-Id: I40a9ba2c25a1e4129f8d820afdd9c9842b19bd78
|
|
vfsstat expects positional arguments to have arg_num starting from 0,
so update argp_parse accordingly
Signed-off-by: Connor O'Brien <connoro@google.com>
Change-Id: Ifb78d13ce638bfb9ba3ec857864fbbbc92e5720f
|
|
libbpf_bcc changes can break program loading, so add presubmit testing
to prevent that.
Test: atest --test-mapping external/bcc/src/cc
Signed-off-by: Connor O'Brien <connoro@google.com>
Change-Id: I4afba466f00a691929b1f20265a21de21a27cf53
|
|
Signed-off-by: Connor O'Brien <connoro@google.com>
Change-Id: I0ac126de9aeb13b9eb306a4ad8cea0212aadbc80
|
|
libbpf-tools: improve fentry_exists check
|
|
|
|
|
|
|
|
add tcp congestion control status duration statistic tool, and it can be used to evaluate the networking and congestion algorithm performance.
|
|
|
|
|
|
On architectures that lack support for fentry programs, tools should
fall back to using kprobes even if the kernel version is new enough to
include BPF_TRACE_FENTRY, but fentry_exists() cannot currently detect
this case.
Instead of searching for BPF_TRACE_FENTRY, verify that attaching a
BPF_TRACE_FENTRY program can actually succeed. Rename fentry_exists to
fentry_can_attach to reflect this change.
Signed-off-by: Connor O'Brien <connoro@google.com>
Change-Id: I5ad0341cb060c7a4a2ee17245337170963dfefad
|
|
Sync with latest libbpf repo. The sync'ed top libbpf repo
commit is:
67a4b1464349 ci: remove subprogs from 5.5 whitelist
Signed-off-by: Yonghong Song <yhs@fb.com>
|
|
|
|
As reported in #3913, vfs_fsync is never triggered when fsync is called.
Use vfscount can reveal that:
sudo python3 ./vfscount.py
Tracing... Ctrl-C to end.
^C
ADDR FUNC COUNT
ffffffff8ad23621 b'vfs_writev' 2
ffffffff8ad29df1 b'vfs_getattr_nosec' 55
ffffffff8ad20401 b'vfs_open' 58
ffffffff8ad2a7b1 b'vfs_statx' 91
ffffffff8ad641d1 b'vfs_fsync_range' 1802
ffffffff8ad22111 b'vfs_read' 1900
ffffffff8ad22551 b'vfs_write' 3752
Let's use vfs_fsync_range instead to trace fsync operations.
Closes #3913.
Signed-off-by: Hengqi Chen <chenhengqi@outlook.com>
|
|
|
|
libbpf-tools: convert BCC tcpsynbl to BPF CO-RE version
|
|
usdt: support xmm registers as args for x64
|
|
Support for using xmm registers for USDT args was added to systemtap in
early 2021 (commit 04c99d0d0267f574fa60044c96933b0dd3846aa1 added xmm0-7
and eaa15b047688175a94e3ae796529785a3a0af208 added xmm8-15). As a result
these registers are showing up in probe descriptors on Fedora.
pthread_start probe description on Ubuntu 20.04:
```
stapsdt 0x00000052 NT_STAPSDT (SystemTap probe descriptors)
Provider: libpthread
Name: pthread_start
Location: 0x00000000000095e9, Base: 0x000000000001922c, Semaphore: 0x0000000000000000
Arguments: 8@%rax 8@1600(%rax) 8@1608(%rax)
```
And in the Fedora test container:
```
```
stapsdt 0x00000053 NT_STAPSDT (SystemTap probe descriptors)
Provider: libpthread
Name: pthread_start
Location: 0x0000000000009280, Base: 0x0000000000016cbc, Semaphore: 0x0000000000000000
Arguments: 8@%xmm0 8@1600(%rax) 8@1608(%rax)
```
bcc doesn't recognize these registers so it's unable to generate code to fetch arguments which use these registers for storage. Add support for XMM0-15.
This should fix `lib/uthreads.py` test, which uses `pthread_start` and therefore fails to generate program on Fedora.
Signed-off-by: Dave Marchevsky <davemarchevsky@fb.com>
|
|
commit 531b698cdc20 ("libbpf-tools: Enable compilation warnings for
BPF programs") applies CFLAGS to all targets. However, some of the c
flags typically used by distribution are not available to the bpf
target. Add a new BPFCFLAGS macro to take care of that.
Fixes the following compilation error on fedora:
BPF bashreadline.bpf.o
clang-13: warning: optimization flag '-ffat-lto-objects' is not supported [-Wignored-optimization-argument]
clang-13: warning: argument unused during compilation: '-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1' [-Wunused-command-line-argument]
clang-13: warning: argument unused during compilation: '-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1' [-Wunused-command-line-argument]
clang-13: warning: argument unused during compilation: '-fstack-clash-protection' [-Wunused-command-line-argument]
error: option 'cf-protection=return' cannot be specified on this target
error: option 'cf-protection=branch' cannot be specified on this target
2 errors generated.
|
|
|
|
btf__get_map_kv_tids() is deprecated and causes annoying compilation warnings.
Reimplement it in BCC.
Signed-off-by: Hengqi Chen <chenhengqi@outlook.com>
|
|
|
|
|
|
llvm upstream patch https://reviews.llvm.org/D118652
did some header file cleanup and this breaks bcc with llvm15
with the following compilation error:
/.../src/cc/bpf_module.cc: In member function ‘void ebpf::BPFModule::dump_ir(llvm::Module&)’:
/.../src/cc/bpf_module.cc:231:39: error: no matching function for call to ‘llvm::legacy::PassManager::add(llvm::Module Pass*)’
PM.add(createPrintModulePass(errs()));
^
In file included from /.../src/cc/bpf_module.cc:25:
/.../include/llvm/IR/LegacyPassManager.h:58:8: note: candidate: ‘virtual void llvm::legacy::PassManager::add(llvm::Pass*)’
void add(Pass *P) override;
^~~
/.../include/llvm/IR/LegacyPassManager.h:58:8: note: no known conversion for argument 1 from ‘llvm::ModulePass*’ to ‘llvm::Pass*’
Adding the include path "llvm/Pass.h" in bpf_module.cc fixed the issue.
Signed-off-by: Yonghong Song <yhs@fb.com>
|
|
The tool cachestat is broken on kernel 5.15 due to kernel function
renaming. Fix the tool by detecting symbol existence. See #3687 and
#3692.
Signed-off-by: Hengqi Chen <chenhengqi@outlook.com>
|
|
|
|
During 5.17 dev cycle, the kernel dropped request->rq_disk. It can now be
accessed through request->q->disk. Fix the python ones in tools/. There are
more usages in other places which need to be fixed too.
Signed-off-by: Tejun Heo <tj@kernel.org>
|
|
|
|
|
|
|
|
d6e70a9dfb am: d82de6b621 am: abb1c0844a
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2007437
Change-Id: I8ea4bc703777b70410d90b39bca4f335ee23064c
|
|
d6e70a9dfb am: d82de6b621
Original change: https://android-review.googlesource.com/c/platform/external/bcc/+/2007437
Change-Id: I61aa9cb962dbd7ae6d31c46c3637a0ee79fb6cf7
|