-
Notifications
You must be signed in to change notification settings - Fork 795
[SYCL][ESIMD][EMU] Queue/Event handling change for esimd_cpu #4201
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
kbobrovs
merged 11 commits into
intel:sycl
from
dongkyunahn-intel:esimdcpu_queue_event_handling
Sep 3, 2021
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
2d26bcf
[SYCL][ESIMD][EMU] Queue/Event handling change for esimd_cpu
dongkyunahn-intel c291db3
clang-format error fix
dongkyunahn-intel 05e656b
Merge branch 'sycl' into esimdcpu_queue_event_handling
dongkyunahn-intel 29d46df
Merge branch 'sycl' into esimdcpu_queue_event_handling
dongkyunahn-intel 349dc85
Merge branch 'sycl' of https://github.com/intel/llvm into esimdcpu_qu…
dongkyunahn-intel 1987a64
Reverting changes applied in queue_impl.cpp
dongkyunahn-intel e309c7f
Support only in-order queue for pi_esimd_cpu
dongkyunahn-intel 65d39cd
Update in event creation
dongkyunahn-intel 605bd5e
clang-format error fix
dongkyunahn-intel a26379a
Comment change per review comment
dongkyunahn-intel 16b3de6
Merge branch 'sycl' of https://github.com/intel/llvm into esimdcpu_qu…
dongkyunahn-intel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I understand your current implementation, with all commands being blocking, all events returned from enqueue operations are effectively in "completed" state once control is returned back to the caller of the enqueue operation.
The same applies to other places where events are created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@romanovvlad suggested this implementation from CUDA PI implementation from recent phone call. Also, he was fine with this 'DummyEvent' approach.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, now I see the point - unique_ptr is useful to automatically release the memory allocated by new _pi_even in case buf->CmBufferPtr->ReadSurface throws an exception. Disregard this my comment then.
DummyEvent
seems is redundant, as I explained above, even though harmless. So I don't mind leaving it as is for now.