AZP: Accept nvidia_peermem and drop legacy service check #10887
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.
What?
nvidia_peermem
alongsidenv_peer_mem
in GPU peer-memory checks inbuildlib/az-helpers.sh
.nv_peer_mem
systemd service.try_load_cuda_env()
verifying via/sys/kernel/mm/memory_peers/nv_mem/version
.Why?
nvidia_peermem
. This avoids false negatives and removes dependency on a legacy service while preserving backward compatibility.How?
check_nv_peer_mem()
: pass if eithernvidia_peermem
ornv_peer_mem
is loaded; drop service status check.try_load_cuda_env()
: unchanged behavior, still relies on the sysfs version file.