Skip to content

[SYCL][UR][L0] Use leak checker and API logging (for v2) from loader #17536

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

Merged
merged 6 commits into from
May 7, 2025

Conversation

igchor
Copy link
Member

@igchor igchor commented Mar 19, 2025

No description provided.

@igchor igchor requested review from a team as code owners March 19, 2025 15:48
@igchor igchor requested a review from sergey-semenov March 19, 2025 15:48
@igchor igchor marked this pull request as draft March 19, 2025 15:48
@igchor igchor force-pushed the leak_checker_from_loader branch from 38e60db to 5db0da7 Compare April 28, 2025 15:43
@igchor igchor marked this pull request as ready for review April 28, 2025 15:43
@igchor igchor requested a review from a team as a code owner April 28, 2025 15:43
@igchor igchor force-pushed the leak_checker_from_loader branch from 5db0da7 to 15db475 Compare April 28, 2025 16:08
@igchor igchor temporarily deployed to WindowsCILock April 28, 2025 16:08 — with GitHub Actions Inactive
@igchor igchor temporarily deployed to WindowsCILock April 28, 2025 16:20 — with GitHub Actions Inactive
@igchor igchor force-pushed the leak_checker_from_loader branch from 15db475 to 578ae99 Compare April 30, 2025 00:02
@igchor igchor temporarily deployed to WindowsCILock April 30, 2025 00:02 — with GitHub Actions Inactive
@igchor igchor temporarily deployed to WindowsCILock April 30, 2025 00:12 — with GitHub Actions Inactive
This ensures that calls to L0 made through UMF and user code
are also tracked.
@igchor igchor force-pushed the leak_checker_from_loader branch from 578ae99 to 0794cc0 Compare April 30, 2025 18:26
@igchor igchor requested a review from a team as a code owner April 30, 2025 18:26
@igchor igchor requested a review from Bensuo April 30, 2025 18:26
@igchor igchor temporarily deployed to WindowsCILock April 30, 2025 18:27 — with GitHub Actions Inactive
@igchor igchor temporarily deployed to WindowsCILock April 30, 2025 18:47 — with GitHub Actions Inactive
@igchor igchor force-pushed the leak_checker_from_loader branch from 0794cc0 to 9610315 Compare April 30, 2025 22:10
@igchor igchor temporarily deployed to WindowsCILock April 30, 2025 22:11 — with GitHub Actions Inactive
@igchor igchor temporarily deployed to WindowsCILock April 30, 2025 22:22 — with GitHub Actions Inactive
@igchor igchor force-pushed the leak_checker_from_loader branch from 9610315 to 866ca61 Compare May 1, 2025 01:11
@igchor igchor temporarily deployed to WindowsCILock May 1, 2025 01:11 — with GitHub Actions Inactive
@igchor igchor temporarily deployed to WindowsCILock May 1, 2025 01:29 — with GitHub Actions Inactive
igchor added 4 commits May 1, 2025 02:11
Account for the fact that when using API loggin from L0 loader,
calls to zeMemFree from the test are also tracked.
UR internally sets env variables to control behavior or L0 loader
(e.g. enabling validation layer). If zeInit in test is called first
the vars will have no effect.
@igchor igchor temporarily deployed to WindowsCILock May 1, 2025 20:36 — with GitHub Actions Inactive
@igchor igchor temporarily deployed to WindowsCILock May 1, 2025 20:52 — with GitHub Actions Inactive
@igchor igchor temporarily deployed to WindowsCILock May 1, 2025 21:03 — with GitHub Actions Inactive
@igchor igchor temporarily deployed to WindowsCILock May 1, 2025 21:03 — with GitHub Actions Inactive
The adapter sets certain env variables during adapter init.
Preloding it will set those variables and result in
unexpected behavior for the legacy adater.
Copy link
Contributor

@Bensuo Bensuo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Graphs changes LGTM.

@igchor
Copy link
Member Author

igchor commented May 7, 2025

@intel/llvm-gatekeepers this should be ready for merge

@aelovikov-intel aelovikov-intel merged commit b0b48a4 into intel:sycl May 7, 2025
34 checks passed
igchor added a commit to igchor/llvm that referenced this pull request May 12, 2025
…r v2) from loader (intel#17536)"

This reverts commit b0b48a4
(except for test changes). The internal testing failed because
the L0 loader used, was older than 1.21.2 (and didn't have
leak checking implemented).

I did not revert changes in the tests as that doesn't make
any difference and it will be easier to reapply the patch
in the future.
aelovikov-intel pushed a commit that referenced this pull request May 13, 2025
#18429)

…r v2) from loader (#17536)"

This reverts commit b0b48a4 (except for
test changes). The internal testing failed because the L0 loader used,
was older than 1.21.2 (and didn't have leak checking implemented).

I did not revert changes in the tests as that doesn't make any
difference and it will be easier to reapply the patch in the future.
sarnex pushed a commit that referenced this pull request May 15, 2025
This reapplies some of the changes from
#17536 (without changes to
leak_checker which broke internal testing).

This fixes: #18463
github-actions bot pushed a commit to oneapi-src/unified-runtime that referenced this pull request May 16, 2025
This reapplies some of the changes from
intel/llvm#17536 (without changes to
leak_checker which broke internal testing).

This fixes: intel/llvm#18463
kbenzie pushed a commit to oneapi-src/unified-runtime that referenced this pull request May 19, 2025
This reapplies some of the changes from
intel/llvm#17536 (without changes to
leak_checker which broke internal testing).

This fixes: intel/llvm#18463
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants