i#5505 kernel tracing: Add flag to configure PT buffer size #6936
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
Adds a new drmemtrace command-line flag that allows setting an appropriate size for the buffer used to collect PT data: -pt_ring_buffer_size_shift. For apps with a high thread count, a large value may cause OOMs. At the same time, a too low value causes issues during trace decode. Issue: #5505
derekbruening
approved these changes
Aug 26, 2024
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.
Adds a new drmemtrace command-line flag that allows setting an appropriate size for the buffer used to collect PT kernel trace data during online trace collection: -kernel_trace_buffer_size_shift.
For apps with a high thread count, a large value may cause OOMs. At the same time, a too low value causes issues during trace decode. The new flag allows tuning it as needed.
Verified that the PT related tests continue to work on a system that supports the Intel-PT hardware feature:
Issue: #5505