Conversation
Member
jschwinger233
left a comment
There was a problem hiding this comment.
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]>
jschwinger233
approved these changes
Oct 21, 2023
jschwinger233
approved these changes
Oct 23, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR supports tracing tc-bpf as discussion in #239 .
Its running result likes: