Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Replace leak checker with L0 validation layer functionality #2603

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

Closed
wants to merge 2 commits into from

Conversation

igchor
Copy link
Member

@igchor igchor commented Jan 22, 2025

@igchor
Copy link
Member Author

igchor commented Jan 22, 2025

I'm not sure if we actually want to set env variables to enable L0 leak checking. I think we could just use the new env vars in SYCL tests (which is mostly where this feature is used).

@github-actions github-actions bot added the level-zero L0 adapter specific issues label Jan 22, 2025
instead, rely on logging provided by L0 loader.

Also, remove ZeCall and option to serialize all
L0 calls. It wasn't used correctly anyway, the function
call in ZE2UR_CALL* was done before taking the lock.
@igchor igchor force-pushed the level-zero-leak-checking branch from 2bb410a to 877e882 Compare February 7, 2025 20:58
@martygrant
Copy link
Contributor

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.

@igchor igchor closed this Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level-zero L0 adapter specific issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants