Implement basic leak checker in validation layer #264
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It is based on the ZeCallCount from UR. There are 2 main reasons for moving the leak checker to level-zero: 1. Some calls to L0 are done through UMF (not by UR directly) which means those calls would not be checked. 2. If an application using UR calls L0 directly, those calls will also not be checked. This happens for example in SYCL tests, where special cases need to be made for direct L0 calls. Signed-off-by: Igor Chorazewicz <igor.chorazewicz@intel.com>
nrspruit
approved these changes
Jan 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is based on the ZeCallCount from UR. There are 2 main reasons for moving the leak checker to level-zero: