ROCM-1617 - Resolve potential issues with Drv memcpy tests #2859
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.
Motivation
The current CI occationally is flakey with failures due to UB, and correctness issues. This change addresses some of those issues in the memory tests
Technical Details
hipDrvMemcpy2DUnaligned.cc
* Reset parameters before each SECTION
* Free pinned host memory with hipHostFree not hipFree
* srcH and srcD need to check, that they are not nullptr's after malloc. Implemented this using RAII class LinearAllocGuard
hipDrvMemcpy3DAsync.cc
* Passes actually invalid pitch, i.e. MaxPitch + 1
hipDrvMemcpy3DAsync_old.cc
* Handle peer access enable/disable
* Allocate 3D memory correctly, currently missing depth we are just allocating 2D
* Reset parameters between SECTION's
* Construct stream, I think previously it was left uninitialized and all work was on the default stream
* Fix memory leak
hipDrvPtrGetAttributes.cc
* Type mismatchs
* remove incorrect nvidia test, with buffer overflow
JIRA ID
Partial solution: ROCM-1617
Test Plan
NA
Submission Checklist