btf: Do not use <linux/types.h> for resolving tracepoint defs #1318
Conversation
This file contains 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
Passing --btf should mean bpftrace does not use system headers at all. The only exception should be if the user manually does an `#include`. To that end, this patch has TracepointFormatParser use the existing BTF infrastructure to resolve basic types we used to get from <linux/types.h> instead of doing header inclusions. This is particularly important in container environments where kernel headers may not be installed.
|
makes sense and looks good |
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.
Passing --btf should mean bpftrace does not use system headers at all.
The only exception should be if the user manually does an
#include.To that end, this patch has TracepointFormatParser use the existing
BTF infrastructure to resolve basic types we used to get from
<linux/types.h> instead of doing header inclusions.
This is particularly important in container environments where kernel
headers may not be installed.
Checklist
docs/reference_guide.mdCHANGELOG.md