intel_gpu: move destruction functions #231
Closed
Conversation
This file contains 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
Implements PAPI_destroy_eventset() functionality for the intel_gpu component. The functions used to free data structures used in the Level Zero API should only be called when an eventset is being destroyed; whereas, they were erroneously being called upon PAPI_stop(). These changes have been tested on the Intel Ponte Vecchio architecture.
|
Closing this PR to create a more comprehensive one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Description
Implements PAPI_destroy_eventset() functionality for the intel_gpu component.
The functions used to free data structures used in the Level Zero API should only be called when an eventset is being destroyed; whereas, they were erroneously being called upon PAPI_stop().
This Pull Request addresses Issue #227.
These changes have been tested on the Intel Ponte Vecchio architecture.
Author Checklist
Why this PR exists. Reference all relevant information, including background, issues, test failures, etc
Commits are self contained and only do one thing
Commits have a header of the form:
module: short descriptionCommits have a body (whenever relevant) containing a detailed description of the addressed problem and its solution
The PR needs to pass all the tests