基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/ROCm/rocm-systems --skill amdsmi-output-verification命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | amdsmi-output-verification |
| description | A checklist for verifying whether AMD SMI is reporting GPU information correctly. |
Use this checklist whenever AMD SMI appears to report incorrect GPU information. The goal is to distinguish a real AMD SMI defect from a driver, firmware, environment, documentation, or expectation mismatch.
When running a test, include the following metadata to help with triage and debugging:
Capture raw output, without editing values.
amd-smi version
amd-smi list
amd-smi static
amd-smi metric
amd-smi monitor
rocminfo
rocm-smi
lspci -nn
lspci -vv
dmesg
Also capture relevant sysfs values:
find /sys/class/drm -maxdepth 4 -type f
For each tested GPU, inspect the matching card path under:
/sys/class/drm/card*/device
Useful files often include:
vendordevicesubsystem_vendorsubsystem_devicerevisionproduct_nameproduct_numberserial_numbermem_info_vram_totalmem_info_vram_usedgpu_busy_percentpp_dpm_sclkpp_dpm_mclkpp_power_profile_modeAvailability varies by GPU, driver, kernel, and permission level.
| Field | AMD SMI value | Baseline value | Baseline source | Result | Notes |
|---|---|---|---|---|---|
| GPU name | |||||
| ASIC name | |||||
| Vendor ID | |||||
| Device ID | |||||
| Subsystem ID | |||||
| Revision ID | |||||
| PCI BDF | |||||
| VRAM total | |||||
| Memory type | |||||
| VBIOS version | |||||
| Firmware versions | |||||
| Driver version | |||||
| ROCm version | |||||
| Temperature | |||||
| Power | |||||
| Clocks | |||||
| Utilization | |||||
| ECC/RAS support | |||||
| Process reporting |
Decode and triage HRR capture archives with full GPU replay by default (Linux). Builds hrr-playback when missing. On Windows: full native GPU replay via triage_archive.ps1 + ensure_playback.ps1 (PowerShell); Docker replay requires Linux or WSL2. Never edits source. Print finding summary in the chat reply.
Profiles a target application using rocprofv3 with program counter sampling enabled and then analyzes the results. Use when the user has a program that runs on an AMD GPU and asks to perform PC sampling, to determine the runtime performance characteristics of their application, to determine stall reasons, or to determine hotspots in the code.
Use when writing, planning, or improving unit tests for low-level transport or systems code — especially when reasoning about branch coverage, test gaps, identifying which uncovered paths are worth pursuing, or deciding when a feature's test suite is ready to merge.