-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix wrong device_id computation in identifier_from_devid #4694
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do we know this is less wrong than the code that was there before?
I'll add a code comment that explains the bit range assignments. |
2576dc7
to
266e51e
Compare
@dalg24 This shows equivalence. |
retest this please |
266e51e
to
71ac133
Compare
1860280
to
54c07ed
Compare
Added unit test coverage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me (only minor nitpicking in the comments).
Co-authored-by: Daniel Arndt <[email protected]>
d3efcd0
to
d9170c0
Compare
@janciesko I am working with the current development branch of Kokkos and the ROCm 5.0.2 compiler... and for my HIP kernels, I am now getting the wrong device type and id. Instead of getting HIP and device 0, I am getting Serial and device 3. I have updated my code to match what is in the PR test example, but I'm still getting the wrong info. Did something else change? |
btw, I know that Kokkos git hash e5a8acc gives what I am expecting... |
@Rombur - do you maybe know what might have changed in the HIP backend in respect to obtaining device Id and device type? |
No I don't know anything that could have change that |
@janciesko @Rombur With the current master, I am running HIP kernels on device 0. The "device ID" passed to our profiler has the value 393217. That is being translated (by the above code) as a Serial kernel (0), on device 3, instance 1. That is incorrect...is the device getting constructed differently by Kokkos, or being interpreted incorrectly? 393217 is:
The value should be:
...right? This has changed since the last Kokkos release (3.5). |
Fixes: #4455