Skip to content

[SYCL][ROCm] Fix freeing USM managed pointer with NVIDIA #4123

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

Closed
wants to merge 1 commit into from

Conversation

npmiller
Copy link
Contributor

@npmiller npmiller commented Jul 16, 2021

This patch works around a bug in the HIP API for NVidia where hipPointerGetAttributes doesn't know about managed pointers.

@npmiller npmiller requested a review from smaslov-intel as a code owner July 16, 2021 10:02
@bader
Copy link
Contributor

bader commented Jul 20, 2021

@smaslov-intel, ping.

type = hipPointerAttributeType.memoryType;
#ifdef __HIP_PLATFORM_NVIDIA__
// The NVIDIA hipPointerGetAttributes implementation doesn't know about
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about other calls to hipPointerGetAttributes which will continue to return error?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good point, I only ran into this call failing, but yeah it will happen with the others too, I'll update them

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please consider doing this adjustment in the function itself, if feasible

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a quick update on this patch, I'm currently looking at this and some of the other HIP workarounds in the ROCm plugin and figuring out if I can fix them in the HIP headers directly and submit the fixes to HIP upstream.

However I do think we'll probably still need the workarounds in the ROCm plugin, at least until the next HIP release and if my fixes get approved. So I'll come back to this patch in a bit and make it a proper workaround for all the other uses of hipPointerGetAttributes as well.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it changed up-stream?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@FMarno did we end up submitting a patch upstream for this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not yet, but it's one of the things we are looking at in the next couple weeks. I'll write a note to notify you when we do something about it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@npmiller looks like AMD put a patch in for this last week ROCm/hipamd@88f1622. You should be able to do a proper fix now.

@bader bader added the hip Issues related to execution on HIP backend. label Aug 4, 2021
@github-actions github-actions bot added the Stale label Feb 12, 2022
@github-actions github-actions bot closed this Apr 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hip Issues related to execution on HIP backend. Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants