DRM_IOCTL_XOCL_INFO_BO returns wrong size #8014
Merged
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
Signed-off-by: Manoj Takasi <[email protected]>
maxzhen
approved these changes
Mar 15, 2024
chvamshi-xilinx
approved these changes
Mar 16, 2024
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.
Problem solved by the commit
CR-1176062 xocl_info_bo_ioctl function returns the aligned size of bo to the user instead of original size.
Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered
When we export a usrptrBO where the size is not multiple of 4K, the imported buffer gets the aligned size of BO from get_properties(). This is invalid for userptr.
How problem was solved, alternative solutions (if any) and why they were rejected
Added variable to store the actual buffer size in xobj
Risks (if any) associated the changes in the commit
NA
What has been tested and how, request additional testing if necessary
Teseted on u250.
Documentation impact (if any)
NA