tp: android_probes_parser pushes events into TraceSorter #3215
Conversation
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
LalitMaganti
reviewed
Oct 8, 2025
LalitMaganti
approved these changes
Oct 8, 2025
rsavitski
approved these changes
Oct 8, 2025
Member
rsavitski
left a comment
rsavitski
left a comment
There was a problem hiding this comment.
LGTM without having looked into specifics of a trace with these packets.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Refactor the android_probes parser to correctly handle out-of-order events by pushing the data through TraceSorter.
Instead of parsing power_rails and android_log packets immediately, the module now breaks them into individual events, wraps each one in a new TracePacket, and pushes them to the sorter's queue.