NVIDIA / NVIDIA/gpu-admin-tools
NVLink debug data with Ampere A100 and H100 PCIe?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 92
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Hi there!
This tool has been the closest thing I've gotten to having a method for discovering whether my hypervisors have NVLinks installed on my H100 PCIe GPUs. I use VFIO, no MIG, so no nvidia driver on the hypervisor.
I noticed that neither the H100 PCIe or the A100 actually supports the --nvlink-debug-dump flag:
- H100 PCIe (0x2331) is not added to the list of devices in
read_module_id_h100() - A100 doesn't have the
links_per_group,base_offsetorper_group_offsetpresent.
I'm not a hardware engineer and I don't know the specs for the registers of the A100, but I was able to get the H100 PCIe working* by simply adding 0x2331 to the lists in the above lines.
As for the A100 I've been able to get it to work intermittently but using the same offsets as the H100, but it's really hit and miss.
I'm hoping to get some insight on whether it'd be possible to get formal support for this? Thank you!
* No clue if it's accurate or not, but it's proven reliable enough for me to know whether NVLink bridges are installed on GPU pairs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in nvidia_gpu_tools.py at read_module_id_h100() around lines 4871-4881 and the A100-related offset definitions around lines 718-729. Verify the H100 PCIe device ID and determine the correct A100 links_per_group, base_offset, and per_group_offset values from the hardware specifications before changing support. Done means --nvlink-debug-dump reliably handles both GPU models.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100