[L0 v2] use UMF in urUSMGetMemAllocInfo

[igchor]

No description provided.

[igchor]

@pbalcer this also bumps the UMF version. Is it OK to do this now (and in this PR?)?

[pbalcer]

@pbalcer this also bumps the UMF version. Is it OK to do this now (and in this PR?)?

Depends on whether there were any breaking changes between current and latest version. If there weren't, then it's fine.

[igchor]

@pbalcer this also bumps the UMF version. Is it OK to do this now (and in this PR?)?

Depends on whether there were any breaking changes between current and latest version. If there weren't, then it's fine.

The umf_memory_provider_ops_t was modified (oneapi-src/unified-memory-framework@3112e2b), and I believe this is a breaking change. I'll convert the PR to draft until it's safe to bump the UMF.

[pbalcer]

This is blocked by #2546

[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.