add the ability to use an empty kernel for command buffer profiling #148
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.
The command buffer emulation layer currently implements event profiling by tracking event profiling on command-queue barriers before and after command-buffer content, but some implementations do not properly implement event profiling on barriers. As a workaround for these implementations, track event profiling on an empty kernel immediately after the command-queue barriers instead.
Because it is less efficient to use the empty kernel for event profiling (the current implementation requires a kernel compilation per command-buffer, in addition to the additional runtime cost associated with the empty kernel every time the command buffer is executed), this codepath is disabled by default, but may be enabled with an environment variable.