pwru
pwru copied to clipboard
cilium
Add XDP support
Do you mean tracing each individual BPF program? If yes, we are planning to do it for Cilium in the nearest future.
Do you mean tracing each individual BPF program?
Yes.
Recently, I discussed with @jschwinger233 that pwru traces XDP and tc-bpf. I was writing some code at that time.
But, currently, I'm busy fixing a kernel-bpf bug.🤔
Martynas, this is the guy @Asphaltt who managed to trace bpf tailcalls using kernel module, as I mentioned this Tuesday. :grin:
Yeah, small world 😀
I'm afraid I can not help this issue for some time. I'm planning to do tailcalls tracing things after fixing the kernel-bpf bug.
Hi @brb ,
I'm glad to tell you that I just finished the POC of tracing TC bpf programs.
But, it's based on PR #266 and the latest go-ebpf library.
Recently, I'm fixing a tailcall issue of kernel-bpf whose progress is really slow. Then, I'm on this support now.
Hi @Asphaltt , thanks for the update!
I just finished the POC of tracing TC bpf programs
Great. I am curious what approach did you take (is it the same as Gray's one)?
is it the same as Gray's one
No. I trace TC bpf programs by listing then filtering all bpf progs.
Would you like to upgrade go-ebpf to latest version?
Would you like to upgrade go-ebpf to latest version?
Sure https://github.com/cilium/pwru/pull/269
Hi, is somebody actively working on this issue? If not, I volunteer to help, as I'm interested on this feature as well.
But I may need some assistance on the approach. I have tried to do a similar kind of filtered tracing on XDP programs using fentry/fexit on some personal projects before with no success. The verifier kept rejecting my program for invalid memory access when I tried to access packet data.
Hi, @brb, I will work on it when my PRs get merged. It'll be nice to work on it without other on-going PRs.
It'll be nice to work on it without other on-going PRs.
Sure, I just wanted to clarify whether @mscastanho can take this issue :sweat_smile: