Fix poision child process issue when call getAccelerator() #144541
Closed
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.
Stack from ghstack (oldest at bottom):
Motivation
fix #144152
Solution
at::globalContext()::hasXXX
to determine if accelerator XXX is built with PyTorch or an extension already registered to PyTorch.at::hasXXX
to determine if accelerator XXX is available at runtime.at::globalContext()::hasXXX
ingetAccelerator
rather thanat::hasXXX
to avoid initializing the XXX runtime (which can poison child processes) while detecting the current accelerator.cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @albanD