feat(ascend): add DCMI telemetry backend - #503
Open
KaranocaVe wants to merge 3 commits into
Open
Conversation
- Search standard Ascend installation locations for libdcmi.so - Allow ASCEND_ROOT to override the installation root - Document the optional Ascend build configuration
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
libdcmi.soin standard Ascend locations, supportASCEND_ROOT, and document the optional build configurationFeature coverage
This is intended to make Ascend a near feature-complete NVTOP backend, rather than a basic detection path. Where the installed CANN driver exposes a metric, it covers the core real-time monitoring surface: device discovery and identity, device and process memory, NPU/AI Core/AI CPU utilization, HBM telemetry, frequencies, temperature, power, PCIe information, and device health/status.
The backend prefers the
dcmiv2logical-device API and falls back to legacy card/device DCMI APIs and symbols, so it can provide that coverage across CANN/Ascend generations. Capabilities absent from a particular driver remain unavailable without preventing monitoring of the rest. This gives Ascend feature coverage close to NVTOP's established vendor backends, subject to the telemetry exposed by the installed driver and hardware.Validation
git diff --check upstream/master...HEADcmake -S /workspace/nvtop -B /tmp/nvtop-ascend-build -DASCEND_SUPPORT=ON -DCMAKE_BUILD_TYPE=Releasecmake --build /tmp/nvtop-ascend-build --parallel 2