-
Notifications
You must be signed in to change notification settings - Fork 123
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
[HIP] Hip adapter multi dev ctx #999
Conversation
source/ur/ur.hpp
Outdated
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.
We'll need to sync changes to this file with the changes in #997
Are you sure this is only multi device context, some of the changes look familiar, maybe the |
864294c
to
ebdb923
Compare
If this is dependant on the |
This depends on the |
Sure, will do. Consider marking PR as |
ebdb923
to
263d84b
Compare
@@ -1 +1,2 @@ | |||
urContextCreateWithNativeHandleTest.Success/AMD_HIP_BACKEND___{{.*}}_ | |||
urContextGetInfoTestWithInfoParam.Success/AMD_HIP_BACKEND___{{.*}} |
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.
The size of the Devices
returned has changed as we now have a vector of devices. Whereas before we just had a pointer. This is backend specific so I think maybe just keep this as failing for now
urMemGetInfoTest.InvalidNullPointerPropSizeRet/AMD_HIP_BACKEND___{{.*}} | ||
urMemGetInfoTest.InvalidNullPointerPropSizeRet/AMD_HIP_BACKEND___{{.*}} | ||
urMemImageCreateTest.InvalidSize/AMD_HIP_BACKEND___{{.*}} | ||
urMemImageGetInfoTest.Success/AMD_HIP_BACKEND___{{.*}} |
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.
These MemImageGetInfo
s are unsupported
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.
Sounds like this test needs to allow these being unsupported. I can look into that.
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.
OK great. Will I change this .match
or just add a TODO?
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.
I expect it'll be a separate PR so this line will need to stay in the .match
file in order to pass testing. I don't actually know if these .match
files support comments.
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.
#1144 is the PR that will address this CTS issue. Can resolve this discussion, I think.
urMemGetInfoTest.InvalidNullPointerParamValue/AMD_HIP_BACKEND___{{.*}} | ||
urMemGetInfoTest.InvalidNullPointerPropSizeRet/AMD_HIP_BACKEND___{{.*}} | ||
urMemGetInfoTest.InvalidNullPointerPropSizeRet/AMD_HIP_BACKEND___{{.*}} | ||
urMemImageCreateTest.InvalidSize/AMD_HIP_BACKEND___{{.*}} |
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.
I'm not sure how to deal with this thing. Perhaps we need to query the max image width depth etc when a device is initialized so we can check vals against this at Image creation
urMemBufferCreateWithNativeHandleTest.Success/AMD_HIP_BACKEND___{{.*}}_ | ||
Segmentation fault | ||
urMemGetInfoTest.Success/AMD_HIP_BACKEND___{{.*}} | ||
urMemGetInfoTest.InvalidNullPointerParamValue/AMD_HIP_BACKEND___{{.*}} |
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.
These are returning early in the adapter, see here https://github.com/oneapi-src/unified-runtime/blob/adapters/source/loader/layers/validation/ur_valddi.cpp#L1350 so the adapter entry point is never called
263d84b
to
32419b6
Compare
cf65a5d
to
3743e6c
Compare
b4bd0f4
to
b811c86
Compare
b811c86
to
8de5817
Compare
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.
That's quite a heavy lifting you've done here, well done!
285e286
to
7e975e9
Compare
The merge conflicts will need to be resolve. |
5ab1690
to
3934569
Compare
@kbenzie have rebased |
intel/llvm#11739 DPC++ PR here |
3934569
to
7118ac6
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## adapters #999 +/- ##
=========================================
Coverage 15.79% 15.79%
=========================================
Files 223 223
Lines 31351 31351
Branches 3511 3511
=========================================
Hits 4951 4951
Misses 26349 26349
Partials 51 51 ☔ View full report in Codecov by Sentry. |
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.
Couple of warnings treated as errors causing the GHA failure.
Oops thanks for that @kbenzie |
a2b5a00
to
f0e0be2
Compare
Update SHA for oneapi-src/unified-runtime#999 UR hip adapter multi device context --------- Co-authored-by: Kenneth Benzie (Benie) <[email protected]>
Moving intel/llvm#11105 into UR repo with a few changes. Depends on #961
The getter func for ptrs/arrays/surfaces now allocates lazily if needed. This has made code a lot cleaner.