-
Notifications
You must be signed in to change notification settings - Fork 181
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
Support tracing tc-bpf #271
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's very nice! 🎉 Small nits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much! This really paves the way for bpf_helper_tracing and bpf_tailcall_tracing. I left a comment to understand if it's the new field is necessary.
Add an option --filter-trace-tc to trace all tc-bpf progs on host by fentry-ing on the progs. To trace tc-bpf, we list all tc-bpf progs first. Then, for each prog, we have to retrieve its entry function name as fentry attaching function. Next, we do fentry on the prog. Example: ... [<empty>] dummy Signed-off-by: Leon Hwang <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
This PR supports tracing tc-bpf as discussion in #239 .
Its running result likes: