Skip to content
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

Handling Devices Duplicated via Multiple Adapters #459

Closed
alycm opened this issue Apr 24, 2023 · 2 comments
Closed

Handling Devices Duplicated via Multiple Adapters #459

alycm opened this issue Apr 24, 2023 · 2 comments
Labels
loader Loader related feature/bug needs-discussion This needs further discussion specification Changes or additions to the specification
Milestone

Comments

@alycm
Copy link

alycm commented Apr 24, 2023

If a single hardware device is supported by multiple adapters, e.g. a GPU supporting Level Zero and OpenCL, then it could be enumerated multiple times.

Should such duplicates be filtered out so that a hardware device is only presented once, but if so how to prioritise which adapter to expose?

Should such duplicates be left and let the language runtime about handle it using UUIDs?

@kbenzie kbenzie added needs-discussion This needs further discussion loader Loader related feature/bug specification Changes or additions to the specification labels Apr 26, 2023
@kbenzie
Copy link
Contributor

kbenzie commented May 2, 2023

Possibly related to ONEAPI_DEVICE_SELECTOR #220

@alycm
Copy link
Author

alycm commented May 3, 2023

WG call discussion: Unified runtime should report everything it sees, even if that means reporting one device more than more. Higher levels handle it (or not).

@kbenzie kbenzie closed this as completed May 4, 2023
@kbenzie kbenzie added this to the 0.7 milestone Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
loader Loader related feature/bug needs-discussion This needs further discussion specification Changes or additions to the specification
Projects
None yet
Development

No branches or pull requests

2 participants