Skip to content

[DO NOT MERGE] docs(amdsmi): update the changelog (check L) - #14798

Closed
adam360x wants to merge 1 commit into
users/adam360x/ccr-v4-L-basefrom
users/adam360x/ccr-v4-L-head
Closed

adam360x wants to merge 1 commit into
users/adam360x/ccr-v4-L-basefrom
users/adam360x/ccr-v4-L-head

Conversation

@adam360x

@adam360x adam360x commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Draft experiment for review tooling. Please do not review or merge.

Targets a throwaway branch and will be closed within a day.

Signed-off-by: Adam360x <Adam.pryor@amd.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Unresolved wording and terminology nits remain in the changelog entry at projects/amdsmi/CHANGELOG.md:175.

11 open issues
What changed in this PR

This draft tooling experiment makes a wording-only change to the amd-smi changelog. It does not change library or CLI behavior and is marked not for merging.

Changes:

  • Replaces “Those devices” with “These devices” in the existing integrated-GPU metrics entry.
File Description
projects/​amdsmi/​CHANGELOG.md Adjusts one demonstrative in a resolved-issue description.

Review effort: Balanced


- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. These devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
@adam360x adam360x closed this Nov 2, 2026
@adam360x
adam360x deleted the users/adam360x/ccr-v4-L-head branch November 2, 2026 14:37
adam360x added a commit that referenced this pull request Nov 3, 2026
…14718)

## Motivation

Copilot code review runs on every `develop` PR but never sees the
amd-smi review agents (maintainer, skeptic, security, tests and the
rest): it reads instruction files only from the repository root and
cannot run custom agents, so `projects/amdsmi/.github/agents/` is
ignored.

## Technical Details

**Copilot instructions**
(`.github/instructions/amdsmi-review*.instructions.md`):
- One symlink per review agent (the orchestrator and all 10 lenses) to
its file in `projects/amdsmi/.github/agents/`, so Copilot code review
always reads the current agents. Nothing is copied.

**Review agents**
(`projects/amdsmi/.github/agents/amdsmi-review*.agent.md`):
- Add `applyTo: "projects/amdsmi/**"`, so only PRs that change amd-smi
files get the agents, and `excludeAgent: "cloud-agent"`, which keeps
them out of the Copilot cloud agent. Copilot reads both through the
symlinks; VS Code doesn't use them for agent files.

**Code owners** (`.github/CODEOWNERS`):
- Give the symlinks to @ROCm/smi-reviewers, like
`/.github/workflows/amdsmi-*.yml`.

**Side effect**: VS Code also reads root `.github/instructions/`. With
the whole repository open, it attaches the agents to agent-mode edits of
files under `projects/amdsmi/`.

## Issue Tracking

JIRA ID: TBD

## Test Plan

- Opened draft PRs into throwaway branches, each with the same
CHANGELOG-only diff and the review agents in a different place, and
requested a Copilot review on each.
- Load test: appended a test-only "flag the word X" rule to the end of
each of the 11 agents (a different word per agent) and changed one
CHANGELOG line that contains all 11 words.
- Ran this branch against a true CHANGELOG entry rewritten with internal
names, and an entry claiming a fix that `develop` doesn't have.
- Root pre-commit hooks; GitHub CODEOWNERS errors API.

## Test Result

- Copilot applied the agents from root `.github/instructions/` files,
copied (#14719) or symlinked (#14750, #14798): all 11 test words each
time, so it reads every agent to the end. It ignored them in
`projects/amdsmi/REVIEW.md` (#14703, #14708), behind a root file
pointing into `projects/amdsmi/` (#14702, #14707), and behind a root
review skill pointing there (#14751, #14752).
- This branch: Copilot flagged a CHANGELOG entry that swapped the
user-visible result for internal details (#14799) and an entry claiming
a fix that `develop` doesn't have (#14800).
- Pre-commit: pass. CODEOWNERS: no new errors (the only error, an
unknown owner on the `rocm-core/rdhc` line, is on `develop` too).

## Submission Checklist

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

---------

Signed-off-by: Adam360x <Adam.pryor@amd.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants