If ONEAPI_DEVICE_SELECTOR requested cpu/fpga devices, do NOT load L0/…

[ytzhang1]

…Cuda/Hip backends

Hi, there's an issue with the current implementation in UR, that even if ONEAPI_DEVICE_SELECTOR specified only cpu devices, like *:cpu , the gpu devices are still enumerated and processes are created on these devices which consume some unnecessary resources (a lot of vram in some cases). The issue is that UR only checks the backend types, but ignores device types. There's some customer complaining about this behavior of our runtime stack (reported JIRA already). please review.

[martygrant]

Unified Runtime -> intel/llvm Repo Move Notice

Information

The source code of Unified Runtime has been moved to intel/llvm under the unified-runtime top-level directory,
all future development will now be carried out there. This was done in intel/llvm#17043.

The code will be mirrored to oneapi-src/unified-runtime and the specification will continue to be hosted at oneapi-src.github.io/unified-runtime.

The contribution guide has been updated with new instructions for contributing to Unified Runtime.

PR Migration

All open PRs including this one will be labelled auto-close and shall be automatically closed after 30 days.
To allow for some breathing space, this automation will not be enabled until next week (27/02/2025).

Should you wish to continue with your PR you will need to migrate it to intel/llvm.
We have provided a script to help automate this process.

---

This is an automated comment.