Skip to content

Conversation

@lslusarczyk
Copy link

Related-To: NEO-13856

Related-To: NEO-13856
Signed-off-by: Łukasz Ślusarczyk <lukasz.slusarczyk@intel.com>
Copy link
Contributor

@MichalMrozek MichalMrozek left a comment

Choose a reason for hiding this comment

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

how do you ensure on host synchronize calls that all submissions were properly processed in async thread?

@lslusarczyk
Copy link
Author

how do you ensure on host synchronize calls that all submissions were properly processed in async thread?

according to my research, completion events are created prior to submission to CommandListCoreFamilyImmediate (which API is worker thread boundary) so "wait" will wait for them (in zeEventSychronize)

if you ask about failures in submitKernel path that may happen inside worker thread, then now I call abort() :) however this should be possible to be handled in the same way as failure in executing kernel on GPU - let's talk about this on person on Monday

@lslusarczyk
Copy link
Author

BTW, let's keep discussion in PR in innersource

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.

2 participants