New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add XDP support #239
Comments
How about supporting tc-bpf together? |
Do you mean tracing each individual BPF program? If yes, we are planning to do it for Cilium in the nearest future. |
Yes. Recently, I discussed with @jschwinger233 that 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. 😁 |
Got it, small world 😄 |
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 @Asphaltt , thanks for the update!
Great. I am curious what approach did you take (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? |
Sure #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. |
@mscastanho Hi, not sure whether @Asphaltt is working on it? |
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. |
Sure, I just wanted to clarify whether @mscastanho can take this issue 😅 |
Details TBD.
The text was updated successfully, but these errors were encountered: