[adam360x]

Cherry-pick of d0357d2 (#13637) to release/therock-10.2.

Motivation

RDC_FI_POWER_USAGE reads 4294967295000000 µW, with a success status, on AMD Instinct MI300 series and newer GPUs, while amd-smi metric --power shows the real socket power. It was reported on MI300A with ROCm 10.1.0. The ROCm 10.2.0 pre-release behaves the same: release/therock-10.2 was cut on 2026-10-14, two days before the fix merged to develop.

RDC treats a socket power of 65535 as "not available", but AMD SMI has reported an unreadable power as UINT32_MAX since ROCm 7.11. These GPUs report no average socket power, so RDC scaled UINT32_MAX to microwatts.

Technical Details

• Library and test changes are identical to fix(rdc): report the socket power of MI300 series and later GPUs #13637 (RdcMetricFetcherImpl.cc, new tests/unit/test_power_usage.cc):
  • Per-field fetch: UINT32_MAX and UINT16_MAX both mean "not available" for the average and current socket power. GPUs without an average socket power report the current one; partitions without any socket power report N/A, and RDC logs an error on each fetch, as on develop.
  • Bulk fetch (RDC_BULK_FETCH_ENABLED, off by default): a GPU with neither reading falls through to the per-field fetch instead of reporting 65535 W.
• Conflicts resolved by keeping only this change's lines:
  • CHANGELOG.md: the entry goes first under Resolved Issues of the branch's top section, whose heading still names ROCm 10.1.0. docs(rdc): split the RDC 1.3.1 and 1.4.0 changelog sections #13874 splits that section into 10.2.0 and 10.1.0 entries on develop and needs its own cherry-pick.
  • tests/unit/CMakeLists.txt, tests/ci/test_gtest_runner.py: without the rdc_link_status_tests lines of fix(rdc): don't report XGMI links amdsmi did not return #13384, which is not on this branch.
• Not included: fix(rdc): report the partition count from the partition profile #13638 (RDC_FI_GPU_PARTITION_COUNT reports 65535 for the same reason).
• To reach ROCm 10.2.0, TheRock release/therock-10.2 also needs a rocm-systems submodule bump after this merges.

Issue Tracking

JIRA ID: ROCM-33968

Test Plan

• GPU-less rdc_power_usage_tests from this branch, and again with RdcMetricFetcherImpl.cc reverted to release/therock-10.2.
• pytest tests/ci/test_gtest_runner.py -k "power or client or help" against a private install of this branch.
• 4x MI300A (gfx942, SPX), non-root, the embedded-RDC Python script from the ticket, amd-smi as reference:
  • ROCm 10.1.0 and the ROCm 10.2.0 pre-release, as shipped;
  • this branch and release/therock-10.2, built locally against the pre-release's AMD SMI;
  • the 2026-11-05 nightly, which has fix(rdc): report the socket power of MI300 series and later GPUs #13637.
• This branch with GPU 0 under a compute load.
• rdcd -u and rdci dmon -u -e 300 in a private network namespace: the pre-release and this branch.
• RDC CI (rdc-ci.yml) does not run for pull requests to this branch; dispatched on the branch: https://github.com/ROCm/rocm-systems/actions/runs/42056116910.

Test Result

• Unit tests: 9 of 9 pass; with RdcMetricFetcherImpl.cc as on release/therock-10.2, 3 of 9 fail.
• pytest: the 3 selected tests pass.
• RDC CI: build and GPU-less tests pass on the third attempt (61 passed, test_rdc_power_usage among them; 20 skipped, no GPU). The first two attempts stopped before checkout on a Docker Hub pull rate limit (infrastructure).
• MI300A: ROCm 10.1.0, the 10.2.0 pre-release and the local release/therock-10.2 build report 4294967295000000 on all 4 GPUs. This branch and the nightly report 53-66 W at idle, the same as amd-smi (current socket power; average socket power N/A).
• Under load, GPU 0: 100-135 W from RDC and 91-136 W from amd-smi over the same 8 s.
• rdci dmon: the pre-release reports 4294967295000000, this branch 53000000-66000000 µW.
• Not re-run on hardware: TPX/CPX partition modes. The unit tests cover partitions without a socket power, and fix(rdc): report the socket power of MI300 series and later GPUs #13637 was run on MI300A in SPX, TPX and CPX.

Submission Checklist

• Look over the contributing guidelines at https://github.com/ROCm/rocm-systems/blob/develop/CONTRIBUTING.md.