We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Under the following conditions, gdrdrv returns the same handle for two different pinned buffers:
The handle for the second buffer supersedes that of the first buffer. One scenario that this behavior becomes problematic is:
This will run correctly.
gdr_pin_buffer(g, first_buffer_ptr, first_buffer_size, 0, 0, &first_buffer_handle); gdr_map(g, first_buffer_handle, &first_buffer_map_ptr, first_buffer_size); gdr_pin_buffer(g, second_buffer_ptr, second_buffer_size, 0, 0, &second_buffer_handle);
This will fail because the offset of the second buffer is non-zero. But the failure happens when trying to map the first buffer!
gdr_pin_buffer(g, first_buffer_ptr, first_buffer_size, 0, 0, &first_buffer_handle); gdr_pin_buffer(g, second_buffer_ptr, second_buffer_size, 0, 0, &second_buffer_handle); gdr_map(g, first_buffer_handle, &first_buffer_map_ptr, first_buffer_size);
Code in #242 can be used to reproduce this bug.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Under the following conditions, gdrdrv returns the same handle for two different pinned buffers:
The handle for the second buffer supersedes that of the first buffer. One scenario that this behavior becomes problematic is:
This will run correctly.
This will fail because the offset of the second buffer is non-zero. But the failure happens when trying to map the first buffer!
Code in #242 can be used to reproduce this bug.
The text was updated successfully, but these errors were encountered: