[SYCL] Eliminate XPTI overhead when it is disabled #18334
Merged
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.
Even if the XPTI collector is not used, we still have some overhead related to XPTI instrumentation when we call
xptiRegisterStream
function.With these changes, we cache the result of the
xptiTraceEnabled
function in the static variables. It is safe to cache it because XPTI collector is enabled by theXPTI_FRAMEWORK_DISPATCHER
environment variable before the process starts.VTune shows ~2% decrease in the number of instructions retired on a submit kernel path.