-
Notifications
You must be signed in to change notification settings - Fork 769
[SYCL][WIP] Extend select_device to take parameters #2241
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
Conversation
This PR allows users to request a specific device of their choice, in terms of device_type, backend, and device_num. select_device now can take 3 OPTIONAL parameters for this purpose. When these 3 parameters are specified, the user can pin down a specific device on which they want to run a kernel. SYCL_DEVICE_TRIPLE will also affect this api, and filters out unspecified devices. If any device that can satisfy the paraemters, it will fall back to the default heuristic approach. (current implemantion) Signed-off-by: Byoungro So <[email protected]>
Signed-off-by: Byoungro So <[email protected]>
Signed-off-by: Byoungro So <[email protected]>
// Checks that only designated plugins are loaded when SYCL_DEVICE_TRIPLE is | ||
// set. Checks that all different device types can be acquired from | ||
// select_device() | ||
// UNSUPPORTED: windows |
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.
Why?
Will there be a dedicated test for windows platform?
Why are we changing the SYCL APIs? We should not do this. |
The name |
Signed-off-by: Byoungro So <[email protected]>
Please stop pursuing this path. |
@bso-intel, should we close this PR? |
Yes, I will have to open another PR for similar work later. |
[L0 v2] implement native APIs and urMemBufferPartition
This PR allows users to request a specific device of their choice,
in terms of device_type, backend, and device_num.
select_device now can take 3 OPTIONAL parameters for this purpose, so keeping backward compatibility.
When these 3 parameters are specified, the user can pin down a specific device on which they want to run a kernel.
A new env var SYCL_DEVICE_TRIPLES will also affect this api, and filters out unspecified devices.
If any device that can satisfy the parameters is not found, it will fall back to the default heuristic approach. (current implementation)
Signed-off-by: Byoungro So [email protected]