-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Don't launch wrapped kernels on devices other than the wrapper's #288
Labels
Comments
eyalroz
added a commit
that referenced
this issue
Dec 13, 2021
…rapped-kernel-vs-stream device match.
eyalroz
added a commit
that referenced
this issue
Dec 13, 2021
…rapped-kernel-vs-stream device match.
eyalroz
added a commit
that referenced
this issue
Dec 13, 2021
…rapped-kernel-vs-stream device match.
eyalroz
added a commit
that referenced
this issue
Dec 14, 2021
…rapped-kernel-vs-stream device match.
eyalroz
added a commit
that referenced
this issue
Dec 19, 2021
…rapped-kernel-vs-stream device match.
eyalroz
added a commit
that referenced
this issue
Dec 28, 2021
…rapped-kernel-vs-stream device match.
eyalroz
added a commit
that referenced
this issue
Jan 14, 2022
…rapped-kernel-vs-stream device match.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With #186, we have made wrapped kernels be associated with a specific device. While I'm having some second thoughts about that, I haven't decided to undo that decision. However - the launch functions currently ignore that association - as the pointer can be used to enqueue execution on another device altogether. We need to enforce the restriction somehow.
The text was updated successfully, but these errors were encountered: