TID-based overlap detection with dynamic range - #65
Merged
Merged
Conversation
Signed-off-by: Lars Schneidenbach <schneidenbach@us.ibm.com>
lasch
requested review from
WarningRan,
eklee15,
mcalman and
yuhaohaoyu
as code owners
November 26, 2025 21:31
mcalman
approved these changes
Dec 1, 2025
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
2 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.
We've encountered traces where thread ids occupy subsequent numbers (nothing unusual). If event overlap is detected in one tid and the subsequent tid is already in use, it can cause collisions, crashes and all kinds of weird behavior.
This PR extends the overlap treatment by adding a scanning stage to collect all tids with input events and then creates a mapping from existing to available tids for overlap resolution.