Don't aggregate kernel records into hipLaunch parent#182
Open
michaelmckinsey1 wants to merge 1 commit into
Open
Don't aggregate kernel records into hipLaunch parent#182michaelmckinsey1 wants to merge 1 commit into
michaelmckinsey1 wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently, records profiled from different threads, like rocm gputime + rocprofiler counters will result in counters being aggregated into the
hipLaunchKernelregion.(The red shows where this PR is moving the data)
This is problematic if there are multiple kernels launched within a single cpu region, because we cannot distinguish their counters once they are aggregated.