This repository was archived by the owner on Jun 9, 2023. It is now read-only.
Add CPU kernel builders #25
Open
Conversation
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Currently, it is not possible to add NVTX tracing to ops that may be executed on CPU rather than GPU. In that case one would run into exceptions like
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot assign a device for operation .../NvtxStart: Could not satisfy explicit device specification '/device:CPU:0' because no supported kernel for CPU devices is available.This can be fixed in a straight-forward manner by registering CPU kernels for
NvtxStartandNvtxEnd. As far as I can tell, NVTX tracing should work fine for non-CUDA code, so this feels generally useful to me.