-
Notifications
You must be signed in to change notification settings - Fork 116
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
[UR] Enable UMF tracking by default #1071
Conversation
8b3a8a4
to
c13bb66
Compare
I think this is ready to be merged. The failing tests turned out to just be tests that unexpectedly succeeded (most of the CUDA and L0 tests with UsePoolEnabled work after this change). |
At this moment, if someone sets |
@lukaszstolarczuk you are right, but I think I would actually prefer to do this after we merge / cherry-pick this change. Removing the option would also mean that we can remove some of the existing code so the change would be bigger. |
Fixes to test-usm in L0 in #1105 depending on this patch. |
I think we can just target adapters for now. I'm hoping we can merged adapters into main branch soon and then stop using the adapters branch so this problem will go away. |
Done. Do we want to wait until changes from #1084 are cherry-picked? If we merge this first, there might be some extra Windows failures. |
If that's a dependency, then yes. |
eca0bfc
to
07ca188
Compare
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## adapters #1071 +/- ##
============================================
- Coverage 15.79% 15.79% -0.01%
============================================
Files 223 223
Lines 31351 31365 +14
Branches 3511 3511
============================================
+ Hits 4951 4953 +2
- Misses 26349 26361 +12
Partials 51 51 ☔ View full report in Codecov by Sentry. |
@igchor any idea why the checks failed? |
It is needed by adapters's urUSMFree implementations where we rely on umfPoolByPtr (which always returns null if tracking is disabled).
@kbenzie there was a conflict in test/conformance/kernel/kernel_adapter_level_zero.match. It should be fixed now and there's one less test failing for L0 kernel test. |
Thanks @igchor |
I have updated the target branch of this PR from the |
[UR] Enable UMF tracking by default
Combines the changes of the follow Unified Runtime pull requests: * oneapi-src/unified-runtime#1108 * oneapi-src/unified-runtime#988 * oneapi-src/unified-runtime#1071 * oneapi-src/unified-runtime#916 * oneapi-src/unified-runtime#1099
Combines the changes of the follow Unified Runtime pull requests: * oneapi-src/unified-runtime#1108 * oneapi-src/unified-runtime#988 * oneapi-src/unified-runtime#1071 * oneapi-src/unified-runtime#916 * oneapi-src/unified-runtime#1099
[UR] Enable UMF tracking by default
Combines the changes of the follow Unified Runtime pull requests: * oneapi-src/unified-runtime#1108 * oneapi-src/unified-runtime#988 * oneapi-src/unified-runtime#1071 * oneapi-src/unified-runtime#916 * oneapi-src/unified-runtime#1099
It is needed by adapters's urUSMFree implementations where we rely on umfPoolByPtr (which always returns null if tracking is disabled).
@kbenzie should I also make a PR to the main branch? We plan to move the UMF to a separate repo anyway and I expect this option (UMF_ENABLE_POOL_TRACKING) to not be publicly exposed to UR users anymore.