Skip to content

[SYCL][UR] Fix P2P Access Get Info Query #15152

New issue

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

Merged
merged 1 commit into from
Aug 21, 2024

Conversation

raiyanla
Copy link
Contributor

No description provided.

@raiyanla raiyanla requested a review from a team as a code owner August 21, 2024 14:20
@raiyanla raiyanla requested review from bso-intel and nrspruit August 21, 2024 14:20
@raiyanla raiyanla force-pushed the fix-can-access-peer-query branch from 69d4fdc to 7efff39 Compare August 21, 2024 14:40
@nrspruit
Copy link
Contributor

@intel/llvm-gatekeepers , please merge this change to address the P2P race conditions.

@againull againull merged commit ee97531 into intel:sycl Aug 21, 2024
12 checks passed
Comment on lines +253 to +254
Plugin->call(urUsmP2PPeerAccessGetInfoExp, Device, Peer, UrAttr, returnSize,
&value, nullptr);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@raiyanla , can underlying UR adapter return more than sizeof(int) bytes of data here? If so, we'll write beyond value's storage. If not, what was the issue before?

Copy link
Contributor Author

@raiyanla raiyanla Aug 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Underlying Adapter only returns sizeof(int) max. I think the issue was possibly more with querying for both the returnSize and value at same time. I saw it was returning garbage numbers each time until this PR. All the adapters use the same helper in the implementation for this, and I'm guessing it doesn't set value properly if returnSize is being queried for at the same time. I will need to confirm when I have access to an appropriate machine though.

AlexeySachkov pushed a commit to AlexeySachkov/llvm that referenced this pull request Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants