cuda: Allow for and restrict use of Cuda Toolkits to >= 11.4.#560
Open
Treece-Burgess wants to merge 1 commit intoicl-utk-edu:masterfrom
Open
cuda: Allow for and restrict use of Cuda Toolkits to >= 11.4.#560Treece-Burgess wants to merge 1 commit intoicl-utk-edu:masterfrom
Treece-Burgess wants to merge 1 commit intoicl-utk-edu:masterfrom
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
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
In the master branch, the
cudacomponent supports down to Cuda Toolkit 11.5; however, support can go down even further to Cuda Toolkit 11.3 when the MetricsEvaluator API was initially introduced.This PR adds support for Cuda Toolkit 11.4 and also restricts users at runtime to need to use Cuda Toolkits >= 11.4. The restriction is added as Cuda Toolkit 11.3 suffers from the same issue as discussed on the following NVIDIA Developers Forum post. From my testing 11.4 does not suffer from this.
Testing
Setup
Testing was done on Athena at Oregon, with the following setup:
Results
*
papi_component_avail,papi_native_avail, andpapi_command_lineAuthor 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