-
Notifications
You must be signed in to change notification settings - Fork 200
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
Properly handle cudaMemHandleTypeNone and cudaErrorInvalidValue in is_export_handle_type_supported #1055
Properly handle cudaMemHandleTypeNone and cudaErrorInvalidValue in is_export_handle_type_supported #1055
Conversation
Closes rapidsai#1054 Signed-off-by: Gera Shegalov <gera@apache.org>
Signed-off-by: Gera Shegalov <gera@apache.org>
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.
Thanks for the fix!
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.
Suggesting a more complete fix.
@harrism review Co-authored-by: Mark Harris <mharris@nvidia.com>
Signed-off-by: Gera Shegalov <gera@apache.org>
@gerashegalov please confirm this fixes #1054 before we merge. Thanks! |
just saw the internal thread, looks good to target 22.08 |
Signed-off-by: Gera Shegalov <gera@apache.org>
@harrism the fix has been confirmed with https://github.com/rapidsai/cudf/compare/branch-22.08...gerashegalov:rmmTest?expand=1#diff-707bbf4bad4194f1803f3586af0611546f6064a20561f68e34f74f30d2ec4f55L20-R27 |
@gpucibot merge |
@gpucibot merge |
cudaErrorInvalidValue
returned fromcudaDeviceGetAttribute
to returnfalse
fromis_export_handle_type_supported
cudaMemHandleTypeNone
Co-authored-by: @jrhemstad
Co-authored-by: @harrism
Closes #1054
Signed-off-by: Gera Shegalov gera@apache.org