# Changelog for AMD SMI Library

Full documentation for amd_smi_lib is available at [https://rocm.docs.amd.com/projects/amdsmi](https://rocm.docs.amd.com/projects/amdsmi/en/latest/).

***All information listed below is for reference and subject to change.***

## amd_smi_lib for ROCm 10.0

### Added

- **Added accelerator partition memory allocation mode API**.  
  - New APIs: `amdsmi_get_gpu_accelerator_partition_mem_alloc_mode()`, `amdsmi_set_gpu_accelerator_partition_mem_alloc_mode()`.
  - New enum: `amdsmi_accelerator_partition_mem_alloc_mode_t` (`AMDSMI_ACCELERATOR_PARTITION_MEM_ALLOC_CAPPING`, `AMDSMI_ACCELERATOR_PARTITION_MEM_ALLOC_ALL`).
  - Supersedes the equivalent `compute_partition` memory allocation mode APIs, which are now deprecated.

### Changed

- **Bumped the library major version to 27.0.0** (breaking).  
  - The shared library SONAME is now `libamd_smi.so.27`. Consumers linked against `libamd_smi.so.26` must relink; no source changes are required beyond the API changes listed elsewhere in this release.

- **Widened five `amdsmi_gpu_metrics_t` accumulator counters from 32-bit to 64-bit** (breaking).  
  - `gfx_activity_acc`, `mem_activity_acc`, `pcie_nak_sent_count_acc`, `pcie_nak_rcvd_count_acc`, and `pcie_lc_perf_other_end_recovery` are now `uint64_t` to match the amdgpu pmfw metrics header. Recompile callers that read these fields; the struct layout and field offsets have changed.

- **Aligned the fabric telemetry and NIC firmware API surface with the unified ABI** (breaking).  
  - `amdsmi_fabric_telem_id_to_string()` now returns `amdsmi_status_t` and writes the name through a `const char**` out-parameter, instead of returning a `const char*` directly.
  - Renamed `amdsmi_nic_fw_t` to `amdsmi_nic_fw_entry_t`.
  - Added the `amdsmi_fabric_type_t` enumerator `AMDSMI_FABRIC_TYPE_UALINK`; the previous spelling `AMDSMI_FABRIC_TYPE_UALLINK` is retained as a deprecated alias with the same value and is slated for removal in a future ROCm release.

- **Flattened the `amdsmi_fabric_info_t` structure and removed `amdsmi_fabric_info_ver_t`**.  
  - The intermediate `amdsmi_fabric_info_ver_t` type was removed from the public header. Its payload union is now the `fabric_info` member of `amdsmi_fabric_info_t`, and its version field is exposed directly as the top-level `fabric_version` field.
  - Field access simplifies from `fabric_info.fabric_version.v1.<field>` to `fabric_info.v1.<field>`, and `fabric_info.version` becomes `fabric_version`.
  - The change is ABI-preserving: field offsets and the overall structure size are unchanged. The Python `amdsmi_get_gpu_fabric_info()` dictionary keys are also unchanged.

- **Prefixed public preprocessor macros with `AMDSMI_` in `amdsmi.h`** (breaking).  
  - `MAX_SVI3_RAIL_INDEX`, `MAX_SVI3_RAIL_SELECTION`, `POWER_EFFICIENCY_MODE_4`, `POWER_EFFICIENCY_MODE_5`, and `MAX_NUMBER_OF_AFIDS_PER_RECORD` are now `AMDSMI_MAX_SVI3_RAIL_INDEX`, `AMDSMI_MAX_SVI3_RAIL_SELECTION`, `AMDSMI_POWER_EFFICIENCY_MODE_4`, `AMDSMI_POWER_EFFICIENCY_MODE_5`, and `AMDSMI_MAX_NUMBER_OF_AFIDS_PER_RECORD`. The unused `CENTRIGRADE_TO_MILLI_CENTIGRADE` macro was removed. Update references to the new names.

- **Deprecated the `compute_partition` APIs in favor of `accelerator_partition` equivalents**.  
  - `amdsmi_get_gpu_compute_partition()`, `amdsmi_set_gpu_compute_partition()`, `amdsmi_get_gpu_compute_partition_mem_alloc_mode()`, and `amdsmi_set_gpu_compute_partition_mem_alloc_mode()` are slated for removal in a future ROCm release. They now emit a `DeprecationWarning` from the Python interface and delegate to their `accelerator_partition` counterparts.
  - The `amdsmi_compute_partition_type_t` and `amdsmi_compute_partition_mem_alloc_mode_t` enums are deprecated in favor of `amdsmi_accelerator_partition_type_t` and `amdsmi_accelerator_partition_mem_alloc_mode_t`.

- **Deprecated `amdsmi_set_gpu_memory_partition()` in favor of `amdsmi_set_gpu_memory_partition_mode()`**.  
  - `amdsmi_set_gpu_memory_partition` is slated for removal in a future ROCm release. It now emits a `DeprecationWarning` from the Python interface and functions as a wrapper of `amdsmi_set_gpu_memory_partition_mode()`.

- **Namespaced `amdsmi_clk_limit_type_t` and `amdsmi_io_bw_encoding_t` enumerators with an `AMDSMI_` prefix**.  
  - Added `AMDSMI_CLK_LIMIT_MIN`/`AMDSMI_CLK_LIMIT_MAX` and `AMDSMI_AGG_BW0`/`AMDSMI_RD_BW0`/`AMDSMI_WR_BW0`.
  - The unprefixed names (`CLK_LIMIT_MIN`, `CLK_LIMIT_MAX`, `AGG_BW0`, `RD_BW0`, `WR_BW0`) are retained as deprecated aliases with unchanged values and are slated for removal in a future ROCm release.

- **Removed the `amdsmi_gpu_driver_reload()` API and its Python binding** (breaking).  
  - Reload the amdgpu driver out of band with `sudo modprobe -r amdgpu && sudo modprobe amdgpu` to apply memory partition changes instead.

- **Removed unused public macros to match the unified ABI** (breaking).  
  - Dropped the `AMDSMI_MAX_VF_COUNT`, `AMDSMI_MAX_DRIVER_NUM`, `AMDSMI_DFC_FW_NUMBER_OF_ENTRIES`, `AMDSMI_MAX_WHITE_LIST_ELEMENTS`, `AMDSMI_MAX_BLACK_LIST_ELEMENTS`, `AMDSMI_MAX_TA_WHITE_LIST_ELEMENTS`, `AMDSMI_MAX_ERR_RECORDS`, `AMDSMI_MAX_PROFILE_COUNT`, and `AMDSMI_PF_INDEX` defines, which were unreferenced by any API or struct.

- **Deduplicated the `amdsmi_fabric_telemetry_category_t` enumerators**.  
  - `AMDSMI_FABRIC_TELEMETRY_CATEGORY_INVALID` is now the canonical `0xFFFFFFFF` value; the previous `AMDSMI_FABRIC_TELEMETRY_CATEGORY_UNKNOWN` name (same value) is retained as a deprecated alias and is slated for removal in a future ROCm release.

- **Deprecated `amdsmi_get_gpu_vram_vendor()`**. Use `amdsmi_get_gpu_vram_info()` and read the `vram_vendor` field instead. The function is retained (it now delegates to `amdsmi_get_gpu_vram_info()`, and the Python binding emits a `DeprecationWarning`) and is slated for removal in a future ROCm release.

- **Removed `amdsmi_get_cpusocket_handles()` from the Python interface** (breaking). Use `amdsmi_get_cpu_handles()` instead.

- **Removed the `plpds` key from `amdsmi_get_xgmi_plpd()` Python output** (breaking). Use the `policies` key instead.

- **Removed `amdsmi_set_gpu_clk_range()`** (breaking). Use `amdsmi_set_gpu_clk_limit()` instead.

- **Restructured AMD SMI C++ tests into unit and functional suites**.  
  - The `amdsmitst` source tree now separates unit tests from hardware-backed functional tests under `tests/amd_smi_test/unit/` and `tests/amd_smi_test/functional/`.
  - GTest suite names now follow a `<Component><Type>[<Operation>]` scheme: functional tests are `<Component>FunctionalReadOnly`/`<Component>FunctionalReadWrite` (e.g. `GpuFunctionalReadOnly`) and unit tests are `<Component>Unit` (e.g. `GpuUnit`). This replaces the old `amdsmitstReadOnly`/`amdsmitstReadWrite` and `AmdSmiDynamicMetricTest` names.
  - Consumers that pass explicit `--gtest_filter` values should update those filters to the new suite names.
  - See the [AMD SMI test design](docs/conceptual/test-design.md#naming-conventions) for the suite naming convention and `--gtest_filter` usage.

### Fixed

- **Fixed `amd-smi ras --cper --json` emitting nothing when there are no CPER entries**.
  - The common no-entries case printed empty output, so consumers feeding stdout to `json.loads` failed with `Expecting value: line 1 column 1 (char 0)`. The command now always emits exactly one valid JSON document: `[]` when there are no entries, or a single aggregated array across all GPUs when there are. `--follow` mode stays silent until entries appear. The human-readable primary-partition warning is also suppressed in JSON mode so it no longer corrupts the output.

### Optimized

- **Optimized `amdsmi_get_gpu_process_list()` to skip redundant KFD topology discovery**.  
  - The per-process KFD lookup rebuilt the entire KFD node topology (an expensive sysfs walk) on every call just to translate the device BDF into its KFD GPU id.
  - The caller already knows this value, so it is now passed through to `gpuvsmi_get_pid_info()`, eliminating one full topology discovery per process per refresh. Falls back to the original discovery path when the id is unavailable.

### Resolved Issues

- **Fixed `amd-smi set --ptl-status` silently failing to change PTL state**.  
  - The set path wrote `"1"`/`"0"` to the `ptl/ptl_enable` sysfs node, which only accepts `"enabled"`/`"disabled"`; the driver ignored the numeric write while the API still reported success. The state now changes as expected, and a rejected write returns a real error instead of a generic success.

- **Fixed `amd-smi process` hiding compute processes owned by other users**.  
  - A caller without permission to read another process's `/proc/<pid>/fd` was misdetected as running in a separate PID namespace, which caused the whole compute-process list to come back empty. Such processes are now listed with a redacted (`N/A`) name instead of being dropped.

- **Fixed CU%/SDMA column alignment in the `amd-smi` process table**.  
  - The `SDMA` header no longer sits a column left of its values, and valid `CU %`/`SDMA` values are no longer truncated.

- **Fixed compute processes being reported on every GPU**.  
  - A process was attributed to a GPU whenever it had a KFD context on that GPU, so a job with queues on a single GPU appeared under every GPU. Attribution now uses the process's active KFD queues plus any GPU where it holds a non-zero VRAM allocation, so a process is listed only against the GPUs it actually uses.

- **Fixed `amd-smi` hanging in `amdsmi_init()` on UALink systems when the IFoE driver is unresponsive**.  
  - `amdsmi_init()` (and every CLI command) opened a per-GPU IFoE/UALoE fabric session up front, so it blocked indefinitely when the Broadcom IFoE driver was unresponsive, even for queries that never use fabric data.
  - The fabric session is now opened only on the first fabric query, so initialization and non-fabric queries no longer touch the IFoE driver.

- **Fixed ctypes `DeprecationWarning` from `amdsmi_wrapper.py` on Python 3.14**.  
  - Python 3.14 deprecates the implicit ctypes structure layout when `_pack_` is set (slated to become an error in 3.19). Each packed structure/union in the generated wrapper now sets `_layout_ = 'ms'`, preserving the existing MSVC-compatible layout (no ABI change) while silencing the warning.

## amd_smi_lib for ROCm 7.14.0

### Added

- **Added NIC processor discovery and information API surface**.  
  - New C APIs: `amdsmi_get_nic_processor_handles()`, `amdsmi_get_nic_device_bdf()`, `amdsmi_get_nic_fw_info()`, `amdsmi_get_nic_port_statistics()`, and `amdsmi_get_nic_vendor_statistics()`.
  - `amdsmi_get_nic_processor_handles()` enumerates NIC processors by socket; the BDF, firmware, and port/vendor statistics getters are reserved and currently return `AMDSMI_STATUS_NOT_YET_IMPLEMENTED`.

- **Exposed APU metrics through the CLI and Python interface**.  
  - `amd-smi metric` now surfaces APU-specific data under `--usage`, `--power`, `--clock`, `--temperature`, `--fan`, `--voltage`, and `--throttle` when APU metrics are available.
  - `amd-smi monitor` provides APU temperature and clock fallbacks when standard dGPU sensors report N/A.
  - On APU systems the `--pcie`, `--ecc-blocks`, `--voltage-curve`, `--overdrive`, `--xgmi-err`, and `--energy` sections are not applicable and are omitted.

- **Added `--partition` flag to `amd-smi metric` for partition-scoped metrics**.  
  - The `-X`/`--partition` flag switches the temperature, clock, and usage categories to partition-level data sources; throttle metrics are already partition-aware.
  - Reuses the existing temperature/clock/usage section schema and adds partition-only AID/XCP/MID entries within it; socket-only fields with no partition equivalent report `N/A`.
  - When `--partition` is set with `--temperature`: adds MID and per-XCP/XCD temperatures.
  - When `--partition` is set with `--clock`: sources GFX/VCLK/DCLK/SOCCLK from partition metrics and adds per-AID and per-XCP clock entries with their limits.
  - When `--partition` is set with `--usage`: reports per-XCP GFX/JPEG/VCN activity.

- **Added `--folder` support to `amd-smi ras --afid`**.  
  - `amd-smi ras --afid --folder <DIR>` decodes every `*.cper` in a directory and prints a `file_name | list of afids` table (or a JSON array under `--json`).
  - Records with no AFIDs show `-`; files that cannot be parsed show `decode failed`.

- **Added IFoE/UALoE fabric telemetry and topology support**.  
  - New `amd-smi fabric` CLI subcommand with `--topology`/`-t` and `--info`/`-i` flags for querying fabric (UALoE) information.
  - New C APIs: `amdsmi_alloc_fabric_telemetry()`, `amdsmi_get_fabric_telemetry_data()`, `amdsmi_free_fabric_telemetry()`, `amdsmi_fabric_telem_id_to_string()`, and `amdsmi_get_gpu_fabric_info()`.
  - New Python APIs: `amdsmi_get_fabric_telemetry_data()` and `amdsmi_get_gpu_fabric_info()`.
  - Fabric telemetry category masks and size constants converted from preprocessor `#define`s to enums so they are exposed through the Python wrapper.

- **Wrapped ESMI functions in `amdsmi_go_shim`**.  
  - Go callers can now access ESMI CPU functionality through the existing `amdsmi_go_shim` interface.

- **Added GPU partitioning conceptual guide and usage examples**.  
  - New guide at `docs/conceptual/partition.md` covering accelerator partition modes (SPX/DPX/TPX/QPX/CPX), memory partition modes (NPS1/NPS2/NPS4/NPS8), API generations, device enumeration after partition, and BDF encoding.
  - New C++ example: `example/amd_smi_partition_example.cc`.
  - New Python example: `example/amd_smi_partition_example.py`.

- **Improved Python test runner behavior**.  
  - Added `-l`/`--list` flag to list all available tests and exit without running them.
  - Added shadow detection: if `amdsmi` loads from a path other than the resolved expected path (`AMDSMI_PATH`, `ROCM_HOME`, `ROCM_PATH`, or `/opt/rocm` default), tests exit early with a clear error message and remediation steps.
  - Non-root invocations now exit with code 1 immediately with a clear message instead of failing mid-test.

- **Added new alias for `amd-smi set -C/--compute-partition` as `amd-smi set --accelerator-partition`**.  
  - Compute and accelerator partitions are fundamentally the same, so users can now use `--accelerator-partition` to set the compute/accelerator partition.

- **Added input validation for CPU `set` commands**.  
  - Out-of-range values are now rejected with a clear error showing the valid range:
    - `--cpu-xgmi-link-width` (0-1)
    - `--cpu-gmi3-link-width` (0-2)
    - `--cpu-lclk-dpm-level` (0-3)
    - `--cpu-disable-apb` (0-3)
  - `--cpu-pwr-limit` values above the socket maximum are now reduced to the maximum and applied, with a warning.

- **Added compute partition memory allocation mode API**.  
  - New `amd-smi static --partition` output includes `COMPUTE_PARTITION_MEM_ALLOC_MODE` field.
  - New `amd-smi set --compute-partition-mem-alloc-mode [CAPPING|ALL]` to control memory allocation mode (requires sudo).
  - New APIs: `amdsmi_get_gpu_compute_partition_mem_alloc_mode()`, `amdsmi_set_gpu_compute_partition_mem_alloc_mode()`.
  - New enum: `amdsmi_compute_partition_mem_alloc_mode_t` (`AMDSMI_COMPUTE_PARTITION_MEM_ALLOC_CAPPING`, `AMDSMI_COMPUTE_PARTITION_MEM_ALLOC_ALL`).
  - Reads/writes sysfs: `/sys/class/drm/cardN/device/compute_partition_mem_alloc_mode`.

- **Added `AMDSMI_LINK_TYPE_NUMA` and `AMDSMI_LINK_TYPE_XNUMA` to `amdsmi_link_type_t`**.  
  - Represent NIC-to-GPU links that cross different PCIe switches on the same CPU (NUMA) or across CPUs (XNUMA).

- **Added PID-grouped process listing across GPUs**.  
  - `amd-smi process --sort-by-pid` and `amd-smi monitor --sort-by-pid` group output by PID, merging each PID's per-GPU usage into one row.
  - New C and Python API `amdsmi_get_gpu_process_list_by_pid()`.

- **Added `amdsmi_get_vcn_busy_percent` API**.  
  - Navi devices were incorrectly displaying N/A for vcn_busy in their metrics output due to a difference in design. This API was added to allow users to properly obtain the vcn_busy metric from Navi and other similar devices.

### Changed

- **Normalized JSON/CSV key casing in `amd-smi metric` clock and temperature sections**.  
  - The `uclk_aid`, `socclks_mid`, and temperature `xcd` keys are now lowercase (`aid_<N>`, `mid_<N>`, `xcp_<N>`) in JSON and CSV output, matching the existing `xcp_<N>` usage keys; they were previously uppercase (`AID_<N>`, `MID_<N>`, `XCP_<N>`).
  - Human-readable output is unchanged, since it uppercases all keys.

- **Normalized JSON/CSV key casing in the `amd-smi topology` NIC-GPU access table**.  
  - The per-GPU columns are now lowercase (`gpu_<N>` for the BDF header row, `gpu_<N>_topo` for each NIC's status row) in JSON and CSV output, matching the existing `gpu_<N>` keys in the GPU-to-GPU access matrix; they were previously uppercase (`GPU<N>`, `GPU<N>_Topo`).
  - Human-readable output is unchanged, since it uppercases all keys.

- **Fixed `amd-smi static --clock` CSV and human-readable formatting to output frequency levels as strings instead of dictionary objects**.  

- **Deprecated `amdsmi_get_gpu_vram_vendor()` in favor of `amdsmi_get_gpu_vram_info()`**.  
  - `amdsmi_get_gpu_vram_vendor` is slated for removal in a future ROCm release. It now emits a `DeprecationWarning` from the Python interface and functions as a wrapper of `amdsmi_get_gpu_vram_info()`.

- **Renamed "AINIC version" to "ionic version" in `amd-smi version` output**.  
  - The label now correctly reflects that it shows the ionic kernel driver version.

### Removed

- **Removed the non-functional `--decode` flag from `amd-smi ras`**. Out-of-band CPER decoding is available via `amd-smi ras --afid --cper-file <path>` or `--afid --folder <DIR>`.

- **Removed the unused `amdsmi_nic_link_type_t` enum from the public header**. No API or struct referenced it; NIC link types are reported through `amdsmi_link_type_t`, which gains `AMDSMI_LINK_TYPE_NUMA` and `AMDSMI_LINK_TYPE_XNUMA` in this release.

### Resolved Issues

- **Fixed `amd-smi set --power-cap` rejecting the minimum allowed value**.  
  - The lower bound is now inclusive, so setting the power cap to the exact minimum of the reported range (e.g. `210` when the range is 210-300W) succeeds instead of failing validation, matching the inclusive range shown in the error message.

- **Corrected invalid AMD SMI status-code names in exception messages and documentation**.  
  - Some `AmdSmiLibraryException` messages and API documentation entries were misspelled; they now use the correct `AMDSMI_STATUS_*` names.

- **Fixed a crash in `amdsmi_get_gpu_vram_vendor()` and made `amdsmi_get_gpu_vram_info()` resilient to DRM failures**.  
  - `amdsmi_get_gpu_vram_vendor()` now validates the output buffer and only writes it on success, fixing a null-pointer dereference on the not-supported path.
  - `amdsmi_get_gpu_vram_info()` now reads the VRAM vendor from sysfs first and treats the DRM ioctl (VRAM type/bit width/bandwidth) as best effort, so the vendor is still returned when the DRM path is unavailable.

- **Fixed AMD GPU manufacturer name display in `amd-smi static --board`**.  
  - The CLI now displays the canonical vendor name `Advanced Micro Devices, Inc. [AMD/ATI]` when the board manufacturer name is reported as the raw AMD PCI vendor ID (`0x1002`) because the host `pci.ids` lookup is unavailable. The C and Python APIs continue to return the raw value unchanged.
  - Standardized the hardcoded AMD vendor string on the canonical `pci.ids` spelling (with the comma) so `VENDOR_NAME` and `MANUFACTURER_NAME` are consistent with `lspci`.

- **Fixed `amd-smi ras --cper` / `amdsmi_get_gpu_cper_entries()` crash (`free(): invalid pointer` / `SIGABRT`)** when `libamd_smi.so` is `LD_PRELOAD`-ed under a host with a different libstdc++ (for example, device-metrics-exporter / `gpuagent`).

- **Fixed `amd-smi ras --cper` failing with `AMDSMI_STATUS_FILE_ERROR` on an empty CPER ring**. An empty ring (no RAS records) now reports no CPER records; `amdsmi_get_gpu_cper_entries()` returns `AMDSMI_STATUS_SUCCESS` with `entry_count == 0`.

- **Fixed `amdsmi_init()` aborting entirely when CPU/ESMI initialization fails**.  
  - `populate_amd_cpus()` treated an `esmi_init()` failure (non-AMD CPU, missing/unsupported energy or HSMP driver, or a CPU/SMU in a bad state) as fatal, causing all of `amdsmi_init()` to fail so GPU and NIC functionality became unusable. ESMI/CPU discovery is now non-fatal and is skipped on failure, mirroring the NIC discovery paths.
  - Removed an incorrect `static_cast<amdsmi_status_t>(esmi_init())` that conflated the unrelated `esmi_status_t` and `amdsmi_status_t` enums.
  - Added checks for the previously ignored return values of `get_nr_cpu_sockets()`, `get_nr_cpu_cores()`, and `get_nr_threads_per_core()`, plus a guard against a divide-by-zero when a misbehaving driver reports zero sockets or threads.

- **Fixed `amd-smi static` hanging indefinitely on gfx1153 and gfx950**.  
  - Added a 60-second timeout to `amdsmi_init()` in the CLI so the process exits with a clear error message instead of hanging when the GPU driver is unresponsive.
  - Added `O_NONBLOCK` to DRM device open during initialization so `open()` returns immediately if the device is wedged.

- **Fixed `amd-smi ras --afid --cper-file <file>` not showing AFIDs for correctable errors**.  
  - `aca_decode_corrected_error` was receiving the count of `uint32_t` elements where `decode_afid` expected the count of `uint64_t` elements, causing `decode_error_info` to return `NULL` for all non-standard section types.

- **Fixed `amd-smi ras --cper --json` producing invalid JSON**.  
  - Multi-GPU runs emitted a separate JSON array per GPU instead of a single unified array, and `--follow` mode printed an empty `[]` every iteration when no new entries existed. Both are now consolidated into a single JSON document.

- **Exposed `amdsmi_get_afids_from_cper` in the Python package**.  
  - The CPER AFID API was implemented but missing from `py-interface/__init__.py`, making it unavailable to Python callers using `from amdsmi import ...`.

- **Python unittest scripts now append a GTest-style summary after test output**.  
  - All `*_test.py` and `unit_tests.py` scripts print a colored `[PASSED]`/`[SKIPPED]`/`[FAILED]` block after the standard unittest output. Colors are automatically suppressed when output is not a TTY (e.g. file redirection, CI log capture).

- **Corrected the documented unit of `amdsmi_frequencies_t::frequency`**.  
  - The struct comment claimed frequencies were in MHz, but `amdsmi_get_clk_freq()` returns them in Hz. The comment now reads "List of frequencies in Hz".
  - Also removed the incorrect "in MHz" note from the `current` field, which is a frequency index, not a frequency value.
  - Updated the Python API reference to state the unit is Hz.

- **Fixed fabric telemetry APIs returning the wrong status on non-IFoE systems**.  
  - `amdsmi_alloc_fabric_telemetry()`, `amdsmi_get_fabric_telemetry_data()`, and `amdsmi_free_fabric_telemetry()` now return `AMDSMI_STATUS_NOT_SUPPORTED` on systems without fabric hardware, consistent with `amdsmi_get_gpu_fabric_info()`.

- **Fixed incorrect N/A output for vcn_busy field in `amd-smi metric --usage`**.  
  - On devices without XCP partitions (e.g. Navi), the CLI now reads `vcn_busy_percent` via the new `amdsmi_get_vcn_busy_percent()` sysfs API.

## amd_smi_lib for ROCm 7.13.0

### Added

- **Added APU metrics support (table versions 2.4 and 3.0)**.  
  - New `amdsmi_apu_metrics_t` struct accessible via `amdsmi_gpu_metrics_t.apu_metrics` pointer (non-null when APU-specific metrics are available).
  - **v2.4 metrics**:
    - `temperature_gfx`, `temperature_soc`, `temperature_core[8]`, `temperature_l3[2]`
    - `average_gfx_activity`, `average_mm_activity`
    - `average_socket_power`, `average_cpu_power`, `average_soc_power`, `average_gfx_power`, `average_core_power[8]`
    - Average clocks: `gfxclk`, `socclk`, `uclk`, `fclk`, `vclk`, `dclk`
    - Current clocks: `gfxclk`, `socclk`, `uclk`, `fclk`, `vclk`, `dclk`, `coreclk[8]`, `l3clk[2]`
    - `average_temperature_gfx`, `average_temperature_soc`, `average_temperature_core[8]`, `average_temperature_l3[2]`
    - `average_cpu_voltage`, `average_soc_voltage`, `average_gfx_voltage`, `average_cpu_current`, `average_soc_current`, `average_gfx_current`
    - `throttle_status`, `indep_throttle_status`
    - `fan_pwm`
  - **v3.0 metrics**:
    - `temperature_core[16]`, `temperature_skin`
    - `average_vcn_activity`, `average_ipu_activity[8]`, `average_core_c0_activity[16]`
    - `average_dram_reads`, `average_dram_writes`, `average_ipu_reads`, `average_ipu_writes`
    - `average_apu_power`, `average_dgpu_power`, `average_all_core_power`, `average_ipu_power`, `average_sys_power`
    - `stapm_power_limit`, `current_stapm_power_limit`
    - `average_core_power[16]`, `current_coreclk[16]`
    - `current_core_maxfreq`, `current_gfx_maxfreq`
    - `average_vpeclk_frequency`, `average_ipuclk_frequency`, `average_mpipu_frequency`
    - `throttle_residency_prochot`, `throttle_residency_spl`, `throttle_residency_fppt`, `throttle_residency_sppt`, `throttle_residency_thm_core`, `throttle_residency_thm_gfx`, `throttle_residency_thm_soc`
    - `time_filter_alphavalue`
  - Fields not applicable to the current version are set to sentinel values: `0xFFFF` for `uint16_t`, `0xFFFFFFFF` for `uint32_t`, and `UINT64_MAX` for `uint64_t` fields.
  - Python bindings updated with `AmdSmiApuMetrics` ctypes structure.

- **Added `oam_id` to `amdsmi_enumeration_info_t`**.  
  - `amd-smi list -e` now displays `OAM_ID` (Physical XGMI ID / OAM ID).
  - Added `--enumeration` as a long-form alias for `-e` in `amd-smi list`.

- **Added support for GPU metrics v1.9 new fields**.  
  - Added new temperature fields to `amdsmi_gpu_metrics_t`:
    - `temperature_hbm_stacks` — per-stack HBM temperatures (°C)
    - `temperature_mid` — per-MID temperatures (°C)
    - `temperature_aid` — per-AID temperatures (°C)
    - `temperature_xcd` — per-XCC compute die temperatures (°C)
  - Added new per-die clock fields to `amdsmi_gpu_metrics_t`:
    - `current_uclk_aid` — per-AID uclk (MHz)
    - `current_socclks_mid` — per-MID SOC clock (MHz)
  - Added new constants:
    - `AMDSMI_MAX_NUM_HBM_STACKS` (12)
    - `AMDSMI_MAX_NUM_AID` (2)
    - `AMDSMI_MAX_NUM_MID` (2)
    - `AMDSMI_MAX_NUM_CLKS_PER_AID` (2)
    - `AMDSMI_MAX_NUM_CLKS_PER_MID` (2)

- **Added VRAM and GTT tuning interface**.  
  - New `amd-smi static --mem-carveout` to view VRAM carveout options.
  - New `amd-smi set --mem-carveout` to change the VRAM carveout (APU).
  - New `amd-smi set --gtt` and `amd-smi reset --gtt` for system-wide GTT size tuning.
  - New APIs: `amdsmi_get_gpu_uma_carveout_info()`, `amdsmi_set_gpu_uma_carveout()`, `amdsmi_get_ttm_info()`, `amdsmi_set_ttm_pages_limit()`, `amdsmi_reset_ttm_pages_limit()`.
  - **TTM module auto-detection**: probes `amdttm` (DKMS), `amd_ttm`, and the in-tree
    `ttm` module in order so the correct `pages_limit` parameter is read/written
    on every supported configuration. Overridable via the `AMDSMI_TTM_SYSFS_NAME`
    environment variable. Note: third-party tools that hard-code
    `/sys/module/ttm/parameters/pages_limit` may report `0` on DKMS hosts
    because the active module is `amdttm`, not `ttm`; `amd-smi` reads the
    active one.
  - **Initramfs rebuild**: `set --gtt` / `reset --gtt` now invoke the
    distro's initramfs builder so the new `modprobe.d` snippet is picked up
    at next boot. Supported tools (first available wins): `dracut -f`
    (RHEL/Fedora/openSUSE), `update-initramfs -u` (Debian/Ubuntu), and
    `mkinitcpio -P` (Arch). If none is found, a clear message is printed
    describing the manual command to run.
  - **Reboot semantics**: these settings take effect only after the next
    reboot. `amd-smi node --gtt` shows the currently active value and, when
    a pending value has been written, an additional `PENDING (after reboot)`
    line so the previous-boot value is not mistaken for the new one.

- **Added UBB power and power_limit fields to `amdsmi_power_info_t` and `amdsmi_npm_info_t`**.  
  - `amd-smi metric --power` now displays `ubb_power` when available.
  - `amd-smi node -p` now displays UBB power threshold when available.

- **Added CPU support for family 1A Models 50h-57h**.  
  - New APIs: `amdsmi_get_cpu_xgmi_pstate_range()`, `amdsmi_get_cpu_core_ccd_power()`, `amdsmi_get_cpu_tdelta()`, `amdsmi_get_cpu_dimm_sb_reg()`, `amdsmi_get_cpu_svi3_vr_controller_temp()`, `amdsmi_get_cpu_pc6_enable()`, `amdsmi_get_cpu_cc6_enable()`, `amdsmi_get_cpu_sdps_limit()`, `amdsmi_get_cpu_core_floor_freq_limit()`, `amdsmi_get_cpu_core_eff_floor_freq_limit()`, and corresponding set APIs.
  - **Note**: `amdsmi_get_dfc_ctrl()` renamed to `amdsmi_get_cpu_dfc_ctrl()` and `amdsmi_set_dfc_ctrl()` renamed to `amdsmi_set_cpu_dfc_ctrl()` for naming consistency.

- **Updated memory API documentation**  
    Added note that the sum of per-process memory usage is not expected to equal total usage.

### Changed

- **Renamed `processor_type_t` enum typedef to `amdsmi_processor_type_t`**.  
  - The unprefixed typedef name did not follow the `amdsmi_*_t` convention used throughout `amdsmi.h` and was easy to collide with identifiers defined by other system-management libraries. New code should use `amdsmi_processor_type_t`. The old name is preserved as a backward-compatibility typedef alias, so existing callers continue to compile unchanged.

- **Package install no longer modifies the system-wide logrotate timer or cron schedule**.  
  - Previously, installing `amd-smi-lib` overwrote `/lib/systemd/system/logrotate.timer` (or moved `/etc/cron.daily/logrotate` to `/etc/cron.hourly/`) to force hourly rotation, which affected every other package using logrotate.
  - The package now only ships `/etc/logrotate.d/amd_smi.conf`, which sets its own `hourly` + `size 1M` cadence. AMD-SMI logs still rotate at the same frequency; system-wide settings stay as the distribution configured them.

- **Renamed `lc_perf_other_end_recovery` to `lc_perf_other_end_recovery_count` in `amd-smi metric` CLI output for unification**.  

- **Removed references to deprecated `amd-smi reset -r`**.  
  - CLI help text and memory partition change warnings no longer reference `amd-smi reset -r` for driver reloading.
  - Users are now directed to use `sudo modprobe -r amdgpu && sudo modprobe amdgpu` to reload the driver after partition changes.

- **Changed CPU power APIs to return values in milliwatts (mW) for higher precision**.  
  - Removed lossy integer rounding (`(mW + 500) / 1000`) from 6 CPU power get APIs. Values are now
    returned in milliwatts directly from the ESMI library, preserving sub-watt precision.
  - **C API**: Output parameter type remains `uint32_t*`, but the unit changed from watts to milliwatts (mW).
    - `amdsmi_get_cpu_socket_power`
    - `amdsmi_get_cpu_socket_power_cap`
    - `amdsmi_get_cpu_socket_power_cap_max`
    - `amdsmi_get_cpu_pwr_efficiency_mode` (ppt_limit field)
    - `amdsmi_get_cpu_core_ccd_power`
    - `amdsmi_get_cpu_sdps_limit`
  - **Python API (breaking)**: These functions now return `int` (milliwatts) instead of `str` (e.g., `"240 Watts"`).
    Callers that parsed the string output must update to handle the numeric return value.
  - **CLI output**: Power values now display with milliwatt precision (e.g., `240.500 Watts`).
  - Added missing null-pointer validation for output parameters in `amdsmi_get_cpu_socket_power_cap`
    and `amdsmi_get_cpu_socket_power_cap_max`.
  - Updated header documentation to specify milliwatt units for all affected get and set API parameters.

- **Changed power APIs to have consistent output parameter types**.  
  - Modified 6 cpu power API's to have consistent output power types. All set and get API's have uint32_t output values.
  - Modified get and set API's that had double output types to have uint32_t output types in milliwatts (mW).
    - amdsmi_get_cpu_socket_power(amdsmi_processor_handle processor_handle, uint32_t* ppower);
    - amdsmi_get_cpu_socket_power_cap(amdsmi_processor_handle processor_handle, uint32_t* pcap);
    - amdsmi_get_cpu_socket_power_cap_max(amdsmi_processor_handle processor_handle, uint32_t* pmax);
    - amdsmi_get_cpu_pwr_efficiency_mode(amdsmi_processor_handle processor_handle,
                                         uint32_t* power_efficiency_mode,
                                         uint32_t* utilization, uint32_t* ppt_limit);
    - amdsmi_get_cpu_core_ccd_power(amdsmi_processor_handle processor_handle, uint32_t* power);
    - amdsmi_get_cpu_sdps_limit(amdsmi_processor_handle processor_handle, uint32_t* sdps_limit);

### Optimized

- **Optimized `rsmi_dev_device_identifiers_get()` in the ROCm-SMI device layer**.  
  - Removed unnecessary iteration by directly indexing the device list.
  - Added bounds checking for `device_id`, with clearer error handling/logging.
  - Improves performance for device identifier queries.

### Resolved Issues

- **Fixed `amd-smi metric` crashing with `TypeError` on MI300A when no CPU flags are specified**.  
  - When no CPU arguments are passed, `metric_cpu()` sets all boolean CPU args to `True` to display all available data. `--cpu-svi3-vr-controller-temp` takes a TYPE argument (and optional RAIL_INDEX) rather than a boolean flag — setting it to `True` caused a `TypeError` crash when the code tried to subscript it with `[0][0]`. Added `cpu_svi3_vr_controller_temp` to the show-all exclusion list, following the existing pattern for `cpu_lclk_dpm_level`, `cpu_io_bandwidth`, `cpu_dimm_sb_reg`, and similar argument-taking flags.

- **Fixed `amdsmi_get_gpu_accelerator_partition_profile()` returning incorrect `num_partitions` when `num_partition` is unavailable from GPU metrics**.  
  - GPU metrics no longer always provides `num_partition`. The function now derives the partition count from the active partition type when `num_partition` is not available:
    - SPX → 1, DPX → 2, TPX → 3, QPX → 4
    - CPX → derived from the XCD counter via `amdsmi_get_gpu_xcd_counter()`

- **Fixed `amdsmi_topo_get_p2p_status()` returning a raw `ctypes.c_uint32` object instead of an integer for the `type` field**.  
  - The `'type'` key in the returned dictionary now correctly returns `type_32.value` (an `int`) rather than the unwrapped ctypes object, consistent with the pattern used in `amdsmi_topo_get_link_type()`.

- **Adjusted KFD process caching to be more responsive**.  
  - Updated process caching to allow cache duration adjustment via the `AMDSMI_PROCESS_INFO_CACHE_MS` environment variable for workflows with rapid metric polling.

- **Fixed CLI exit codes to use absolute values**.  
  - Invalid GPU parameters now return positive error codes as documented.

- **Fixed CLI breakage when `amdgpu` driver is not present**.  
  - Improved init to better catch driver loading issues.

- **Aligned `amdsmi_get_gpu_device_uuid()` with HIP/rocminfo UUID format**.  
  - Modified `amdsmi_asic_info_t.asic_serial` to report per-socket serial using KFD's `unique_id`.

- **Fixed multiple bugs in NIC/switch code and `amdsmi_init()` NIC handling**.  
  - Fixed `sizeof` operator precedence, `hw_mon` reset, NUMA=65535 handling, and several CLI function call errors.
  - Fixed `amdsmi_init()` to succeed when no NIC hardware is present.

- **Fixed shared mutex and self-heal**.  
  - Improved self-heal logic to correctly identify and recover from corrupted or uninitialized mutex state.

- **Fixed `cu_occupancy` displaying `0%` instead of `N/A` when file is unavailable**.  
  - Process `cu_occupancy` is now initialized to `INVALID` instead of zero, so `amd-smi process` displays `N/A` rather than a misleading `0%` when the sysfs file is not accessible.

- **Fixed CLI set commands silently succeeding on invalid input values**.  
  - `amd-smi set --profile <INVALID>` now returns a non-zero exit code and lists available profiles in the error message; invalid profile names are rejected at parse time.
  - `amd-smi set --clk-level <CLK_TYPE>` (missing performance level indices) now returns a non-zero exit code with a usage hint instead of silently succeeding.
  - `amd-smi set --power-cap <OUT_OF_RANGE>` now returns a non-zero exit code.
  - `amd-smi set --fan <INVALID>%` no longer prompts the out-of-spec warning before validating the percentage range; invalid values are rejected immediately.

- **Fixed `amd-smi set --profile` help text omitting `BOOTUP_DEFAULT`**.  
  - `BOOTUP_DEFAULT` was always accepted at runtime but was missing from the `--help` profile list. Auditing invalid-input handling exposed this gap. `amd-smi reset --profile` can also be used to return to the bootup default power profile.

- **Fixed `amd-smi monitor --brcm_nic` and `--brcm_switch` flags being registered on non-BRCM systems**.  
  - These flags are now only registered when BRCM hardware is present, preventing spurious failures on AMD GPU-only systems.

- **Fixed `amd-smi` default command alignment**.  
  - Updated default `amd-smi` output to align values to the left for improved readability.
    Several items were misaligned in the default output, and this change ensures a consistent left-aligned format across all fields.
  - *This change is purely cosmetic and does not affect any functionality.*

- **Fixed `amd-smi static -C` reporting `N/A` for SYS/MEM/DF/SOC/DCEF clocks at idle on gfx1151-class APUs**.  
  - `get_frequencies()` in the rsmi backend no longer discards a parsed `pp_dpm_*` DPM table with `STATUS_UNEXPECTED_DATA` when the kernel omits the `*` current-level marker (which happens whenever the SMU power-gates the domain at idle). The supported frequency table is now returned and `current` is reported as `-1` (unknown) until the marker reappears, so `amdsmi_get_clk_freq()` and all callers see the table at idle as well as under load.

## amd_smi_lib for ROCm 7.12.0

### Added

- **Enhanced `amd-smi node` command to display baseboard temperatures**.  
  - Added `--base-board-temps` / `-b` option to display baseboard temperature sensors.
  - Selective display: Use `-p` for NPM only, `-b` for Baseboard only.
  - Default behavior (no flags): Shows both power management and baseboard temperatures.

- **Added UBB (baseboard) power monitoring support**.  
  - Added `ubb_power` field to `amdsmi_power_info_t` for baseboard power in Watts.
  - Added `ubb_power_threshold` field to `amdsmi_npm_info_t` for UBB node power threshold.
  - `amd-smi metric --power` now displays `ubb_power` when available.
  - `amd-smi node -p` now displays `THRESHOLD` when available.
  
- **Added Power Profile set/get/reset to amd-smi CLI**.  
  - New `amd-smi static --profile` command to display current and available power profiles.
  - New `amd-smi set --profile <PROFILE>` command to set the power profile.
  - New `amd-smi reset --profile` command to reset power profile back to default (bootup default).
  - Available profiles: CUSTOM, VIDEO, POWER_SAVING, COMPUTE, VR, 3D_FULL_SCREEN, BOOTUP_DEFAULT.

  ```console
  $ amd-smi static --profile
  GPU: 0
      POWER_PROFILE:
          CURRENT: COMPUTE
          NUM_PROFILES: 7
          PROFILES:
              CUSTOM
              VIDEO
              POWER_SAVING
              COMPUTE
              VR
              3D_FULL_SCREEN
              BOOTUP_DEFAULT
  ```

  ```console
  $ sudo amd-smi set --profile VIDEO
  GPU: 0
      PROFILE: Successfully set power profile to VIDEO
  ```

  ```console
  $ sudo amd-smi reset --profile
  GPU: 0
      RESET_PROFILE:
          POWER_PROFILE: Successfully reset Power Profile to default (bootup default)
  ```

- **Added `os_kernel_version` to `amd-smi static --driver` and `amd-smi` output**.  
  - Displays the Linux kernel version from `os.uname().release`.

- **Added new error status code `AMDSMI_STATUS_IPC_ERROR` (21)**.  
  - For IPC communication errors.

### Changed

- **Improved VRAM usage reporting performance and reliability**.  
  - Optimized memory queries with batching and caching (< 1 μs for cached queries)
  - Improved error handling and automatic fallback mechanisms
  - Configurable behavior via environment variables:
    - `AMDSMI_KFD_CACHE_TTL_MS`: Cache time-to-live in milliseconds (default: 250, set to 0 to disable)
    - `AMDSMI_KFD_USE_ORIG_VRAM`: Use original method if needed (default: 0)
    - Additional low-level tuning variables available for advanced debugging
  
- **Enhanced logging system** with better resource management and error reporting

- **Modified asic_serial to display "N/A" when not available**.  
  - Skipped setting asic_serial when kfd node unique_id is 0.
  - Python interface will validate against max uint64 to display N/A.

- **Made `libdrm` a required runtime dependency** ([#3349](https://github.com/ROCm/rocm-systems/pull/3349)).  
  - Debian: `libdrm-dev` moved from `Recommends` to `Depends` on the `amd-smi-lib` package; `libdrm-amdgpu-dev` remains in `Recommends` (not shipped by Debian 10).
  - RPM: `libdrm-devel` moved from `Suggests` to `Requires`; `libdrm-amdgpu-devel` remains in `Suggests` (not shipped by Azure Linux).
  - Building from source now requires `libdrm-dev` / `libdrm-devel`; the project `Dockerfile` was updated accordingly.
  - Removed the "libdrm is optional" note from `docs/install/install.md` — firmware and hardware-IP queries previously gated on libdrm are now always available.

### Removed

- **Removed `amd-smi reset --reload-driver` and `amd-smi reset -r` option from CLI only**.  
  - The API `amdsmi_gpu_driver_reload()` will remain for backwards compatibility until deprecated in a future release.
  - Use modprobe to reload driver, e.g.,

  ```console
  sudo modprobe -r amdgpu
  sudo modprobe amdgpu
  ```

  - For historical reference; this option has been removed [<i><b>Separated driver reload from `amdsmi_set_gpu_memory_partition()` / `amdsmi_set_gpu_memory_partition_mode()` and CLI (`sudo amd-smi set -M <NPS mode>`)</b></i>](#separate-driver-reload-anchor)

### Optimized

- **Adjusted the KFD Process cache to be more responsive and have and adjustable cache duration**.  
  - Users may adjust the cache duration by setting the environment variable 'AMDSMI_PROCESS_INFO_CACHE_MS'.

### Resolved Issues

- **Fixed `amdsmi_get_gpu_memory_usage()` blocking driver reloads and partition changes**.  
  - Memory queries no longer create persistent process entries that interfere with driver operations
  - Use `AMDSMI_KFD_USE_ORIG_VRAM=1` environment variable to revert to previous behavior if needed

- **Fixed sensor ID formatting bug** that caused terminal output pollution for sensor IDs greater than 9

- **Fixed XGMI PLPD policy parsing in `amdsmi_get_xgmi_plpd()` returning incorrect data**.  
  - Previously, only the first XGMI PLPD policy was correctly displayed; subsequent policies showed `policy_id=0` with empty descriptions.
  - Root cause was incorrect usage of `ctypes.string_at()` combined with overly broad exception handling that silently masked errors.
  - Fix uses direct `.decode()` on c_char arrays, matching the proven pattern in `amdsmi_get_soc_pstate()`.
  - Affected command: `amd-smi static --xgmi-plpd`

- **Fixed an issue on MI3x ASICs in mVF configurations where `amd-smi xgmi --source-status` and `amd-smi xgmi --link-status` incorrectly reported links as down**.  
  - Updated driver logic to detect when `amdsmi_get_gpu_xgmi_link_status()` should return `AMDSMI_STATUS_NOT_SUPPORTED`. In mVF configurations, links are connected over XGMI and active, but security restrictions prevent the driver from exposing link status. In these cases we now return `AMDSMI_STATUS_NOT_SUPPORTED` instead of reporting the links as down.
  - Example outputs:

    ```console
    $ amd-smi xgmi --source-status

    GPU LINK PORT STATUS:
           bdf           port_num
    GPU0   0000:05:00.0  N/A  N/A  N/A  N/A  N/A  N/A  N/A  N/A
    GPU1   0000:15:00.0  N/A  N/A  N/A  N/A  N/A  N/A  N/A  N/A
    GPU2   0000:65:00.0  N/A  N/A  N/A  N/A  N/A  N/A  N/A  N/A
    GPU3   0000:75:00.0  N/A  N/A  N/A  N/A  N/A  N/A  N/A  N/A
    GPU4   0000:85:00.0  N/A  N/A  N/A  N/A  N/A  N/A  N/A  N/A
    GPU5   0000:95:00.0  N/A  N/A  N/A  N/A  N/A  N/A  N/A  N/A
    GPU6   0000:e5:00.0  N/A  N/A  N/A  N/A  N/A  N/A  N/A  N/A
    GPU7   0000:f5:00.0  N/A  N/A  N/A  N/A  N/A  N/A  N/A  N/A
    ...  
    ```

    ```console
    $ amd-smi xgmi --link-status

    XGMI LINK STATUS:
           bdf           GPU0          GPU1          GPU2          GPU3          GPU4          GPU5          GPU6          GPU7
    GPU0   0000:05:00.0  SELF          N/A           N/A           N/A           N/A           N/A           N/A           N/A
    GPU1   0000:15:00.0  N/A           SELF          N/A           N/A           N/A           N/A           N/A           N/A
    GPU2   0000:65:00.0  N/A           N/A           SELF          N/A           N/A           N/A           N/A           N/A
    GPU3   0000:75:00.0  N/A           N/A           N/A           SELF          N/A           N/A           N/A           N/A
    GPU4   0000:85:00.0  N/A           N/A           N/A           N/A           SELF          N/A           N/A           N/A
    GPU5   0000:95:00.0  N/A           N/A           N/A           N/A           N/A           SELF          N/A           N/A
    GPU6   0000:e5:00.0  N/A           N/A           N/A           N/A           N/A           N/A           SELF          N/A
    GPU7   0000:f5:00.0  N/A           N/A           N/A           N/A           N/A           N/A           N/A           SELF
    ...
    ```

- **Fixed `amd-smi xgmi --metric` on devices without XGMI links reporting `bit_rate` and `max_bandwidth` with their maximum values instead of `N/A`**.  
  - Updated the logic to report `N/A` for `bit_rate` and `max_bandwidth` when no XGMI links are present.
  - Below shows a before and after of the fix (using 2 Navi ASICs without XGMI links as an example).

    - Before fix:
    ```console
    $ amd-smi xgmi --metric

    LINK METRIC TABLE:
           bdf           bit_rate  max_bandwidth  link_type  GPU0         GPU1
    GPU0   0000:08:00.0  65535 Gb/s4294967295 Gb/sN/A
     Read                                                    N/A          N/A
     Write                                                   N/A          N/A
    GPU1   0000:44:00.0  65535 Gb/s4294967295 Gb/sN/A
     Read                                                    N/A          N/A
     Write                                                   N/A          N/A
    ...
    ```
    - After fix:

    ```console
    $ amd-smi xgmi --metric

    LINK METRIC TABLE:
           bdf           bit_rate  max_bandwidth  link_type  GPU0         GPU1
    GPU0   0000:08:00.0  N/A       N/A             N/A
     Read                                                    N/A          N/A
     Write                                                   N/A          N/A
    GPU1   0000:44:00.0  N/A       N/A             N/A
     Read                                                    N/A          N/A
     Write                                                   N/A          N/A
    ...
    ```

### Upcoming Changes

- N/A

### Known Issues

- N/A

## amd_smi_lib for ROCm 7.11.0

### Updated

- **Updated support for set and get option for the following APIs**.  

  - Users can now set the power efficiency mode using `amd-smi set --cpu-pwr-eff-mode MODE(0-5) UTIL(0-100) PPT_LIMIT(in mW)`
  - UTIL and PPT_LIMIT are valid only if mode is 4 or 5 and Family 1Ah Models 50h-57h onwards.

  ```console
  amd-smi  set --cpu-pwr-eff-mode 4 100 3000
  CPU: 0
      PWR_EFF_MODE:
          MODE: 4
          UTIL: 100%
          PPT_LIMIT: 3.000 Watts
          RESPONSE: Set power efficiency mode operation successful

  CPU: 1
      PWR_EFF_MODE:
          MODE: 4
          UTIL: 100%
          PPT_LIMIT: 3.000 Watts
          RESPONSE: Set power efficiency mode operation successful
  ```

  - Users can now read the power efficiency mode using `amd-smi metric --cpu-pwr-eff-mode`

  ```console
  amd-smi  metric --cpu-pwr-eff-mode
  CPU: 0
      PWR_EFF_MODE:
          MODE: 4
          UTIL: 100%
          PPT_LIMIT: 3.000 Watts

  CPU: 1
      PWR_EFF_MODE:
          MODE: 4
          UTIL: 100%
          PPT_LIMIT: 3.000 Watts
  ```

  - Users can now set the XGMI Pstate range using `amd-smi set --cpu-xgmi-pstate-range MIN_PSTATE(0-1) MAX_PSTATE(0-1)`

  ```console
  amd-smi set --cpu-xgmi-pstate-range 1 1
  CPU: 0
      XGMI_PSTATE_RANGE:
          RESPONSE: Set, MIN_PSTATE: 1, MAX_PSTATE: 1, successful

  CPU: 1
      XGMI_PSTATE_RANGE:
          RESPONSE: Set, MIN_PSTATE: 1, MAX_PSTATE: 1, successful
  ```

  - Users can now read the XGMI Pstate range using `amd-smi metric --cpu-xgmi-pstate-range`

  ```console
  amd-smi metric --cpu-xgmi-pstate-range
  CPU: 0
      XGMI_PSTATE_RANGE:
          MIN_PSTATE: 0
          MAX_PSTATE: 0

  CPU: 1
      XGMI_PSTATE_RANGE:
          MIN_PSTATE: 0
          MAX_PSTATE: 0
  ```

  - Users can now set cpu rail isolated frequency policy using `amd-smi set --cpu-railisofreq-policy VALUE(0-1)`.

  ```console
  amd-smi set --cpu-railisofreq-policy 1
  CPU: 0
      RAILISOFREQ_POLICY:
          RESPONSE: Set, VALUE: 1, successful

  CPU: 1
      RAILISOFREQ_POLICY:
          RESPONSE: Set, VALUE: 1, successful
  ```

  - Users can now read the cpu rail isolated frequency policy  using `amd-smi metric --cpu-railisofreq-policy`.

  ```console
  amd-smi metric --cpu-railisofreq-policy
  CPU: 0
      RAILISOFREQ_POLICY:
          VALUE: 1

  CPU: 1
      RAILISOFREQ_POLICY:
          VALUE: 1
  ```

  - Users can now set the Data Fabric C-state control status using `amd-smi set --cpu-dfcstate-ctrl VALUE(0-1)`.

  ```console
  amd-smi set --cpu-dfcstate-ctrl 1
  CPU: 0
      DFCSTATE_CTRL:
          RESPONSE: Set, VALUE: 1, successful

  CPU: 1
      DFCSTATE_CTRL:
          RESPONSE: Set, VALUE: 1, successful
  ```

  - Users can now read the Data Fabric C-state control status  using `amd-smi metric --cpu-dfcstate-ctrl`.

  ```console
  amd-smi metric --cpu-dfcstate-ctrl
  CPU: 0
      DFCSTATE_CTRL:
          VALUE: 1

  CPU: 1
      DFCSTATE_CTRL:
          VALUE: 1
  ```

  - Users can now set the PC6 enabling control status using `amd-smi set --cpu-pc6-enable VALUE(0-1)`.

  ```console
  amd-smi set --cpu-pc6-enable 1
  CPU: 0
      PC6_ENABLE:
          RESPONSE: Set, VALUE: 1, successful

  CPU: 1
      PC6_ENABLE:
          RESPONSE: Set, VALUE: 1, successful
  ```

  - Users can now read the PC6 enabling control status using `amd-smi metric --cpu-pc6-enable`.

  ```console
  amd-smi metric --cpu-pc6-enable
  CPU: 0
      PC6_ENABLE:
          VALUE: 1

  CPU: 1
      PC6_ENABLE:
          VALUE: 1
  ```

  - Users can now set the CC6 enabling control status using `amd-smi set --cpu-cc6-enable VALUE(0-1)`.

  ```console
  amd-smi set --cpu-cc6-enable 1
  CPU: 0
      CC6_ENABLE:
          RESPONSE: Set, VALUE: 1, successful

  CPU: 1
      CC6_ENABLE:
          RESPONSE: Set, VALUE: 1, successful
  ```

  - Users can now read the CC6 enabling control status using `amd-smi metric --cpu-cc6-enable`.

  ```console
  amd-smi metric --cpu-cc6-enable
  CPU: 0
      CC6_ENABLE:
          VALUE: 1

  CPU: 1
      CC6_ENABLE:
          VALUE: 1
  ```

  - Users can now read 4 bytes data at a given register offset on the target DIMM address using `amd-smi metric --cpu-dimm-sb-reg`.

  ```console
  amd-smi metric --cpu-dimm-sb-reg 0x87 0xA 0 1
  CPU: 0
      DIMM_SB_REG:
          DIMMADDRESS: 0x87
          LID: 0x0A
          OFFSET: 0x0000
          REGSPACE: 1
          DATA: 0x01121230
  ```

  - Users can now write 4 byte data at a given register offset on the target DIMM address using `amd-smi set --cpu-dimm-sb-reg`.

  ```console
  amd-smi set --cpu-dimm-sb-reg 0x87 0xA 0x2c0 1 0x11
  CPU: 0
      DIMM_SB_REG:
          DIMMADDRESS: 0x87
          LID: 0x0A
          OFFSET: 0x02C0
          REGSPACE: 1
          DATA: 0x00000011
          RESPONSE: Set DIMM sideband register write operation successful
  ```

  - Users can now read CCD power using `amd-smi metric --core-ccd-power`.

  ```console
  amd-smi metric --core-ccd-power -O 0 1 2
  CORE: 0
      CCD_POWER:
          VALUE: 3.501 Watts

  CORE: 1
      CCD_POWER:
          VALUE: 3.501 Watts

  CORE: 2
      CCD_POWER:
          VALUE: 3.501 Watts
  ```

  - Users can now read Tdelta value using `amd-smi metric --cpu-tdelta`.

  ```console
  amd-smi metric --cpu-tdelta
  CPU: 0
      TDELTA:
          VALUE: 0

  CPU: 1
      TDELTA:
          VALUE: 0
  ```

  - Users can now read Temperature of SVI3 VR controller using `amd-smi metric --cpu-svi3-vr-controller-temp TYPE(0-1) RAIL_INDEX(0-4)`.
  - RAIL_INDEX (0-4) is valid only when the TYPE is 1.

  ```console
  amd-smi metric --cpu-svi3-vr-controller-temp 1 1
  CPU: 0
      SVI3_VR_CONTROLLER_TEMP:
          RAIL_SELECTION: 1
          RAIL_INDEX: 1
          TEMPERATURE: 30.0 Degree C

  CPU: 1
      SVI3_VR_CONTROLLER_TEMP:
          RAIL_SELECTION: 1
          RAIL_INDEX: 1
          TEMPERATURE: 32.0 Degree C
  ```

  - Users can now read enabled HSMP command bit mask using `amd-smi metric --cpu-enabled-commands`.

  ```console
  amd-smi metric --cpu-enabled-commands
  CPU: 0
      ENABLED_COMMANDS:
          READ_ENABLED_COMMANDS_BITMASK0: 0xFFFFFFFF
          READ_ENABLED_COMMANDS_BITMASK1: 0xFFFFFFFF
          READ_ENABLED_COMMANDS_BITMASK2: 0x7FFFFFFF
          WRITE_ENABLED_COMMANDS_BITMASK0: 0xFFFFFFFF
          WRITE_ENABLED_COMMANDS_BITMASK1: 0xFFFFFFFF
          WRITE_ENABLED_COMMANDS_BITMASK2: 0x7FFFFFFF

  CPU: 1
      ENABLED_COMMANDS:
          READ_ENABLED_COMMANDS_BITMASK0: 0xFFFFFFFF
          READ_ENABLED_COMMANDS_BITMASK1: 0xFFFFFFFF
          READ_ENABLED_COMMANDS_BITMASK2: 0x7FFFFFFF
          WRITE_ENABLED_COMMANDS_BITMASK0: 0xFFFFFFFF
          WRITE_ENABLED_COMMANDS_BITMASK1: 0xFFFFFFFF
          WRITE_ENABLED_COMMANDS_BITMASK2: 0x7FFFFFFF
  ```

  - Users can now read core floor frequency limit using `amd-smi metric --core-floor-limit`.

  ```console
  amd-smi metric --core-floor-limit -O 0 1 2
  CORE: 0
      FLOOR_LIMIT:
          VALUE: 600 MHz

  CORE: 1
      FLOOR_LIMIT:
          VALUE: 600 MHz

  CORE: 2
      FLOOR_LIMIT:
          VALUE: 600 MHz
  ```

  - Users can now read core effictive floor frequency limit using `amd-smi metric --core-eff-floor-limit`.

  ```console
  amd-smi metric --core-eff-floor-limit -O 0 1 2
  CORE: 0
      EFF_FLOOR_LIMIT:
          VALUE: 600 MHz

  CORE: 1
      EFF_FLOOR_LIMIT:
          VALUE: 600 MHz

  CORE: 2
      EFF_FLOOR_LIMIT:
          VALUE: 600 MHz

  ```

  - Users can now set core floor frequency limit using `amd-smi set --core-floor-limit FLOOR_LIMIT(in MHz)`.
  ```console
  amd-smi set --core-floor-limit 1200 -O 0 1 2
  CORE: 0
      FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful

  CORE: 1
      FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful

  CORE: 2
      FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful

  ```

  - Users can now set cpu floor frequency limit using `amd-smi set --cpu-floor-limit FLOOR_LIMIT (in MHz)`.

  ```console
  amd-smi set --cpu-floor-limit 1200
  CPU: 0
      FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful

  CPU: 1
      FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful
  ```

  - Users can now set core msr floor frequency limit using `amd-smi set --core-msr-floor-limit MSR_FLOOR_LIMIT (in MHz)`.

  ```console
  amd-smi set --core-msr-floor-limit 1200 -O 0 1 2
  CORE: 0
      MSR_FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful

  CORE: 1
      MSR_FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful

  CORE: 2
      MSR_FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful
  ```

  - Users can now set cpu msr floor frequency limit using `amd-smi set --cpu-msr-floor-limit MSR_FLOOR_LIMIT (in MHz)`.

  ```console
  amd-smi set --cpu-msr-floor-limit 1200
  CPU: 0
      MSR_FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful

  CPU: 1
      MSR_FLOOR_LIMIT:
          RESPONSE: Set, VALUE: 1200 MHz, successful
  ```

  - Users can now set the socket + DIMM combined power (SDPS) limit using `amd-smi set --cpu-sdps-limit SDPS_LIMIT (in mW)`.

  ```console
  amd-smi set  --cpu-sdps-limit 300000
  CPU: 0
      SDPS_LIMIT:
          RESPONSE: Set, VALUE: 300.000 Watts, successful
  ```

  - Users can now read set the socket + DIMM combined power (SDPS) limit using `amd-smi metric --cpu-sdps-limit`.

  ```console
  amd-smi metric --cpu-sdps-limit
  CPU: 0
      SDPS_LIMIT:
          VALUE: 300.000 Watts
  ```

### Added

- **Added `--hex` flag to `amd-smi bad-pages` command**.  
  - Added `--hex` option to display page addresses and sizes in hexadecimal format with `0x` prefix

  ```console
  $ amd-smi bad-pages --hex
  GPU: 0
      RETIRED:
          PAGE_ADDRESS: 0x7f8000
          PAGE_SIZE: 0x1000
          STATUS: RESERVED
      PENDING: N/A
      UN_RES: N/A
  ```

- **Added flexible argument ordering for `amd-smi set --power-cap`**.  
  - The `--power-cap` option now accepts arguments in any order, improving usability.
    - Both syntaxes are now supported:
      - `amd-smi set --power-cap <power-cap-type> <new-cap>`
      - `amd-smi set --power-cap <new-cap> <power-cap-type>`

  Example:

  ```console
  $ sudo amd-smi set --power-cap ppt1 1150
  GPU: 0
    POWERCAP: Successfully set ppt1 power cap to 1150W
    ...

  $ sudo amd-smi set --power-cap 1100 ppt1
  GPU: 0
    POWERCAP: Successfully set ppt1 power cap to 1100W
    ...
  ```

- **Added support for CPUISOFreqPolicy and DFCState Control APIs**.  
  - Set/get CPU ISO frequency policy:
    - `amd-smi set --cpu-railisofreq-policy (0-1)`
    - `amd-smi metric --cpu-railisofreq-policy`
  - Set/get Data Fabric C-state control:
    - `amd-smi set --cpu-dfcstate-ctrl (0-1)`
    - `amd-smi metric --cpu-dfcstate-ctrl`

  ```console
  $ amd-smi set --cpu-railisofreq-policy 0
  CPU: 0
    CPURAILISO:
        STATE: Set CPU ISO frequency policy operation successful

  CPU: 1
    CPURAILISO:
        STATE: Set CPU ISO frequency policy operation successful

  $ amd-smi metric --cpu-railisofreq-policy
  CPU: 0
    CPURAILISO:
        CPURAILISOFREQ_POLICY: 0

  CPU: 1
    CPURAILISO:
        CPURAILISOFREQ_POLICY: 0

  $ amd-smi set --cpu-dfcstate-ctrl 0
  CPU: 0
    DFCSTATECTRL:
        STATE: DFCState control operation successful

  CPU: 1
    DFCSTATECTRL:
        STATE: DFCState control operation successful

  $ amd-smi metric --cpu-dfcstate-ctrl
  CPU: 0
    DFCSTATE:
        DFCSTATECTRL_STATUS: 0

  CPU: 1
    DFCSTATE:
        DFCSTATECTRL_STATUS: 0
  ```

### Changed

- **Modified output file handling options for `--file` argument**.  
  - Previously tool always appended to existing files without confirmation
  - Now added `--overwrite` / `--append` flag: Overwrites / Appends file content
  - Interactive prompt when file exists and no flag is specified:
    - User can choose: Overwrite (o) / Append (a) / Cancel (N)

### Removed

- N/A

### Optimized

- N/A

### Resolved Issues

- **Fixed structure mismatch bug in `amdsmi_get_soc_pstate()` and `amdsmi_get_xgmi_plpd()`**.  
  - This issue caused all policy IDs to display as 0.

### Upcoming Changes

- N/A

### Known Issues

- N/A

## amd_smi_lib for ROCm 7.2.1

### Added

- **Added gpu_board and base_board temperatures to monitor**.  
  - Added GPU board and base board temperature sensors to `amd-smi monitor` command.

### Changed

- N/A

### Removed

- N/A

### Optimized

- N/A

### Resolved Issues

- **Fixed `amd-smi metric` JSON output under watch mode**.  
  - Resolved issue where JSON output was not formatted correctly when using watch mode with metrics.

- **Fixed `amd-smi` not redirecting output to file when `--json` option is used**.  
  - Resolved issue where output was not properly redirected to file when using JSON format.

- **Fixed `amd-smi ras --cper` component not being redirected to output file with `--follow`**.  
  - Resolved issue where CPER component output was not redirected when using the follow option.

- **Fixed list of AFIDs printing garbage values when given invalid CPER files**.  
  - Resolved issue where invalid CPER files caused garbage output for AFID lists.

- **Fixed JSON output for `amd-smi reset`**.  
  - Resolved issue where JSON output was not formatted correctly for reset commands.

- **Fixed `amd-smi set` commands showing an AttributeError when partition attributes are not present**.  
  - Resolved `AttributeError: 'Namespace' object has no attribute 'compute_partition'` error
  - Now using safe `getattr()` access pattern for optional arguments in set_gpu function


### Known Issues

- N/A

## amd_smi_lib for ROCm 7.2.0

### Added

- **Added support for get and set option for CPUISOFreqPolicy control API and DFCState Control API**.  
  - Users can now set the  CPU ISO frequency policy  using `amd-smi set --cpu-railisofreq-policy (0-1)`.
  - Users can now read the CPU ISO frequency policy  using `amd-smi metric --cpu-railisofreq-policy`.
  - Users can now set the  Data Fabric C-state control status using `amd-smi set --cpu-dfcstate-ctrl (0-1)`.
  - Users can now read the Data Fabric C-state control status  using `amd-smi metric --cpu-dfcstate-ctrl`.

  ```console
  $amd-smi set --cpu-railisofreq-policy 0
  CPU: 0
      RAILISOFREQ_POLICY:
          RESPONSE: Set, VALUE: 1, successful

  CPU: 1
      RAILISOFREQ_POLICY:
          RESPONSE: Set, VALUE: 1, successful

  $amd-smi metric --cpu-railisofreq-policy
  CPU: 0
      RAILISOFREQ_POLICY:
          VALUE: 1

  CPU: 1
      RAILISOFREQ_POLICY:
          VALUE: 1

  $amd-smi set --cpu-dfcstate-ctrl 0
  CPU: 0
      DFCSTATE_CTRL:
          RESPONSE: Set, VALUE: 1, successful

  CPU: 1
      DFCSTATE_CTRL:
          RESPONSE: Set, VALUE: 1, successful

  $amd-smi metric --cpu-dfcstate-ctrl
  CPU: 0
      DFCSTATE_CTRL:
          VALUE: 1

  CPU: 1
      DFCSTATE_CTRL:
          VALUE: 1
 ```
- **Added GPU and base board temperature `amd-smi monitor` CLI support**.  
  - Added `--gpu-board-temps` option to `amd-smi monitor` command for GPU board temperature sensors
  - Added `--base-board-temps` option to `amd-smi monitor` command for base board temperature sensors

- **Added Node Power Management (NPM) support**.  
  - Added new Node Power Management APIs and CLI for node monitoring
  - Added C++ API functions:
    - `amdsmi_get_node_handle()`: Get handle for node devices
    - `amdsmi_get_npm_info()`: Retrieve Node Power Management information
  - Added C++ types to support NPM API:
    - `amdsmi_npm_status_t`: whether NPM is enabled or disabled
    - `amdsmi_npm_info_t`: a struct containing the status and the Node-level power limit in Watts
  - Added Python API wrappers for new node device functions
  - Added `amd-smi node` CLI command for Node Power Management operations
  - Currently supported for OAM_ID 0 only.

- **Added the following C API's to amdsmi_interface.py**.  
  - amdsmi_get_cpu_handle()
  - amdsmi_get_esmi_err_msg()
  - amdsmi_get_gpu_event_notification()
  - amdsmi_get_processor_count_from_handles()
  - amdsmi_get_processor_handles_by_type()
  - amdsmi_gpu_validate_ras_eeprom()
  - amdsmi_init_gpu_event_notification()
  - amdsmi_set_gpu_event_notification_mask()
  - amdsmi_stop_gpu_event_notification()
  - amdsmi_get_gpu_busy_percent()

- **Added additional return value to API amdsmi_get_xgmi_plpd()**.  
  - The entry `policies` is added to the end of the dictionary to match API definition.
  - The entry `plpds` is marked for deprecation as it has the same information as `policies`.

- **Added pcie levels to `amd-smi static --bus` command**.  
  - The static --bus option has been updated to include the range of pcie levels that one may set a device to.
  - Levels are a 2-tuple composed of the PCIE speed and bandwidth.

  ```console
  $ amd-smi static --bus
  GPU: 0
  BUS:
  BDF: 0000:43:00.0
  MAX_PCIE_WIDTH: 16
  MAX_PCIE_SPEED: 16 GT/s
  PCIE_LEVELS:
    0: (2.5 GT/s, 1)
    1: (5.0 GT/s, 4)
    2: (16.0 GT/s, 16)
  PCIE_INTERFACE_VERSION: Gen 4
  SLOT_TYPE: CEM
  ```

- **Added evicted_time metric for kfd processes**.  
  - Time that queues are evicted on a GPU in milliseconds
  - Added to CLI in `amd-smi monitor -q` and `amd-smi process`
  - Added to C API and Python API:
    - amdsmi_get_gpu_process_list()
    - amdsmi_get_gpu_compute_process_info()
    - amdsmi_get_gpu_compute_process_info_by_pid()

- **Added new VRAM types to  `amdsmi_vram_type_t`**.  
  - `amd-smi static --vram` & `amdsmi_get_gpu_vram_info()` now support the following types:
  - DDR5, LPDDR4, LPDDR5, and HBM3E

- **Added support for PPT1 power limit information**.  
  - Support has been added for querying and setting the PPT (Package Power Tracking) limits
    - There are two PPT limits, PPT0 has lower limit and tracks a filtered version of the input power and PPT1 has higher limit but tracks the raw input power. This is to catch spikes in the raw data.  
  - New C++ API added:
    - amdsmi_get_supported_power_cap(): Returns which power cap types are supported on the device (PPT0, PPT1). This will allow users to know which power cap types they can get/set.
    - Original APIs remain the same but now can get/set both PPT0 and PPT1 limits (on supported hardware):
      - amdsmi_get_power_cap_info()
      - amdsmi_set_power_cap()
  - New C++ type added:
    - `amdsmi_power_cap_type_t`: The power cap type, either PPT0 or PPT1
  - See the Changed section for changes made to the `set` and `static` commands regarding support for PPT1.  

- **Added PTL Support to `amd-smi static` and `amd-smi set`**.  
  - Performance TOPS Limiter (PTL) is a control system that, when in place, constrains the product to never deliver more than a specified TOPS / second.
  - New C++ API added:
    - `amdsmi_get_gpu_ptl_state()`: retrieves whether PTL (Peak Tops Limiter) is currently enabled or disabled for the specified processor
    - `amdsmi_set_gpu_ptl_state()`: enables or disables PTL (Peak Tops Limiter) operation
    - `amdsmi_get_gpu_ptl_formats()`: retrieves the current PTL formats for the specified processor
    - `amdsmi_set_gpu_ptl_formats()`: Set PTL with specified preferred data formats
  - New C++ type added:
    - `amdsmi_ptl_data_format_t`: Valid PTL data formats: I8, F16, BF16, F32, F64
  - `amd-smi set` now support --ptl-status 0|1 and --ptl-format FORMAT1,FORMAT2
  - `amd-smi static -l` shows current state and format of PTL

  ```console
  $ amd-smi static -l
  GPU: 0
      LIMIT:
        PTL_STATE: Enabled
        PTL_FORMAT: I8,F64
  ```

- **Added support to process CPER files even on machines without GPU and CPER is not enabled.**  
  - New `--cper-file` option:
  ```console
  $ sudo amd-smi ras --afid --cper-file cpers/bad_cper/incomplete_aca.cper --decode --folder /tmp/cper_dump
timestamp            gpu_id  severity             file_name         list of afids
2070/01/01 00:26:21  -       FATAL                fatal-1.cper      28
2070/01/01 00:26:21  -       FATAL                fatal-2.cper      28
  ```

### Changed

- **The `amd-smi` command now shows hsmp rather than amd_hsmp**.  
  - The hsmp driver version can be shown without the amdgpu version using `amd-smi version -c`

  ```console
   $ amd-smi version
   AMDSMI Tool: 24.7.1+b446d6c-dirty | AMDSMI Library version: 24.7.2.0 | ROCm version: N/A | amdgpu version: 6.10.10 | hsmp version: 2.2

   $ amd-smi version -c
   AMDSMI Tool: 24.7.1+b446d6c-dirty | AMDSMI Library version: 24.7.2.0 | ROCm version: N/A | hsmp version: 2.2
   ...
  ```

- **`amd-smi set --power-cap` now accepts specification of the power cap type**.  
  - Command now takes the form: `amd-smi set --power-cap <power-cap-type> <new-cap>`
  - Default power cap type will be ppt0
  - Acceptable power cap types are "ppt0" and "ppt1"

  ```console
  $ sudo amd-smi set --power-cap ppt1 1150
  GPU: 0
    POWERCAP: Successfully set ppt1 power cap to 1150W
    ...
  ```

- **`amd-smi reset --power-cap` will attempt to reset both power caps**.  
  - When using the reset command, both PPT0 and PPT1 power caps will be reset to their default values. If a device only has PPT0, then only PPT0 will be reset.  
    Ex.

    ```console
    $ sudo amd-smi reset --power-cap
    GPU: 0
      POWERCAP:
          PPT0: Successfully reset power cap to 203W
          PPT1: [AMDSMI_STATUS_NOT_SUPPORTED] Unable to reset to default power cap
      ...
    ```

- **`amd-smi static --limit` now has a PPT1 section when PPT1 is available**.  
  - The static --limit command has been updated to include PPT1 power limit information when available on the device.

    ```console
    $ amd-smi static --limit
    GPU: 0
      LIMIT:
          PPT0:
              MAX_POWER_LIMIT: 1000
              MIN_POWER_LIMIT: 0
              SOCKET_POWER_LIMIT: 1000
          PPT1:
              MAX_POWER_LIMIT: 1300
              MIN_POWER_LIMIT: 1100
              SOCKET_POWER_LIMIT: 1250
          SLOWDOWN_EDGE_TEMPERATURE: N/A
          ...
    ```

    - JSON and CSV formats are updated to reflect this change as well.  
      Ex.

      ```console
      $ amd-smi static --limit --json
      {
        "gpu_data": [
            {
                "gpu": 0,
                "limit": {
                    "ppt0": {
                        "max_power_limit": {
                            "value": 203,
                            "unit": "W"
                        },
                        "min_power_limit": {
                            "value": 0,
                            "unit": "W"
                        },
                        "socket_power_limit": {
                            "value": 100,
                            "unit": "W"
                        }
                    },
                    "ppt1": {
                        "max_power_limit": "N/A",
                        "min_power_limit": "N/A",
                        "socket_power_limit": "N/A"
                    },
                    ...
                }
            },
            ...
      ```

      ```console
      $ amd-smi static --limit --csv
      gpu,ppt0_max_power_limit,ppt0_min_power_limit,ppt0_socket_power_limit,ppt1_max_power_limit,ppt1_min_power_limit,ppt1_socket_power_limit,slowdown_edge_temperature,slowdown_hotspot_temperature,slowdown_vram_temperature,shutdown_edge_temperature,shutdown_hotspot_temperature,shutdown_vram_temperature
      0,203,0,100,N/A,N/A,N/A,100,110,100,105,115,105
      1,213,0,100,N/A,N/A,N/A,109,110,100,114,115,105
      ```

### Removed

- N/A

### Optimized

- N/A

### Resolved Issues

- **Fixed an issue where amdsmi_get_gpu_od_volt_info() returned a reference to a python object**.  
  - The returned dictionary was changed to return values in all fields

### Upcoming Changes

- N/A

### Known Issues

- N/A

## amd_smi_lib for ROCm 7.1.0

### Added

- **Added `GPU LINK PORT STATUS` table to `amd-smi xgmi` command**.  
  - The `amd-smi xgmi -s` or `amd-smi xgmi --source-status` will show `GPU LINK PORT STATUS` table.  

- **Added `amdsmi_get_gpu_revision()` to Python API**  
  - This function retrieves the GPU revision ID. Available in `amdsmi_interface.py` as `amdsmi_get_gpu_revision()`.

- **Added gpuboard and baseboard temperatures to `amd-smi metric` command**.  
  - The metric command has been updated with various gpuboard and baseboard temperatures in degrees Celsius. Users can access these
  values through the `-G/--gpuboard` or `-b/--baseboard` options or obtain all of them as normal using the `amd-smi metric` command without
  any options. If the hardware does not support gpuboard or baseboard temperatures, then the values will be hidden from the default `metric` view.

  ```console
  $ amd-smi metric -b
  GPU: 0
      BASEBOARD:
          TEMPERATURE:
              FIRST: 78
              UBB_FRONT: 55
              UBB_BACK: 49
              UBB_OAM7: 86
              UBB_IBC: 94
              UBB_UFPGA: 49
              UBB_OAM1: 78
              OAM_0_1_HSC: 54
              OAM_2_3_HSC: 32
              OAM_4_5_HSC: 14
              OAM_6_7_HSC: 85
              UBB_FPGA_0V72_VR: 43
              UBB_FPGA_3V3_VR: 41
              RETIMER_0_1_2_3_1V2_VR: 64
              RETIMER_4_5_6_7_1V2_VR: 56
              RETIMER_0_1_0V9_VR: 74
              RETIMER_4_5_0V9_VR: 34
              RETIMER_2_3_0V9_VR: 85
              RETIMER_6_7_0V9_VR: 92
              OAM_0_1_2_3_3V3_VR: 29
              OAM_4_5_6_7_3V3_VR: 13
              IBC_HSC: 41
              IBC: 43

  $ amd-smi metric -G
  GPU: 0
      GPUBOARD:
          TEMPERATURE:
              NODE_RETIMER_X: 43
              NODE_OAM_X_IBC: 24
              NODE_OAM_X_IBC_2: 56
              NODE_OAM_X_VDD18_VR: 34
              NODE_OAM_X_04_HBM_B_VR: 53
              NODE_OAM_X_04_HBM_D_VR: 47
              VR_FIRST: 58
              VDDCR_VDD1: 78
              VDDCR_VDD2: 35
              VDDCR_VDD3: 73
              VDDCR_SOC_A: 12
              VDDCR_SOC_C: 57
              VDDCR_SOCIO_A: 39
              VDDCR_SOCIO_C: 75
              VDD_085_HBM: 64
              VDDCR_11_HBM_B: 92
              VDDCR_11_HBM_D: 87
              VDD_USR: 46
              VDDIO_11_E32: 98

  $ amd-smi metric
  GPU: 0
      USAGE:
          GFX_ACTIVITY: 0 %
          UMC_ACTIVITY: 0 %
          ...
      POWER:
          SOCKET_POWER: 140 W
          GFX_VOLTAGE: N/A
          ...
      CLOCK:
          GFX_0:
              CLK: 132 MHz
              MIN_CLK: 500 MHz
          ...
      TEMPERATURE:
          EDGE: N/A
          HOTSPOT: 37 °C
          ...
      PCIE:
          WIDTH: 16
          SPEED: 32 GT/s
          ...
      GPUBOARD:
          TEMPERATURE:
              NODE_RETIMER_X: 43
              NODE_OAM_X_IBC: 24
              ...
      BASEBOARD:
          TEMPERATURE:
              UBB_FPGA: 78
              UBB_FRONT: 55
              ...
      ECC:
          TOTAL_CORRECTABLE_COUNT: 0
          TOTAL_UNCORRECTABLE_COUNT: 0
          ...
      ECC_BLOCKS:
          UMC:
              CORRECTABLE_COUNT: 0
              UNCORRECTABLE_COUNT: 0
          ...
      FAN:
          SPEED: N/A
          MAX: N/A
          ...
      VOLTAGE_CURVE:
          POINT_0_FREQUENCY: N/A
          POINT_0_VOLTAGE: N/A
          ...
      OVERDRIVE: N/A
      MEM_OVERDRIVE: N/A
      PERF_LEVEL: AMDSMI_DEV_PERF_LEVEL_AUTO
      XGMI_ERR: N/A
      VOLTAGE:
          VDDBOARD: N/A
      ENERGY:
          TOTAL_ENERGY_CONSUMPTION: 14292727.274 J
      MEM_USAGE:
          TOTAL_VRAM: 196592 MB
          USED_VRAM: 283 MB
          ...
      THROTTLE:
          ACCUMULATION_COUNTER: 100936627
          PROCHOT_ACCUMULATED: 0
          ...
  ```

### Changed

- **Changed struct amdsmi_topology_nearest_t member processor_list**.  
  - Member size changed, processor_list[AMDSMI_MAX_DEVICES * AMDSMI_MAX_NUM_XCP]

- **Changed `amd-smi reset --profile` behavior so that it would not also reset the performance level**.  
  - These settings are completely independent now so there is no longer any need to reset them together. Therefore the reset behavior for performance level has been removed from resetting the profile. Users can still reset the performance level as they normally would using `amd-smi reset --perf-determinism`.  

- **Setting power cap is now available in Linux Guest**.  
  - Users can now use `amd-smi set --power-cap` as usual but now in Linux Guest systems.

- **Changed `amd-smi static --vbios` to `amd-smi static --ifwi`**.  
  - VBIOS naming is replaced with IFWI (Integrated Firmware Image) for improved clarity and consistency.
  - Mi300+ series devices now use a new version format with enhanced build information.
  - Legacy command `amd-smi static --vbios` remains functional for backward compatibility, but displays updated IFWI heading.
  - The Python, C & Rust API for `amdsmi_get_gpu_vbios_version()` will now have a new field called `boot_firmware` which will return the legacy vbios version number which is also known as the Unified BootLoader Version (UBL version)

  **Legacy format (Non IFWI systems):**

  ```shell
  $ amd-smi static --ifwi
  GPU: 0
      IFWI:
          NAME: XXXXXXXXXXXXXXXXXX
          BUILD_DATE: 2020/10/29 13:30
          PART_NUMBER: 113-XXXXXXXX-111
          VERSION: 000.000.000.000.000000 (Legacy format)
  ...
  ```

  **New format (Mi300+ series and IFWI systems):**

  ```shell
  $ amd-smi static --ifwi
  GPU: 0
      IFWI:
          NAME: XXXXXXXXXXXXXXXXXX
          BUILD_DATE: 2020/10/29 13:30
          PART_NUMBER: 113-XXXXXXXX-111
          VERSION: 00111111 (New format)
  ...
  ```

### Removed

- N/A

### Optimized

- **Optimized the way `amd-smi process` validates which processes are running on a GPU**.  

- **Changed sourcing of BDF to from drm to kfd**.  
  - Non sudo privliged users were unable to see the BDF due to logical errors.

### Resolved Issues

- **Fixed CPER component not being redirected to output file issue when using `amd-smi ras --cper --folder <folder_name> --file <file_name> --follow`**.  
  - Utilized the AMDSMILogger to redirect to output file when --file option is used

- **Fixed a CPER record count mismatch issue when using the `amd-smi ras --cper --file-limit`**.  
  - Fixed deletion calculation to use files_to_delete = len(folder_files) - file_limit for exact file count management

- **Fixed event monitoring segfaults causing RDC to crash**.  
  - Adds mutex locking around access to device event notification file pointer

- **Fixed an issue where using `amd-smi ras --folder <folder_name>` was forcing the created folder's name to be lowercase**.  
  - This fix also allows all string input options to be case insensitive.

- **Fixed certain output in `amd-smi monitor` when GPUs are partitioned**.  
  - Fixes amd-smi monitor such as: `amd-smi monitor -Vqt`, `amd-smi monitor -g 0 -Vqt -w 1`, `amd-smi monitor -Vqt --file /tmp/test1`, etc. Those such commands will now be able to display as normal in partitioned GPU scenarios.


### Upcoming Changes

- N/A

### Known Issues

- N/A

## amd_smi_lib for ROCm 7.0.2

### Added

- **Add bad_page_threshold_exceeded to `amd-smi static --ras`**.  
  - Added bad_page_threshold_exceeded field to `amd-smi static --ras`, which compares retired pages count against bad page threshold. This field displays True if retired pages exceed the threshold, False if within threshold, or N/A if threshold data is unavailable. Users should note that sudo is required to have the bad_page_threshold_exceeded field populated.

  ```shell
  $ sudo amd-smi static --ras -g 0
  GPU: 0
      RAS:
          EEPROM_VERSION: 0x30000
          BAD_PAGE_THRESHOLD: 128
          BAD_PAGE_THRESHOLD_EXCEEDED: False
          PARITY_SCHEMA: DISABLED
          SINGLE_BIT_SCHEMA: DISABLED
          DOUBLE_BIT_SCHEMA: DISABLED
          POISON_SCHEMA: ENABLED
  ...
  ```

### Changed

- N/A

### Removed

- **Removed gpuboard and baseboard temperatures enums in amdsmi Python Library**.  
  - AmdSmiTemperatureType had issues with referencing the right attribute, so we removed the following duplicate enums:
    - `AmdSmiTemperatureType.GPUBOARD_NODE_FIRST`
    - `AmdSmiTemperatureType.GPUBOARD_VR_FIRST`
    - `AmdSmiTemperatureType.BASEBOARD_FIRST`

### Optimized

- **Implemented reference counting to manage init and shutdown processes**.  
  - This allows multiple initializations and shutdowns of amdsmi.

### Resolved issues

- **Fixed `attribute error` in `amd-smi monitor` on Linux Guest systems where violations argument caused CLI to break**.  

- **Added KFD Fallback for process detection**.  
  - Some processes were not being detected by AMD SMI despite making use of KFD resources. This fix ensures that all KFD processes will be detected.

- **Multiple CPER issues were fixed**.  
  - Fixed issue where we were unable to query for additional CPERs after 20 were generated on a single device.
  - Fixed issue where RAS HBM CRC read was failing due to incorrect AFID value.
  - Fixed issue where RAS injections were not always producing related CPERs.

### Upcoming changes

- N/A

### Known issues

- N/A

## amd_smi_lib for ROCm 7.0.0

### Added

- **Added restarting (reloading) AMD GPU driver to both CLI and API calls**  
  - Refer to [<i><b>Separated driver reload from `amdsmi_set_gpu_memory_partition()` / `amdsmi_set_gpu_memory_partition_mode()` and CLI (`sudo amd-smi set -M <NPS mode>`)</b></i>](#separate-driver-reload-anchor) section for more details.

- **Added the Default command**.  
  - A default view has been added. The default view provides a snapshot of commonly requested information such as bdf, current partition mode, version information, and more. Users can access that information by simply typing `amd-smi` with no additional commands or arguments. Users may also obtain this information through laternate output formats such as json or csv by using the default command with the respective output format: `amd-smi default --json` or `amd-smi default --csv`.

```console
$ amd-smi
+------------------------------------------------------------------------------+
| AMD-SMI 26.0.0+eaa54ecc      amdgpu version: 6.12.12  ROCm version: 7.0.0    |
| Platform: Linux Baremetal                                                    |
|-------------------------------------+----------------------------------------|
| BDF                        GPU-Name | Mem-Uti   Temp   UEC       Power-Usage |
| GPU  HIP-ID  OAM-ID  Partition-Mode | GFX-Uti    Fan               Mem-Usage |
|=====================================+========================================|
| 0000:0c:00.0    AMD Instinct MI300X | 13 %     60 °C   0           734/750 W |
|   0       0       2        SPX/NPS1 | 98 %       N/A          4976/196592 MB |
|-------------------------------------+----------------------------------------|
| 0000:22:00.0    AMD Instinct MI300X | 10 %     60 °C   0           652/750 W |
|   1       1       1        SPX/NPS1 | 83 %       N/A          4976/196592 MB |
|-------------------------------------+----------------------------------------|
| 0000:38:00.0    AMD Instinct MI300X | 5 %      55 °C   0           376/750 W |
|   2       2       0        SPX/NPS1 | 34 %       N/A          4976/196592 MB |
|-------------------------------------+----------------------------------------|
| 0000:5c:00.0    AMD Instinct MI300X | 2 %      57 °C   0           234/750 W |
|   3       3       3        SPX/NPS1 | 12 %       N/A          4976/196592 MB |
|-------------------------------------+----------------------------------------|
| 0000:9f:00.0    AMD Instinct MI300X | 1 %      57 °C   0           219/750 W |
|   4       4       7        SPX/NPS1 | 11 %       N/A          4976/196592 MB |
|-------------------------------------+----------------------------------------|
| 0000:af:00.0    AMD Instinct MI300X | 3 %      61 °C   0           295/750 W |
|   5       5       5        SPX/NPS1 | 23 %       N/A          4976/196592 MB |
|-------------------------------------+----------------------------------------|
| 0000:bf:00.0    AMD Instinct MI300X | 5 %      58 °C   0           367/750 W |
|   6       6       4        SPX/NPS1 | 36 %       N/A          4976/196592 MB |
|-------------------------------------+----------------------------------------|
| 0000:df:00.0    AMD Instinct MI300X | 6 %      62 °C   0           434/750 W |
|   7       7       6        SPX/NPS1 | 47 %       N/A          4976/196592 MB |
+-------------------------------------+----------------------------------------+
+------------------------------------------------------------------------------+
| Processes:                                                                   |
|  GPU        PID  Process Name          GTT_MEM  VRAM_MEM  MEM_USAGE     CU % |
|==============================================================================|
|    0    2427396  rvs                    2.0 MB    2.0 GB     2.5 GB    0.0 % |
|    1    2427396  rvs                    2.0 MB    2.2 GB     2.6 GB    0.0 % |
|    2    2427396  rvs                    2.0 MB    2.3 GB     2.7 GB    0.0 % |
|    3    2427396  rvs                    2.0 MB    2.3 GB     2.7 GB    0.0 % |
|    4    2427396  rvs                    2.0 MB    2.1 GB     2.5 GB    0.0 % |
|    5    2427396  rvs                    2.0 MB    2.0 GB     2.2 GB    0.0 % |
|    6    2427396  rvs                    2.0 MB    2.1 GB     2.4 GB    0.0 % |
|    7    2427396  rvs                    2.0 MB    2.1 GB     2.5 GB    0.0 % |
+------------------------------------------------------------------------------+
```

- **Added support for GPU metrics 1.8**.  
  - Added new fields for `amdsmi_gpu_xcp_metrics_t` including:  
    - Adding the following metrics to allow new calculations for violation status:
    - Per XCP metrics `gfx_below_host_limit_ppt_acc[XCP][MAX_XCC]` - GFX Clock Host limit Package Power Tracking violation counts
    - Per XCP metrics `gfx_below_host_limit_thm_acc[XCP][MAX_XCC]` - GFX Clock Host limit Thermal (TVIOL) violation counts
    - Per XCP metrics `gfx_low_utilization_acc[XCP][MAX_XCC]` - violation counts for how did low utilization caused the GPU to be below application clocks.
    - Per XCP metrics `gfx_below_host_limit_total_acc[XCP][MAX_XCC]`- violation counts for how long GPU was held below application clocks any limiter (see above new violation metrics).
  - Increasing available JPEG engines to 40.  
  Current ASICs may not support all 40. These will be indicated as `UINT16_MAX` or `N/A` in CLI.

- **Added bad page threshold count**.  
  - Added `amdsmi_get_gpu_bad_page_threshold` to Python API and CLI; root/sudo permissions required to display the count.

- **Updated `amdsmi_get_gpu_asic_info` in `amdsmi.h`**.  
  - Added `subsystem_id` structure member.

- **Added cpu model name for RDC**.  
  - Added new C and Python API `amdsmi_get_cpu_model_name`
  - Not sourced from esmi library.

- **Added `amdsmi_get_cpu_affinity_with_scope()`**.  

- **Added `socket power` to `amdsmi_get_power_info`**  
  - Previously the C API had the value in the `amdsmi_power_info` structure, but was unused
  - Now we populate the value in both C & Python APIs
  - The value is representative of the socket's power agnostic of the the GPU version.

### Changed

<a name="separate-driver-reload-anchor"></a>
- **Separated driver reload from `amdsmi_set_gpu_memory_partition()` / `amdsmi_set_gpu_memory_partition_mode()` and CLI (`sudo amd-smi set -M <NPS mode>`)**  
  - Providing new API (`amdsmi_gpu_driver_reload()`) and CLI (`sudo amd-smi reset -r` or `sudo amd-smi reset --reload-driver`) once user is ready to reload driver. We understand
  the automatic reload could be at an inconvenient time. This is why we now provide this
  functionality in separate API/CLI commands to use when the time is right.
  - It is important to understand, the memory (NPS) partition change requires:
    1) Memory partition change request (`amdsmi_set_gpu_memory_partition()` / `amdsmi_set_gpu_memory_partition_mode()`) or CLI (`sudo amd-smi set -M <NPS mode>`)
    2) Driver reload (`amdsmi_gpu_driver_reload()` / `sudo amd-smi reset -r` or `sudo amd-smi reset --reload-driver`) \[\*\]
  ***Driver reload requires all GPU activity on all devices to be stopped.***

- **Modified `amd-smi` CLI `monitor` and `metric` for violations**.  
  - Disabled `amd-smi monitor --violation` on guests.  
  - Modified `amd-smi metric -T/--throttle` to alias to `amd-smi metric -v/--violation`.

- **Updated `amdsmi_get_clock_info` in `amdsmi_interface.py`**.  
  - The `clk_deep_sleep` field now returns the sleep integer value.  

- **The `amd-smi topology` command has been enabled for Guest environments**.  
  - `amd-smi topology` is now available in Guest environments. This includes full functionality so users can use the command just as they would in Bare Metal environments.

- **Expanded Violation Status tracking for GPU metrics 1.8**.  
  - The driver will no longer be supporting existing single-value GFX Clk Below Host Limit fields (`acc_gfx_clk_below_host_limit`, `per_gfx_clk_below_host_limit`, `active_gfx_clk_below_host_limit`), they are now changed in favor of new per-XCP/XCC arrays.
  - Added new fields to `amdsmi_violation_status_t` and related interfaces for enhanced violation breakdown:
    - Per-XCP/XCC accumulators and status for:
      - GFX Clock Below Host Limit (Power, Thermal, and Total)
      - Low Utilization
    - Added 2D arrays to track per-XCP/XCC accumulators, percentage, and active status:
      - `acc_gfx_clk_below_host_limit_pwr`, `acc_gfx_clk_below_host_limit_thm`, `acc_gfx_clk_below_host_limit_total`
      - `per_gfx_clk_below_host_limit_pwr`, `per_gfx_clk_below_host_limit_thm`, `per_gfx_clk_below_host_limit_total`
      - `active_gfx_clk_below_host_limit_pwr`, `active_gfx_clk_below_host_limit_thm`, `active_gfx_clk_below_host_limit_total`
      - `acc_low_utilization`, `per_low_utilization`, `active_low_utilization`
  - Python API and CLI now report these expanded fields.
  - Example outputs:

    ```console
    $ amd-smi monitor -V
    GPU  XCP  PVIOL  TVIOL  TVIOL_ACTIVE  PHOT_TVIOL  VR_TVIOL  HBM_TVIOL  GFX_CLKVIOL                                              GFXCLK_PVIOL                                              GFXCLK_TVIOL                                          GFXCLK_TOTALVIOL                                              LOW_UTILVIOL
      0    0    0 %    0 %         False         0 %       0 %        0 %          N/A                  [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]                  [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]  [100 %, 100 %, 100 %, 100 %, 100 %, 100 %, 100 %, 100 %]  [100 %, 100 %, 100 %, 100 %, 100 %, 100 %, 100 %, 100 %]
      1    0    0 %    0 %         False         0 %       0 %        0 %          N/A                  [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]                  [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]  [100 %, 100 %, 100 %, 100 %, 100 %, 100 %, 100 %, 100 %]  [100 %, 100 %, 100 %, 100 %, 100 %, 100 %, 100 %, 100 %]
      ...
    ```

    ```console
    $ sudo amd-smi set -C DPX > /dev/null

    $ amd-smi monitor -V
    GPU  XCP  PVIOL  TVIOL  TVIOL_ACTIVE  PHOT_TVIOL  VR_TVIOL  HBM_TVIOL  GFX_CLKVIOL                                              GFXCLK_PVIOL                                              GFXCLK_TVIOL                                          GFXCLK_TOTALVIOL                                              LOW_UTILVIOL
      0    0    0 %    0 %         False         0 %       0 %        0 %          N/A                  [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]                  [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]          [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]          [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]
      0    1    N/A    N/A           N/A         N/A       N/A        N/A          N/A                  [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]                  [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]          [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]          [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]
      1    1    N/A    N/A           N/A         N/A       N/A        N/A          N/A                                                       N/A                                                       N/A                                                       N/A                                                       N/A
      2    0    0 %    0 %         False         0 %       0 %        0 %          N/A                  [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]                  [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]          [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]          [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]
      2    1    N/A    N/A           N/A         N/A       N/A        N/A          N/A                  [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]                  [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]          [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]          [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]
    ...
    ```

    ```console
    $ amd-smi metric -v -g 0
    GPU: 0
        THROTTLE:
            ACCUMULATION_COUNTER: 8213780
            PROCHOT_ACCUMULATED: 0
            PPT_ACCUMULATED: 2
            SOCKET_THERMAL_ACCUMULATED: 0
            VR_THERMAL_ACCUMULATED: 0
            HBM_THERMAL_ACCUMULATED: 0
            GFX_CLK_BELOW_HOST_LIMIT_ACCUMULATED: N/A
            GFX_CLK_BELOW_HOST_LIMIT_POWER_ACCUMULATED:
                XCP_0: [0, 0, 0, 0, N/A, N/A, N/A, N/A]
                XCP_1: [0, 0, 0, 0, N/A, N/A, N/A, N/A]
            GFX_CLK_BELOW_HOST_LIMIT_THERMAL_ACCUMULATED:
                XCP_0: [0, 0, 0, 0, N/A, N/A, N/A, N/A]
                XCP_1: [0, 0, 0, 0, N/A, N/A, N/A, N/A]
            TOTAL_GFX_CLK_BELOW_HOST_LIMIT_ACCUMULATED:
                XCP_0: [8213744, 8213743, 8213742, 8213743, N/A, N/A, N/A, N/A]
                XCP_1: [8213744, 8213743, 8213744, 8213744, N/A, N/A, N/A, N/A]
            LOW_UTILIZATION_ACCUMULATED:
                XCP_0: [8213744, 8213743, 8213742, 8213743, N/A, N/A, N/A, N/A]
                XCP_1: [8213744, 8213743, 8213744, 8213744, N/A, N/A, N/A, N/A]
            PROCHOT_VIOLATION_STATUS: NOT ACTIVE
            PPT_VIOLATION_STATUS: NOT ACTIVE
            SOCKET_THERMAL_VIOLATION_STATUS: NOT ACTIVE
            VR_THERMAL_VIOLATION_STATUS: NOT ACTIVE
            HBM_THERMAL_VIOLATION_STATUS: NOT ACTIVE
            GFX_CLK_BELOW_HOST_LIMIT_VIOLATION_STATUS: N/A
            GFX_CLK_BELOW_HOST_LIMIT_POWER_VIOLATION_STATUS:
                XCP_0: [NOT ACTIVE, NOT ACTIVE, NOT ACTIVE, NOT ACTIVE, N/A, N/A, N/A, N/A]
                XCP_1: [NOT ACTIVE, NOT ACTIVE, NOT ACTIVE, NOT ACTIVE, N/A, N/A, N/A, N/A]
            GFX_CLK_BELOW_HOST_LIMIT_THERMAL_VIOLATION_STATUS:
                XCP_0: [NOT ACTIVE, NOT ACTIVE, NOT ACTIVE, NOT ACTIVE, N/A, N/A, N/A, N/A]
                XCP_1: [NOT ACTIVE, NOT ACTIVE, NOT ACTIVE, NOT ACTIVE, N/A, N/A, N/A, N/A]
            TOTAL_GFX_CLK_BELOW_HOST_LIMIT_VIOLATION_STATUS:
                XCP_0: [ACTIVE, ACTIVE, ACTIVE, ACTIVE, N/A, N/A, N/A, N/A]
                XCP_1: [ACTIVE, ACTIVE, ACTIVE, ACTIVE, N/A, N/A, N/A, N/A]
            LOW_UTILIZATION_VIOLATION_STATUS:
                XCP_0: [ACTIVE, ACTIVE, ACTIVE, ACTIVE, N/A, N/A, N/A, N/A]
                XCP_1: [ACTIVE, ACTIVE, ACTIVE, ACTIVE, N/A, N/A, N/A, N/A]
            PROCHOT_VIOLATION_ACTIVITY: 0 %
            PPT_VIOLATION_ACTIVITY: 0 %
            SOCKET_THERMAL_VIOLATION_ACTIVITY: 0 %
            VR_THERMAL_VIOLATION_ACTIVITY: 0 %
            HBM_THERMAL_VIOLATION_ACTIVITY: 0 %
            GFX_CLK_BELOW_HOST_LIMIT_VIOLATION_ACTIVITY: N/A
            GFX_CLK_BELOW_HOST_LIMIT_POWER_VIOLATION_ACTIVITY:
                XCP_0: [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]
                XCP_1: [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]
            GFX_CLK_BELOW_HOST_LIMIT_THERMAL_VIOLATION_ACTIVITY:
                XCP_0: [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]
                XCP_1: [0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A]
            TOTAL_GFX_CLK_BELOW_HOST_LIMIT_VIOLATION_ACTIVITY:
                XCP_0: [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]
                XCP_1: [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]
            LOW_UTILIZATION_VIOLATION_ACTIVITY:
                XCP_0: [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]
                XCP_1: [100 %, 100 %, 100 %, 100 %, N/A, N/A, N/A, N/A]
    ```

- **The char arrays in the following structures have been changed**.  
  - `amdsmi_vbios_info_t` member `build_date` changed from `AMDSMI_MAX_DATE_LENGTH` to `AMDSMI_MAX_STRING_LENGTH`.
  - `amdsmi_dpm_policy_entry_t` member `policy_description` changed from `AMDSMI_MAX_NAME` to `AMDSMI_MAX_STRING_LENGTH`.
  - `amdsmi_name_value_t` member `name` changed from `AMDSMI_MAX_NAME` to `AMDSMI_MAX_STRING_LENGTH`.

- **Added new event notification types to `amdsmi_evt_notification_type_t`**.  
  The following values were added to the `amdsmi_evt_notification_type_t` enum:
  - `AMDSMI_EVT_NOTIF_EVENT_MIGRATE_START`
  - `AMDSMI_EVT_NOTIF_EVENT_MIGRATE_END`
  - `AMDSMI_EVT_NOTIF_EVENT_PAGE_FAULT_START`
  - `AMDSMI_EVT_NOTIF_EVENT_PAGE_FAULT_END`
  - `AMDSMI_EVT_NOTIF_EVENT_QUEUE_EVICTION`
  - `AMDSMI_EVT_NOTIF_EVENT_QUEUE_RESTORE`
  - `AMDSMI_EVT_NOTIF_EVENT_UNMAP_FROM_GPU`
  - `AMDSMI_EVT_NOTIF_PROCESS_START`
  - `AMDSMI_EVT_NOTIF_PROCESS_END`

- **Added Power Cap to `amd-smi monitor`**.  
  - `amd-smi monitor -p` will display the power cap along with power.

    ```console
    $ amd-smi monitor -p
    GPU  POWER  PWR_CAP
      0  148 W    750 W
      1  156 W    750 W
      2  153 W    750 W
    ...
    ```

- **Updated `amdsmi_bdf_t` in `amdsmi.h`**.  
  - The `amdsmi_bdf_t` union was changed to have an identical unnamed struct for backwards compatibility

- **Updated `amdsmi_get_temp_metric` and `amdsmi_temperature_type_t` with new values**.  
  - New values have added to `amdsmi_temperature_type_t` representing various baseboard and gpuboard temperature measures.
  - `amdsmi_get_temp_metric` API has also been updated to be able to take in and return the respective values for the new
  temperature types.

- **Modified error responses for `amd-smi set` and `amd-smi reset` to display AMD SMI's error codes**.  
  - Error responses now include the explicit AMDSMI status code in square brackets (e.g., `[AMDSMI_STATUS_NOT_SUPPORTED]`) before the error message for each GPU, providing clear context on the type of failure.
  - This change is intended to help provide more context on the failure and why the failure occurred.
  - **How to interpret error codes:**  
    - If you see `[AMDSMI_STATUS_NOT_SUPPORTED]`, the device does not support the requested operation and no action is taken.
    - If you see `[AMDSMI_STATUS_INVAL]`, user provided invalid parameters.
    - If you see `[AMDSMI_STATUS_BUSY]`, device is busy and cannot process this request
    - For other codes, refer to our documentation for details. [Link to `enum amdsmi_status_t` documentation.](https://rocm.docs.amd.com/projects/amdsmi/en/amd-staging/doxygen/docBin/html/amdsmi_8h.html#ab05c37a8d1e512898eef2d25fb9fe06b)
  - Example scenarios:
    - **Navi System:**  
      Attempting to change partitions on a Navi system will result in a "not supported" response, since Navi does not support partitions.

      ```console
      $ sudo amd-smi set -M NPS2

                  ******WARNING******

                  After changing memory (NPS) partition modes, users MUST restart
                  (reload) the AMD GPU driver. This command NO LONGER AUTOMATICALLY
                  reloads the driver, see `amd-smi reset -h` and
                  `sudo amd-smi reset -r` for more information.

                  This change is intended to allow users the ability to control when is
                  the best time to restart the AMD GPU driver, as it may not be desired
                  to restart the AMD GPU driver immediately after changing the
                  memory (NPS) partition mode.

                  Please use `sudo amd-smi reset -r` AFTER successfully
                  changing the memory (NPS) partition mode. A successful driver reload
                  is REQUIRED in order to complete updating ALL GPUs in the hive to
                  the requested partition mode.

                  ******REMINDER******
                  In order to reload the AMD GPU driver, users MUST quit all GPU
                  workloads across all devices.

      Do you accept these terms? [Y/N] y

      GPU: 0
          MEMORY_PARTITION: [AMDSMI_STATUS_NOT_SUPPORTED] Unable to set memory partition to NPS2

      GPU: 1
          MEMORY_PARTITION: [AMDSMI_STATUS_NOT_SUPPORTED] Unable to set memory partition to NPS2
      ```

    - **MI3x System in DPX Mode:**  
      Restricting the power limit on a MI3x device in DPX mode will show "not supported" for logical devices, as only the primary device can accept the change.

      ```console
      $ sudo amd-smi set --power-cap 700
      GPU: 0
          POWERCAP: Successfully set power cap to 700W

      GPU: 1
          POWERCAP: [AMDSMI_STATUS_NOT_SUPPORTED] Unable to set power cap to 700W

      GPU: 2
          POWERCAP: Successfully set power cap to 700W

      GPU: 3
          POWERCAP: [AMDSMI_STATUS_NOT_SUPPORTED] Unable to set power cap to 700W
      ...
      ```

- **Modified the enum `AMDSMI_STATUS_MORE_DATA` in `amdsmi_status_t`**.  
  - The `AMDSMI_STATUS_MORE_DATA` value changed from 57 to 39.
  - Change was done to align all drivers on a common value.

### Removed

- **Removed unnecessary API, `amdsmi_free_name_value_pairs(),` from amdsmi.h**.  
  - This API is only used internally to free up memory from the python interface and does not need to be
  exposed to the User.

- **Removed unused definitions**  
  - `AMDSMI_MAX_NAME`
  - `AMDSMI_256_LENGTH`
  - `AMDSMI_MAX_DATE_LENGTH`
  - `MAX_AMDSMI_NAME_LENGTH`
  - `AMDSMI_LIB_VERSION_YEAR`
  - `AMDSMI_DEFAULT_VARIANT`
  - `AMDSMI_MAX_NUM_POWER_PROFILES`
  - `AMDSMI_MAX_DRIVER_VERSION_LENGTH`

- **Removed unused member `year` in struct `amdsmi_version_t`**  

- **Removed `amdsmi_io_link_type_t` and replaced with `amdsmi_link_type_t`**.  
  - `amdsmi_io_link_type_t` is no longer needed as `amdsmi_link_type_t` is sufficient.
  - Mapping from `amdsmi_io_link_type_t` to `amdsmi_link_type_t` is as follows:

  ```console
  AMDSMI_IOLINK_TYPE_UNDEFINED  == AMDSMI_LINK_TYPE_INTERNAL
  AMDSMI_IOLINK_TYPE_PCIEXPRESS == AMDSMI_LINK_TYPE_PCIE
  AMDSMI_IOLINK_TYPE_XGMI       == AMDSMI_LINK_TYPE_XGMI
  ```

  - `amdsmi_link_type_t` enum has changed, primarily the ordering of the PCI and XGMI types:

  ```C++
  typedef enum {
      AMDSMI_LINK_TYPE_INTERNAL = 0,
      AMDSMI_LINK_TYPE_PCIE = 1,
      AMDSMI_LINK_TYPE_XGMI = 2,
      AMDSMI_LINK_TYPE_NOT_APPLICABLE = 3,
      AMDSMI_LINK_TYPE_UNKNOWN = 4
  } amdsmi_link_type_t;
  ```

  - Please note that this change will also affect `amdsmi_link_metrics_t`, where the link_type field changes from `amdsmi_io_link_type_t` to `amdsmi_link_type_t`:

  ```C++
  typedef struct {
    uint32_t num_links;     //!< number of links
    struct _links {
        amdsmi_bdf_t bdf;               //!< bdf of the destination gpu
        uint32_t bit_rate;              //!< current link speed in Gb/s
        uint32_t max_bandwidth;         //!< max bandwidth of the link in Gb/s
        amdsmi_link_type_t link_type;   //!< type of the link
        uint64_t read;                  //!< total data received for each link in KB
        uint64_t write;                 //!< total data transferred for each link in KB
        uint64_t reserved[2];
    } links[AMDSMI_MAX_NUM_XGMI_PHYSICAL_LINK];
    uint64_t reserved[7];
  } amdsmi_link_metrics_t;
  ```

- **Removed `amdsmi_get_power_info_v2()`**.  
  - The amdsmi_get_power_info() has been unified and the v2 function is no longer needed/used.

- **Removed `AMDSMI_EVT_NOTIF_RING_HANG` event notification type in `amdsmi_evt_notification_type_t`**.  

- **The `amdsmi_get_gpu_vram_info` now provides vendor names as a string**.  
  - `amdsmi_vram_vendor_type_t` enum structure was removed
  - `amdsmi_vram_info_t` member named `amdsmi_vram_vendor_type_t` was changed to a character string
  - `amdsmi_get_gpu_vram_info` now no longer requires decoding the vendor name as an enum

- **Removed backwards compatibility `amdsmi_get_gpu_metrics_info()`'s `jpeg_activity` or `vcn_activity` fields: use `xcp_stats.jpeg_busy` or `xcp_stats.vcn_busy`**  
  - Backwards compatibility is removed for `jpeg_activity` and `vcn_activity` fields, if the `jpeg_busy` or `vcn_busy` field is available.
    - *Reasons for this change:*
      - Providing both `vcn_activity`/`jpeg_activity` and XCP (partition) stats `vcn_busy`/`jpeg_busy` caused confusion for users about which field to use. By removing backward compatibility, it is easier to identify the relevant field.
      - The `jpeg_busy` field increased in size (for supported ASICs), making backward compatibility unable to fully copy the structure into `jpeg_activity`.

    See below for comparison of updated CLI outputs:

    Original output:

    ```console
    $ amd-smi metric --usage
    GPU: 0
        USAGE:
            GFX_ACTIVITY: 0 %
            UMC_ACTIVITY: 0 %
            MM_ACTIVITY: N/A
            VCN_ACTIVITY: [0 %, N/A, N/A, N/A]
            JPEG_ACTIVITY: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            GFX_BUSY_INST:
                XCP_0: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_1: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_2: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_3: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_4: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_5: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_6: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_7: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            JPEG_BUSY:
                XCP_0: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_1: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_2: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_3: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_4: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_5: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_6: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_7: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            VCN_BUSY:
                XCP_0: [0 %, N/A, N/A, N/A]
                XCP_1: [0 %, N/A, N/A, N/A]
                XCP_2: [0 %, N/A, N/A, N/A]
                XCP_3: [0 %, N/A, N/A, N/A]
                XCP_4: [0 %, N/A, N/A, N/A]
                XCP_5: [0 %, N/A, N/A, N/A]
                XCP_6: [0 %, N/A, N/A, N/A]
                XCP_7: [0 %, N/A, N/A, N/A]
    ```

    New output:

    ```console
    $ amd-smi metric --usage
    GPU: 0
        USAGE:
            GFX_ACTIVITY: 0 %
            UMC_ACTIVITY: 0 %
            MM_ACTIVITY: N/A
            VCN_ACTIVITY: [N/A, N/A, N/A, N/A]
            JPEG_ACTIVITY: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            GFX_BUSY_INST:
                XCP_0: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_1: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_2: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_3: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_4: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_5: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_6: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_7: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            JPEG_BUSY:
                XCP_0: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_1: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_2: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_3: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_4: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_5: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_6: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
                XCP_7: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            VCN_BUSY:
                XCP_0: [0 %, N/A, N/A, N/A]
                XCP_1: [0 %, N/A, N/A, N/A]
                XCP_2: [0 %, N/A, N/A, N/A]
                XCP_3: [0 %, N/A, N/A, N/A]
                XCP_4: [0 %, N/A, N/A, N/A]
                XCP_5: [0 %, N/A, N/A, N/A]
                XCP_6: [0 %, N/A, N/A, N/A]
                XCP_7: [0 %, N/A, N/A, N/A]
    ```

### Optimized

- **Reduced amd-smi's CLI's API calls needed to be called before reading or (re)setting GPU features**.  
  - Now when users call any amd-smi CLI command, we have reduced the APIs needed to be called. Previously,
  when a user would read a GPU's status, (for example) we would poll for other information helpful for our sets/reset
  CLI calls. This change will increase overall run-time performance of the CLI tool.

- **Removed partition information from the default `amd-smi static` CLI command**.  
  - Users can still retrieve the same data by calling `amd-smi`, `amd-smi static -p`, or `amd-smi partition -c -m`/`sudo amd-smi partition -a`.  
   ***Reason for this change***:  
      Reading current_compute_partition may momentarily wake the GPU up. This is due to reading XCD registers, which is expected behavior. Changing partitions is not a trivial operation, `current_compute_partition` SYSFS controls this action.

- **Optimized CLI command `amd-smi topology` in partition mode**.  
  - Reduced the number of `amdsmi_topo_get_p2p_status` API calls to one fourth.  

### Resolved issues

- **Removed duplicated GPU IDs when receiving events using the `amd-smi event` command**.  

- **Fixed `amd-smi monitor` decoder utilization (`DEC%`) not showing up on MI3x ASICs**.  

- **Removed additional output after valid json for `amd-smi partition --json`**.  
  - Previously, when calling `amd-smi partition --json`, there was additional output after the valid json.
  - This has been fixed to only show valid json output.

### Upcoming changes

- **`amd-smi metric` will also display gpuboard and baseboard temperatures**.  
  - This change is meant to follow the API change to amdsmi_get_temp_metric. If these measures are not available due
  to hardware incompatibility, then they will simply not be displayed in the results when using the metric command.

### Known issues

- `amd-smi monitor` does not work on guest systems

  ```shell
  $ amd-smi monitor
  AttributeError: 'Namespace' object has no attribute 'violation'
  ```

## amd_smi_lib for ROCm 6.4.2

### Added

- **Added Compute Unit Occupancy information per process**  
  Measuring compute units are the best way currently to determine gfx usage on a per process basis  
  - Added `cu_occupancy` field to `amdsmi_proc_info_t` structure in C & Python APIs, in minor version update  
  - Added `CU_OCCUPANCY` to `amd-smi process` output.
  - Added `CU%` to `amd-smi monitor -q`

- **Added support to get GPU Board voltage**.  

  ```console
      $ amd-smi metric --voltage
          GPU: 0
              VOLTAGE:
                  VDDBOARD: 52536 mV
                  ...
  ```

- **Added new firmware PLDM_BUNDLE**.  
  - `amd-smi firmware` can now show the PLDM Bundle on supported systems.  

- **Added `amd-smi ras --afid --cper-file <file_path>` to decode CPER records**  
  - Python and C have added the `amdsmi_get_afids_from_cper()` to decode

### Changed

- **Padded `asic_serial` in `amdsmi_get_asic_info` with 0s**.  

- **Renamed fields `COMPUTE_PARTITION` to `ACCELERATOR_PARTITION` in CLI call `amd-smi --partition`**.  
  - We are changing the field named `COMPUTE_PARTITION` to `ACCELERATOR_PARTITION`.  
  - API and associated struct naming will remain the same  
  - Reason(s) for this change:  
    - Align with host AMD SMI's `static --partition` field naming  
    - Align with naming seen in `amd-smi partition`  

  *Previous Output:*  

  ```console
  $ amd-smi static --partition
    GPU: 0
        PARTITION:
            COMPUTE_PARTITION: SPX
            MEMORY_PARTITION: NPS1
            PARTITION_ID: 0
  ```

  *New Output:*  

  ```console
  $ amd-smi static --partition
    GPU: 0
        PARTITION:
            ACCELERATOR_PARTITION: SPX
            MEMORY_PARTITION: NPS1
            PARTITION_ID: 0
  ```

### Removed

- N/A

### Optimized

- N/A

### Resolved issues

- **Corrected VRAM memory calculation in `amdsmi_get_gpu_process_list`**.  
  - Previously, the VRAM memory usage reported by `amdsmi_get_gpu_process_list` was inaccurate and calculated using KB vs KiB.

### Upcoming changes

- N/A

### Known issues

- N/A

## amd_smi_lib for ROCm 6.4.1

### Added

- **Added dumping CPER entries from RAS tool `amdsmi_get_gpu_cper_entries()` to Python & C APIs**.  
  - CPER entries consist of `amdsmi_cper_hdr_t`

    ```C
    typedef struct {
        char                   signature[4];       /* "CPER" */
        uint16_t               revision;
        uint32_t               signature_end;      /* 0xFFFFFFFF */
        uint16_t               sec_cnt;
        amdsmi_cper_sev_t      error_severity;
        //valid_bits_t          valid_bits;
        //uint32_t              valid_mask;
        amdsmi_cper_valid_bits_t cper_valid_bits;
        uint32_t                record_length;     /* Total size of CPER Entry */
        amdsmi_cper_timestamp_t timestamp;
        char                    platform_id[16];
        amdsmi_cper_guid_t      partition_id;      /* Reserved */
        char                  creator_id[16];
        amdsmi_cper_guid_t    notify_type;         /* CMC, MCE, can use amdsmi_cper_notifiy_type_t to decode*/
        char                  record_id[8];        /* Unique CPER Entry ID */
        uint32_t              flags;               /* Reserved */
        uint64_t              persistence_info;    /* Reserved */
        uint8_t               reserved[12];        /* Reserved */
    } amdsmi_cper_hdr_t;
    ```

  - Dumping CPER entries is also enabled in the CLI interface via `sudo amd-smi ras --cper`

    ```console
    $ sudo amd-smi ras --cper
    Dumping CPER file header entries for GPU 0:
    "0": {
       "error_severity": "non_fatal_corrected",
       "notify_type": "CMC",
       "timestamp": "2025/04/08 18:23:44",
       "signature": "CPER",
       "revision": 256,
       "signature_end": "0xffffffff",
       "sec_cnt": 1,
       "record_length": 472,
       "platform_id": "0x1002:0x74A2",
       "creator_id": "amdgpu",
       "record_id": "5:1",
       "flags": 0,
       "persistence_info": 0
       }
    ```

- **Added `amdsmi_get_gpu_busy_percent` to the C API**.  
  - This function retrieves the GPU busy percentage from the `gpu_busy_percent` sysfs file.

### Changed

- **Modified VRAM display for `amd-smi monitor -v`**.  
  - Added free VRAM and VRAM percentage.

    ```console
    $ amd-smi monitor -v
    GPU  VRAM_USED   VRAM_FREE  VRAM_TOTAL    VRAM%
      0     174 MB    16011 MB    16185 MB   0.01 %
      1      78 MB      347 MB      425 MB   0.18 %
      ...
    ```

### Removed

- N/A

### Optimized

- **Improved load times for CLI commands when the GPU has multiple partitions**.  

### Resolved issues

- **Fixed partition enumeration - `amd-smi list -e`, `amdsmi_get_gpu_enumeration_info()`'s `amdsmi_enumeration_info_t` `drm_card` and `drm_render` fields**  
    Previously, partitions incorrectly reflected the primary node (1st GPU) and showed the DRM Render Minor as renderD128. Partition nodes mirrored renderD128's information, which was incorrect. See the "*Previous Outputs in CPX*" example below.

    Device enumeration was updated to correctly map DRM Render Minor paths. See the "*Corrected Outputs in CPX*" example below.

    These changes impact what information is readable/writable for the partition nodes.

    ***Example: Previous Outputs in CPX***  

    ```console
    $ amd-smi list -e                                                                    
    GPU: 0
        BDF: 0000:0c:00.0
        UUID: <Redacted>
        KFD_ID: 18421
        NODE_ID: 2
        PARTITION_ID: 0
        RENDER: renderD128
        CARD: card0
        HSA_ID: 2
        HIP_ID: 0
        HIP_UUID: <Redacted>

    GPU: 1
        BDF: 0000:0c:00.1
        UUID: <Redacted>
        KFD_ID: 48116
        NODE_ID: 3
        PARTITION_ID: 1
        RENDER: N/A
        CARD: N/A
        HSA_ID: 3
        HIP_ID: 1
        HIP_UUID: GPU-<Redacted>
    ...
    ```

    ```console
    $ amd-smi monitor
    GPU  POWER   GPU_T   MEM_T   GFX_CLK   GFX%   MEM%   ENC%   DEC%      VRAM_USAGE
      0  201 W   46 °C   42 °C  2107 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
      1  201 W   46 °C   42 °C  2107 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
      2  201 W   46 °C   42 °C  2107 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
      3  201 W   46 °C   42 °C  2107 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
      4  201 W   46 °C   42 °C  2107 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
      5  201 W   46 °C   42 °C  2107 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
      6  201 W   46 °C   42 °C  2107 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
      7  201 W   46 °C   42 °C  2107 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
      8  210 W   46 °C   42 °C  2104 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
    ...
    ```

    ***Example: Corrected outputs in CPX***  

    ```console
    $ amd-smi list -e
    GPU: 0
        BDF: 0000:0c:00.0
        UUID: <Redacted>
        KFD_ID: 18421
        NODE_ID: 2
        PARTITION_ID: 0
        RENDER: renderD128
        CARD: card0
        HSA_ID: 2
        HIP_ID: 0
        HIP_UUID: GPU-<Redacted>

    GPU: 1
        BDF: 0000:0c:00.1
        UUID: <Redacted>
        KFD_ID: 48116
        NODE_ID: 3
        PARTITION_ID: 1
        RENDER: renderD129
        CARD: card1
        HSA_ID: 3
        HIP_ID: 1
        HIP_UUID: GPU-<Redacted>
    ...
    ```

    ```console
    $ amd-smi monitor
    GPU  POWER   GPU_T   MEM_T   GFX_CLK   GFX%   MEM%   ENC%   DEC%      VRAM_USAGE
      0  202 W   46 °C   42 °C  2107 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
      1    N/A     N/A     N/A       N/A    N/A    N/A    N/A    N/A    0.5/ 24.0 GB
      2    N/A     N/A     N/A       N/A    N/A    N/A    N/A    N/A    0.5/ 24.0 GB
      3    N/A     N/A     N/A       N/A    N/A    N/A    N/A    N/A    0.5/ 24.0 GB
      4    N/A     N/A     N/A       N/A    N/A    N/A    N/A    N/A    0.5/ 24.0 GB
      5    N/A     N/A     N/A       N/A    N/A    N/A    N/A    N/A    0.5/ 24.0 GB
      6    N/A     N/A     N/A       N/A    N/A    N/A    N/A    N/A    0.5/ 24.0 GB
      7    N/A     N/A     N/A       N/A    N/A    N/A    N/A    N/A    0.5/ 24.0 GB
      8  210 W   46 °C   42 °C  2104 MHz    0 %    0 %    N/A    0 %    0.3/192.0 GB
    ...
    ```

### Upcoming changes

- N/A

### Known issues

- N/A

## amd_smi_lib for ROCm 6.4.0

### Added

- **Added enumeration mapping `amdsmi_get_gpu_enumeration_info()` to Python & C APIs**.  
  - Enumeration mapping consists of `amdsmi_enumeration_info_t`

    ```C
    typedef struct {
        uint32_t drm_render; // the render node under /sys/class/drm/renderD*
        uint32_t drm_card;   // the graphic card device under /sys/class/drm/card*
        uint32_t hsa_id;     // the HSA enumeration ID
        uint32_t hip_id;     // the HIP enumeration ID
        char hip_uuid[AMDSMI_MAX_STRING_LENGTH];  // the HIP unique identifier
    } amdsmi_enumeration_info_t;
    ```

  - The mapping is also enabled in the CLI interface via `amd-smi list -e`

    ```console
    $ amd-smi list -e
    GPU: 0
        BDF: 0000:23:00.0
        UUID: XXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
        KFD_ID: 45412
        NODE_ID: 1
        PARTITION_ID: 0
        RENDER: renderD128
        CARD: card0
        HSA_ID: 1
        HIP_ID: 0
        HIP_UUID: GPU-XXXXXXXXXXXXXXXX
    ```

- **Added dynamic virtualization mode detection**.  
  - Added new C and Python API `amdsmi_get_gpu_virtualization_mode`
  - Added new C and Python enum `amdsmi_virtualization_mode_t`

- **Added TVIOL_ACTIVE to `amd-smi monitor`**.  
  - Added temperature violation active or not status to `amd-smi monitor`. TVIOL_ACTIVE will be displayed as below:
    - True if active
    - False if not active
    - N/A if not supported.

  Example CLI output:

    ```console
    $ amd-smi monitor --viol
    GPU  PVIOL  TVIOL  TVIOL_ACTIVE  PHOT_TVIOL  VR_TVIOL  HBM_TVIOL
    0  100 %    1 %          True         0 %       0 %        0 %
    1  100 %    0 %         False         0 %       0 %        0 %
    2  100 %    0 %         False         0 %       0 %        0 %
    3  100 %    0 %         False         0 %       0 %        0 %
    4  100 %    0 %         False         0 %       0 %        0 %
    5  100 %    3 %          True         0 %       0 %        0 %
    6  100 %    0 %         False         0 %       0 %        0 %
    7  100 %    0 %         False         0 %       0 %        0 %
    ```

- **Added support for GPU metrics 1.7 to `amdsmi_get_gpu_metrics_info()`**.  
Updated `amdsmi_get_gpu_metrics_info()` and structure `amdsmi_gpu_metrics_t` to include new fields for XGMI Link Status, graphics clocks below host limit (per XCP), and VRAM max bandwidth:  
  - `uint64_t vram_max_bandwidth` - VRAM max bandwidth at max memory clock (GB/s)
  - `uint16_t xgmi_link_status[MAX_NUM_XGMI_LINKS]` - XGMI link statis, 1=Up 0=Down
  - `uint64_t gfx_below_host_limit_acc[MAX_NUM_XCC]` - graphics clocks below host limit (per XCP) accumulators. Used for graphic clk below host limit violation status.

- **Added new API `amdsmi_get_gpu_xgmi_link_status()` and CLI `amd-smi xgmi --link-status`**  

    New API is defined as:

    ```C
    typedef enum {
        AMDSMI_XGMI_LINK_DOWN,     //!< The XGMI Link is down
        AMDSMI_XGMI_LINK_UP,       //!< The XGMI Link is up
        AMDSMI_XGMI_LINK_DISABLE,  //!< The XGMI Link is disabled
    } amdsmi_xgmi_link_status_type_t;

    typedef struct {
        uint32_t total_links;     //!< The total links in the status array
        amdsmi_xgmi_link_status_type_t status[AMDSMI_MAX_NUM_XGMI_LINKS];
        uint64_t reserved[7];
    } amdsmi_xgmi_link_status_t;

    amdsmi_status_t amdsmi_get_gpu_xgmi_link_status(amdsmi_processor_handle processor_handle, amdsmi_xgmi_link_status_t *link_status)
    ```

    Example CLI output:

    ```console
    $ amd-smi xgmi --link-status

    XGMI LINK STATUS:
        bdf           link_status
    GPU0   0000:08:00.0  U  U  U  U  D  U  D  X
    GPU1   0000:44:00.0  U  U  U  U  D  U  D  X
    ...

    * U:Up D:Down X:Disabled
    ```

- **Added fclk and socclk info to `amd-smi metric -c/--clock`**.  
  - fclk and socclk information such as min and max clock have been added to the metric command, in line with all the other clocks.  

  ```shell
  $ amd-smi metric -c -g 1
  ...
          FCLK_0:
            CLK: 2301 MHz
            MIN_CLK: 601 MHz
            MAX_CLK: 2301 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: DISABLED
        SOCCLK_0:
            CLK: 1500 MHz
            MIN_CLK: 500 MHz
            MAX_CLK: 1500 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: DISABLED
  ```

- **Added new command `amd-smi set -c/--clock-level`**.  
  - This new command sets the performance level of the selected clock on the desired GPUs.
  - The command can accept a range of acceptable levels, but will not set the level when a level is beyond the number of frequency levels as show in `amd-smi static -C/--clock`.  

    ```console
    $ sudo amd-smi set -c sclk 5 6
    GPU: 0
        CLK_LEVEL: Successfully changed sclk perf level(s) to 5, 6

GPU: 1
    CLK_LEVEL: clock level(s) 5, 6 is/are greater than sclk frequency levels supported for device GPU ID: 1 BDF:0000:46:00.0
```

- **Added new command `amd-smi static -C/--clock`**.  
  - This new command displays the clock frequency performance levels for the selected GPUs and clocks.

    ```console
    $ amd-smi static --clock all -g 0
    GPU: 0
        CLOCK:
            SYS:
                CURRENT LEVEL: 2
                FREQUENCY_LEVELS:
                    0: 300 MHz
                    1: 904 MHz
                    2: 1165 MHz
                    3: 1360 MHz
                    4: 1440 MHz
                    5: 1544 MHz
                    6: 1627 MHz
                    7: 1720 MHz
                    8: 1800 MHz
            MEM:
                CURRENT LEVEL: 0
                FREQUENCY_LEVELS:
                    0: 167 MHz
            DF:
                CURRENT LEVEL: 0
                FREQUENCY_LEVELS:
                    0: 1400 MHz
            SOC:
                CURRENT LEVEL: 0
                FREQUENCY_LEVELS:
                    0: 302 MHz
            DCEF: N/A
            VCLK0: N/A
            VCLK1: N/A
            DCLK0: N/A
            DCLK1: N/A
    ```

### Changed

- **AMDSMI Library Version number to reflect changes in backwards compatibility**.  
  - Removed Year from AMDSMI Library version number.
  - Version changed from 25.2.0.0 (Year.Major.Minor.Patch) to 25.2.0 (Major.Minor.Patch)
  - Removed year in all version references

- **Removed initialization requirements for `amdsmi_get_lib_version()` and added `amdsmi_get_rocm_version()` to the python API & CLI**.  

- **Added `amdsmi_get_power_info_v2()` with `sensor_ind`**.  
  - Python API now accepts sensor_ind as an optional argument, does not impact previous usage

- **Deprecated enum `AMDSMI_NORMAL_STRING_LENGTH` in favor of `AMDSMI_MAX_STRING_LENGTH`**.  

- **Changed to use thread local mutex by default**.  
  - Most sysfs reads do not require cross-process level mutex, and writes to sysfs should be protected by the kernel already.
  - Users can still switch to the old behavior by setting the environment variable `AMDSMI_MUTEX_CROSS_PROCESS=1`.

- **Changed `amdsmi_vram_vendor_type_t` enum names impacting `amdsmi_vram_info_t` structure**.  
This also change impacts usage of the vram_vendor output of `amdsmi_get_gpu_vram_info()`

- **Changed `amdsmi_nps_caps_t` struct impacting `amdsmi_memory_partition_config_t`, `amdsmi_accelerator_partition_t`, `amdsmi_accelerator_partition_profile_config_t`**.  
Functions affected by struct change are:
  - `amdsmi_get_gpu_memory_partition_config()`
  - `amdsmi_get_gpu_accelerator_partition_profile()`
  - `amdsmi_get_gpu_accelerator_partition_profile_config()`

- **Corrected CLI CPU argument name**.  
  - `--cpu-pwr-svi-telemtry-rails` to `--cpu-pwr-svi-telemetry-rails`

- **Added amdgpu driver version and amd_hsmp driver version to `amd-smi version` command**.  
  - The `amd-smi version` command can now also display the amdgpu driver version using the `-g` flag.
  - The amd_hsmp driver version can also be displayed using the `-c` flag.
  - The new default for the `version` command is to display all the version information, including both amdgpu and amd_hsmp driver versions.

    ```console
    $ amd-smi version
    AMDSMI Tool: 24.7.1+b446d6c-dirty | AMDSMI Library version: 24.7.2.0 | ROCm version: N/A | amdgpu version: 6.10.10 | amd_hsmp version: 2.2

    $ amd-smi version -g
    AMDSMI Tool: 24.7.1+b446d6c-dirty | AMDSMI Library version: 24.7.2.0 | ROCm version: N/A | amdgpu version: 6.10.10

    $ amd-smi version -c
    AMDSMI Tool: 24.7.1+b446d6c-dirty | AMDSMI Library version: 24.7.2.0 | ROCm version: N/A | amd_hsmp version: 2.2
    ```

- **All `amd-smi set` and `amd-smi reset` options are now mutually exclusive**.  
  - Users can only use one set option at a time now.  

- **Python API for `amdsmi_get_energy_count()` will change the name for the `power` field to `energy_accumulator`**.  

- **Added violation status output for Graphics Clock Below Host Limit to our CLI: `amdsmi_get_violation_status()`, `amd-smi metric  --throttle`, and `amd-smi monitor --violation`**.  
  ***Only available for MI300+ ASICs.***  
  Users can retrieve violation status' through either our Python or C++ APIs.  
  Additionally, we have added capability to view these outputs conveniently through `amd-smi metric --throttle` and `amd-smi monitor --violation`.  
  Example outputs are listed below (below is for reference, output is subject to change):

    ```console
    $ amd-smi monitor --violation
    GPU  PVIOL  TVIOL  TVIOL_ACTIVE PHOT_TVIOL  VR_TVIOL  HBM_TVIOL  GFX_CLKVIOL
    0    0 %    0 %           False        0 %       0 %        0 %          0 %
    1    0 %    0 %           False        0 %       0 %        0 %          0 %
    ...
    ```

    ```console
    $ amd-smi metric --throttle
    GPU: 0
        THROTTLE:
            ACCUMULATION_COUNTER: 11240028
            PROCHOT_ACCUMULATED: 0
            PPT_ACCUMULATED: 0
            SOCKET_THERMAL_ACCUMULATED: 0
            VR_THERMAL_ACCUMULATED: 0
            HBM_THERMAL_ACCUMULATED: 0
            GFX_CLK_BELOW_HOST_LIMIT_ACCUMULATED: N/A
            PROCHOT_VIOLATION_STATUS: NOT ACTIVE
            PPT_VIOLATION_STATUS: NOT ACTIVE
            SOCKET_THERMAL_VIOLATION_STATUS: NOT ACTIVE
            VR_THERMAL_VIOLATION_STATUS: NOT ACTIVE
            HBM_THERMAL_VIOLATION_STATUS: NOT ACTIVE
            GFX_CLK_BELOW_HOST_LIMIT_VIOLATION_STATUS: N/A
            PROCHOT_VIOLATION_ACTIVITY: 0 %
            PPT_VIOLATION_ACTIVITY: 0 %
            SOCKET_THERMAL_VIOLATION_ACTIVITY: 0 %
            VR_THERMAL_VIOLATION_ACTIVITY: 0 %
            HBM_THERMAL_VIOLATION_ACTIVITY: 0 %
            GFX_CLK_BELOW_HOST_LIMIT_VIOLATION_ACTIVITY: 0 %

    GPU: 1
        THROTTLE:
            ACCUMULATION_COUNTER: 11238232
            PROCHOT_ACCUMULATED: 0
            PPT_ACCUMULATED: 0
            SOCKET_THERMAL_ACCUMULATED: 0
            VR_THERMAL_ACCUMULATED: 0
            HBM_THERMAL_ACCUMULATED: 0
            GFX_CLK_BELOW_HOST_LIMIT_ACCUMULATED: 0
            PROCHOT_VIOLATION_STATUS: NOT ACTIVE
            PPT_VIOLATION_STATUS: NOT ACTIVE
            SOCKET_THERMAL_VIOLATION_STATUS: NOT ACTIVE
            VR_THERMAL_VIOLATION_STATUS: NOT ACTIVE
            HBM_THERMAL_VIOLATION_STATUS: NOT ACTIVE
            GFX_CLK_BELOW_HOST_LIMIT_VIOLATION_STATUS: NOT ACTIVE
            PROCHOT_VIOLATION_ACTIVITY: 0 %
            PPT_VIOLATION_ACTIVITY: 0 %
            SOCKET_THERMAL_VIOLATION_ACTIVITY: 0 %
            VR_THERMAL_VIOLATION_ACTIVITY: 0 %
            HBM_THERMAL_VIOLATION_ACTIVITY: 0 %
            GFX_CLK_BELOW_HOST_LIMIT_VIOLATION_ACTIVITY: 0 %
    ...
    ```

- **Updated API `amdsmi_get_violation_status()` structure and CLI `amdsmi_violation_status_t` to include GFX Clk below host limit**  
    Updated structure `amdsmi_violation_status_t`:  

    ```C
    typedef struct {
        ...
        uint64_t acc_gfx_clk_below_host_limit;  //!< Current graphic clock below host limit count; Max uint64 means unsupported
        ...
        uint64_t per_gfx_clk_below_host_limit;  //!< Graphics clock below host limit violation % (greater than 0% is a violation); Max uint64 means unsupported
        ...
        uint8_t active_gfx_clk_below_host_limit;  //!< Graphics clock below host limit violation; 1 = active 0 = not active; Max uint8 means unsupported
        ...
    } amdsmi_violation_status_t;
    ```

- **Updated API `amdsmi_get_gpu_vram_info()` structure and CLI `amd-smi static --vram`**  
    Updated structure `amdsmi_vram_info_t`:  

    ```C
    typedef struct {
        amdsmi_vram_type_t vram_type;
        amdsmi_vram_vendor_type_t vram_vendor;
        uint64_t vram_size;
        uint32_t vram_bit_width;
        uint64_t vram_max_bandwidth;   //!< The VRAM max bandwidth at current memory clock (GB/s)
        uint64_t reserved[4];
    } amdsmi_vram_info_t;

    amdsmi_status_t amdsmi_get_gpu_vram_info(amdsmi_processor_handle processor_handle, amdsmi_vram_info_t *info)
    ```

    Example CLI output:

    ```console
    $ amd-smi static --vram
    GPU: 0
        VRAM:
            TYPE: GDDR6
            VENDOR: N/A
            SIZE: 16368 MB
            BIT_WIDTH: 256
            MAX_BANDWIDTH: 1555 GB/s
    GPU: 1
        VRAM:
            TYPE: GDDR6
            VENDOR: N/A
            SIZE: 30704 MB
            BIT_WIDTH: 256
            MAX_BANDWIDTH: 1555 GB/s
    ...
    ```

- **Changed amd-smi partition --accelerator & `amdsmi_get_gpu_accelerator_partition_profile_config()` detect users running without root/sudo permissions**  
  - Updated `amdsmi_get_gpu_accelerator_partition_profile_config()` to return `AMDSMI_STATUS_NO_PERM` immediately if users run without root/sudo permissions.
  - Updated `amd-smi partition --accelerator` to provide a warning for users without root/sudo permissions (see example below, ***output subject to change***).

    ```console
    $ amd-smi partition --accelerator

    ACCELERATOR_PARTITION_PROFILES:

    ***************************************************************************
    ** WARNING:                                                              **
    ** ACCELERATOR_PARTITION_PROFILES requires sudo/root permissions to run. **
    ** Please run the command with sudo permissions to get accurate results. **
    ***************************************************************************

    GPU_ID  PROFILE_INDEX  MEMORY_PARTITION_CAPS  ACCELERATOR_TYPE  PARTITION_ID     NUM_PARTITIONS  NUM_RESOURCES  RESOURCE_INDEX  RESOURCE_TYPE  RESOURCE_INSTANCES  RESOURCES_SHARED
    N/A     N/A            N/A                    N/A               0                N/A             N/A            N/A             N/A            N/A                 N/A
    N/A     N/A            N/A                    N/A               0                N/A             N/A            N/A             N/A            N/A                 N/A
    N/A     N/A            N/A                    N/A               0                N/A             N/A            N/A             N/A            N/A                 N/A
    N/A     N/A            N/A                    N/A               0                N/A             N/A            N/A             N/A            N/A                 N/A
    N/A     N/A            N/A                    N/A               0                N/A             N/A            N/A             N/A            N/A                 N/A
    N/A     N/A            N/A                    N/A               0                N/A             N/A            N/A             N/A            N/A                 N/A
    N/A     N/A            N/A                    N/A               0                N/A             N/A            N/A             N/A            N/A                 N/A
    N/A     N/A            N/A                    N/A               0                N/A             N/A            N/A             N/A            N/A                 N/A

    ACCELERATOR_PARTITION_RESOURCES:
    RESOURCE_INDEX  RESOURCE_TYPE  RESOURCE_INSTANCES  RESOURCES_SHARED
    N/A             N/A            N/A                 N/A
    N/A             N/A            N/A                 N/A
    N/A             N/A            N/A                 N/A
    N/A             N/A            N/A                 N/A
    N/A             N/A            N/A                 N/A
    N/A             N/A            N/A                 N/A
    N/A             N/A            N/A                 N/A
    N/A             N/A            N/A                 N/A


    Legend:
    * = Current mode
    ```

- **Changed `amd-smi partition --current`, `amd-smi partition --accelerator`, and `amdsmi_get_gpu_accelerator_partition_profile()` to display partition ID for each individual partition**  
  - Host will continue to display in the full array format, they do not display the individual partitions as Baremetal/Guest setups.
  - Baremetal and Guest MI3x setups will change to reflect each individual partition ID, now provided in `partition_id[0]` location (as seen in other amd-smi CLI commands).  
  - This change was needed for BM/Guest setups due to other related partition outputs seen in (`amd-smi list` and `amd-smi static --partition`) and individual logical partition devices displayed.

    Previous output:

    ```console
    $ amd-smi partition --current

    CURRENT_PARTITION:
    GPU_ID  MEMORY  ACCELERATOR_TYPE  ACCELERATOR_PROFILE_INDEX  PARTITION_ID
    0       NPS1    CPX               3                          0,1,2,3,4,5,6,7
    1       NPS1    CPX               3                          N/A
    2       NPS1    CPX               3                          N/A
    3       NPS1    CPX               3                          N/A
    4       NPS1    CPX               3                          N/A
    5       NPS1    CPX               3                          N/A
    6       NPS1    CPX               3                          N/A
    7       NPS1    CPX               3                          N/A
    8       NPS1    CPX               3                          0,1,2,3,4,5,6,7
    9       NPS1    CPX               3                          N/A
    10      NPS1    CPX               3                          N/A
    ...
    ```

    New output:

    ```console
    amd-smi partition --current
    CURRENT_PARTITION:
    GPU_ID  MEMORY  ACCELERATOR_TYPE  ACCELERATOR_PROFILE_INDEX  PARTITION_ID
    0       NPS1    CPX               3                          0
    1       NPS1    CPX               3                          1
    2       NPS1    CPX               3                          2
    3       NPS1    CPX               3                          3
    4       NPS1    CPX               3                          4
    5       NPS1    CPX               3                          5
    6       NPS1    CPX               3                          6
    7       NPS1    CPX               3                          7
    8       NPS1    CPX               3                          0
    9       NPS1    CPX               3                          1
    10      NPS1    CPX               3                          2
    ...
    ```

### Removed

- **Removed `GFX_BUSY_ACC` from `amd-smi metric --usage`**.  
  - Displaying `GFX_BUSY_ACC` does not provide helpful outputs for users.  

  Old output:

  ```console
  $ amd-smi metric --usage
    GPU: 0
        USAGE:
            GFX_ACTIVITY: 0 %
            UMC_ACTIVITY: 0 %
            MM_ACTIVITY: N/A
            VCN_ACTIVITY: [0 %, 0 %, 0 %, 0 %]
            JPEG_ACTIVITY: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]
            GFX_BUSY_INST:
                XCP_0: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]
            JPEG_BUSY:
                XCP_0: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]
            VCN_BUSY:
                XCP_0: [0 %, 0 %, 0 %, 0 %]
            GFX_BUSY_ACC:
                XCP_0: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
  ...
  ```

  New Output:

  ```console
  $ amd-smi metric --usage
  GPU: 0
      USAGE:
          GFX_ACTIVITY: 0 %
          UMC_ACTIVITY: 0 %
          MM_ACTIVITY: N/A
          VCN_ACTIVITY: [0 %, 0 %, 0 %, 0 %]
          JPEG_ACTIVITY: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]
          GFX_BUSY_INST:
              XCP_0: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]
          JPEG_BUSY:
              XCP_0: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %]
          VCN_BUSY:
              XCP_0: [0 %, 0 %, 0 %, 0 %]
  ...
  ```

### Optimized

- **Added additional help information to `amd-smi set --help` command**.  
  - sub commands now detail what values are acceptable as input. These include:
    - `amd-smi set --perf-level` with performance levels
    - `amd-smi set --profile` with power profiles
    - `amd-smi set --perf-determinism` with preset GPU frequency limits
    - `amd-smi set --power-cap` with valid power cap values
    - `amd-smi set --soc-pstate` with soc pstate policy ids
    - `amd-smi set --xgmi-plpd` with xgmi per link power down policy ids

- **Modified `amd-smi` CLI to allow case insensitive arguments if the argument does not begin with a single dash**.  
  - With this change `amd-smi version` and `amd-smi VERSION` will now yield the same output.
  - `amd-smi static --bus` and `amd-smi STATIC --BUS` will produce identical results.
  - `amd-smi static -b` and `amd-smi static -B` will still return different results (-b for bus and -B for board).

- **Converted xgmi read and write from KB's to readable units**.  
  - With this change `amd-smi xgmi` will now display the statistics in dynamically selected readable units.
  - Example output CLI output:

    ```console
    $ amd-smi xgmi
    LINK METRIC TABLE:
        bdf          bit_rate max_bandwidth link_type 0000:05:00.0 0000:26:00.0 0000:46:00.0 0000:65:00.0 0000:85:00.0 0000:a6:00.0 0000:c6:00.0 0000:e5:00.0
    GPU0   0000:05:00.0 32 Gb/s  512 Gb/s      XGMI
    Read                                                N/A          1.123 PB     1.123 PB     1.123 PB     1.123 PB     1.123 PB     1.123 PB     1.123 PB
    Write                                               N/A          229.1 MB     229.1 MB     229.1 MB     229.1 MB     229.1 MB     229.1 MB     229.1 MB
    GPU1   0000:26:00.0 32 Gb/s  512 Gb/s      XGMI
    Read                                                1.123 PB     N/A          1.123 PB     1.123 PB     1.123 PB     1.123 PB     1.123 PB     1.123 PB
    Write                                               229.1 MB     N/A          229.1 MB     229.1 MB     229.1 MB     229.1 MB     229.1 MB     229.1 MB
    GPU2   0000:46:00.0 32 Gb/s  512 Gb/s      XGMI
    Read                                                1.123 PB     1.123 PB     N/A          1.123 PB     1.123 PB     1.123 PB     1.123 PB     1.123 PB
    Write                                               229.1 MB     229.1 MB     N/A          229.1 MB     229.1 MB     229.1 MB     229.1 MB     229.1 MB
    ...
    ```

### Resolved issues

- **Fixed `amd-smi static --partition` for guest systems with MIx ASICs being unable to run**  

- **Fixed `amdsmi_get_gpu_asic_info` and `amd-smi static --asic` not displaying graphics version properly for MI2x, MI1x or Navi 3x ASICs**.  

  Before on MI100:

  ```console
  $ amd-smi static --asic | grep TARGET_GRAPHICS_VERSION
        TARGET_GRAPHICS_VERSION: gfx9008
        TARGET_GRAPHICS_VERSION: gfx9008
  ```

  After on MI100:

  ```console
  $ amd-smi static --asic | grep TARGET_GRAPHICS_VERSION
        TARGET_GRAPHICS_VERSION: gfx908
        TARGET_GRAPHICS_VERSION: gfx908
  ```

- **Fixed `amd-smi static --partition` for guest systems with MIx ASICs being unable to run**  

### Upcoming changes

- **Deprecation in ROCm 7.0 of the `AMDSMI_LIB_VERSION_YEAR` enum and API fields**.  

- **Deprecation in ROCm 7.0 of the `pasid` field within struct `amdsmi_process_info_t`**  

### Known issues

- **AMD SMI only reports 63 GPU devices when setting CPX on all 8 GPUs**  
    When setting CPX as a partition mode, there is a DRM node limitation of 64.  
    This is a known limitation of the Linux kernel, not the driver. Other drivers, such as those using PCIe space (e.g., ast), may be occupying the necessary DRM nodes.  
    The number of DRM nodes used can be checked via `ls /sys/class/drm`  

  - References to kernel changes:  
    - [Updates to number of node](https://cgit.freedesktop.org/drm/libdrm/commit/?id=7130cb163eb860d4a965c6708b64fe87cee881d6)  
    - [Identification of node type](https://cgit.freedesktop.org/drm/libdrm/commit/?id=3bc3cca230c5a064b2f554f26fdec27db0f5ead8)  

    Options are as follows:
    1) ***Workaround - removing other devices using DRM nodes***  

        Recommended steps for removing unnecessary drivers:  
        a. Unload amdgpu - `sudo rmmod amdgpu`  
        b. Remove unnecessary driver(s) - ex. `sudo rmmod ast`  
        c. Reload amgpu - `sudo modprobe amdgpu`  
        d. Confirm `amd-smi list` reports all nodes (this can vary per MI ASIC)

    2) ***Update your OS' kernel***  
    3) ***Building and installing your own kernel***  

## amd_smi_lib for ROCm 6.3.1

### Added

### Changed

- **Changed `amd-smi monitor`: No longer display `ENC_CLOCK`/`DEC_CLOCK` but `VCLOCK` and `DCLOCK`**.  
  Due to fix mentioned in `Resolved Issues`, this change was needed.  
  Reason: Navi products use vclk and dclk for both encode and decode. On MI products, only decode is supported.  
  Before:

  ```console
  $ amd-smi monitor -n -d
  GPU  ENC_UTIL  ENC_CLOCK  DEC_UTIL  DEC_CLOCK
    0     0.0 %     29 MHz       N/A     22 MHz
    1     0.0 %     29 MHz       N/A     22 MHz
    2     0.0 %     29 MHz       N/A     22 MHz
    3     0.0 %     29 MHz       N/A     22 MHz
    4     0.0 %     29 MHz       N/A     22 MHz
    5     0.0 %     29 MHz       N/A     22 MHz
    6     0.0 %     29 MHz       N/A     22 MHz
    7     0.0 %     29 MHz       N/A     22 MHz
  ```

  After:

  ```console
  $ amd-smi monitor -n -d
  GPU  ENC_UTIL  DEC_UTIL  VCLOCK  DCLOCK
    0       N/A     0.0 %  29 MHz  22 MHz
    1       N/A     0.0 %  29 MHz  22 MHz
    2       N/A     0.0 %  29 MHz  22 MHz
    3       N/A     0.0 %  29 MHz  22 MHz
    4       N/A     0.0 %  29 MHz  22 MHz
    5       N/A     0.0 %  29 MHz  22 MHz
    6       N/A     0.0 %  29 MHz  22 MHz
    7       N/A     0.0 %  29 MHz  22 MHz
  ```

### Removed

### Optimized

### Resolved issues

- **Fixed `amd-smi monitor`'s encode/decode: `ENC_UTIL`, `DEC_UTIL`, and now associate `VCLOCK`/`DCLOCK` with both**.  
  Navi products use vclk and dclk for both encode and decode. On MI products, only decode is supported. 

  Navi products cannot support displaying ENC_UTIL % at this time.  

  Before:
  ```console
  $ amd-smi monitor -n -d
  GPU  ENC_UTIL  ENC_CLOCK  DEC_UTIL  DEC_CLOCK
    0     0.0 %     29 MHz       N/A     22 MHz
    1     0.0 %     29 MHz       N/A     22 MHz
    2     0.0 %     29 MHz       N/A     22 MHz
    3     0.0 %     29 MHz       N/A     22 MHz
    4     0.0 %     29 MHz       N/A     22 MHz
    5     0.0 %     29 MHz       N/A     22 MHz
    6     0.0 %     29 MHz       N/A     22 MHz
    7     0.0 %     29 MHz       N/A     22 MHz
  ```

  After:
  ```console
  $ amd-smi monitor -n -d
  GPU  ENC_UTIL  DEC_UTIL  VCLOCK  DCLOCK
    0       N/A     0.0 %  29 MHz  22 MHz
    1       N/A     0.0 %  29 MHz  22 MHz
    2       N/A     0.0 %  29 MHz  22 MHz
    3       N/A     0.0 %  29 MHz  22 MHz
    4       N/A     0.0 %  29 MHz  22 MHz
    5       N/A     0.0 %  29 MHz  22 MHz
    6       N/A     0.0 %  29 MHz  22 MHz
    7       N/A     0.0 %  29 MHz  22 MHz
  ```

### Upcoming changes

### Known issues

## amd_smi_lib for ROCm 6.3.0

### Added

- **Added support for `amd-smi metric --ecc` & `amd-smi metric --ecc-blocks` on Guest VMs**.  
Guest VMs now support getting current ECC counts and ras information from the Host cards.

- **Added support for GPU metrics 1.6 to `amdsmi_get_gpu_metrics_info()`**.  
Updated `amdsmi_get_gpu_metrics_info()` and structure `amdsmi_gpu_metrics_t` to include new fields for PVIOL / TVIOL,  XCP (Graphics Compute Partitions) stats, and pcie_lc_perf_other_end_recovery:  
  - `uint64_t accumulation_counter` - used for all throttled calculations
  - `uint64_t prochot_residency_acc` - Processor hot accumulator
  - `uint64_t ppt_residency_acc` - Package Power Tracking (PPT) accumulator (used in PVIOL calculations)
  - `uint64_t socket_thm_residency_acc` - Socket thermal accumulator - (used in TVIOL calculations)
  - `uint64_t vr_thm_residency_acc` - Voltage Rail (VR) thermal accumulator
  - `uint64_t hbm_thm_residency_acc` - High Bandwidth Memory (HBM) thermal accumulator
  - `uint16_t num_partition` - corresponds to the current total number of partitions
  - `struct amdgpu_xcp_metrics_t xcp_stats[MAX_NUM_XCP]` - for each partition associated with current GPU, provides gfx busy & accumulators, jpeg, and decoder (VCN) engine utilizations
    - `uint32_t gfx_busy_inst[MAX_NUM_XCC]` - graphic engine utilization (%)
    - `uint16_t jpeg_busy[MAX_NUM_JPEG_ENGS]` - jpeg engine utilization (%)
    - `uint16_t vcn_busy[MAX_NUM_VCNS]` - decoder (VCN) engine utilization (%)
    - `uint64_t gfx_busy_acc[MAX_NUM_XCC]` - graphic engine utilization accumulated (%)
  - `uint32_t pcie_lc_perf_other_end_recovery` - corresponds to the pcie other end recovery counter

- **Added new violation status outputs and APIs: `amdsmi_status_t amdsmi_get_violation_status()`, `amd-smi metric  --throttle`, and `amd-smi monitor --violation`**.  
  ***Only available for MI300+ ASICs.***  
  Users can now retrieve violation status' through either our Python or C++ APIs. Additionally, we have
  added capability to view these outputs conveniently through `amd-smi metric --throttle` and `amd-smi monitor --violation`.  
  Example outputs are listed below (below is for reference, output is subject to change):

```shell
$ amd-smi metric --throttle
GPU: 0
    THROTTLE:
        ACCUMULATION_COUNTER: 3808991
        PROCHOT_ACCUMULATED: 0
        PPT_ACCUMULATED: 585613
        SOCKET_THERMAL_ACCUMULATED: 2190
        VR_THERMAL_ACCUMULATED: 0
        HBM_THERMAL_ACCUMULATED: 0
        PROCHOT_VIOLATION_STATUS: NOT ACTIVE
        PPT_VIOLATION_STATUS: NOT ACTIVE
        SOCKET_THERMAL_VIOLATION_STATUS: NOT ACTIVE
        VR_THERMAL_VIOLATION_STATUS: NOT ACTIVE
        HBM_THERMAL_VIOLATION_STATUS: NOT ACTIVE
        PROCHOT_VIOLATION_ACTIVITY: 0 %
        PPT_VIOLATION_ACTIVITY: 0 %
        SOCKET_THERMAL_VIOLATION_ACTIVITY: 0 %
        VR_THERMAL_VIOLATION_ACTIVITY: 0 %
        HBM_THERMAL_VIOLATION_ACTIVITY: 0 %



GPU: 1
    THROTTLE:
        ACCUMULATION_COUNTER: 3806335
        PROCHOT_ACCUMULATED: 0
        PPT_ACCUMULATED: 586332
        SOCKET_THERMAL_ACCUMULATED: 18010
        VR_THERMAL_ACCUMULATED: 0
        HBM_THERMAL_ACCUMULATED: 0
        PROCHOT_VIOLATION_STATUS: NOT ACTIVE
        PPT_VIOLATION_STATUS: NOT ACTIVE
        SOCKET_THERMAL_VIOLATION_STATUS: NOT ACTIVE
        VR_THERMAL_VIOLATION_STATUS: NOT ACTIVE
        HBM_THERMAL_VIOLATION_STATUS: NOT ACTIVE
        PROCHOT_VIOLATION_ACTIVITY: 0 %
        PPT_VIOLATION_ACTIVITY: 0 %
        SOCKET_THERMAL_VIOLATION_ACTIVITY: 0 %
        VR_THERMAL_VIOLATION_ACTIVITY: 0 %
        HBM_THERMAL_VIOLATION_ACTIVITY: 0 %

...
```

```shell
$ amd-smi monitor --violation
GPU     PVIOL     TVIOL  PHOT_TVIOL  VR_TVIOL  HBM_TVIOL
  0       0 %       0 %         0 %       0 %        0 %
  1       0 %       0 %         0 %       0 %        0 %
  2       0 %       0 %         0 %       0 %        0 %
  3       0 %       0 %         0 %       0 %        0 %
  4       0 %       0 %         0 %       0 %        0 %
  5       0 %       0 %         0 %       0 %        0 %
  6       0 %       0 %         0 %       0 %        0 %
  7       0 %       0 %         0 %       0 %        0 %
  8       0 %       0 %         0 %       0 %        0 %
  9       0 %       0 %         0 %       0 %        0 %
 10       0 %       0 %         0 %       0 %        0 %
 11       0 %       0 %         0 %       0 %        0 %
 12       0 %       0 %         0 %       0 %        0 %
 13       0 %       0 %         0 %       0 %        0 %
 14       0 %       0 %         0 %       0 %        0 %
 15       0 %       0 %         0 %       0 %        0 %
...
```

- **Added ability to view XCP (Graphics Compute Partition) activity within `amd-smi metric --usage`**.  
  ***Partition specific features are only available on MI300+ ASICs***  
  Users can now retrieve graphic utilization statistic on a per-XCP (per-partition) basis. Here all  XCP activities will be listed,
  but the current XCP is the partition id listed under both `amd-smi list` and `amd-smi static --partition`.  
  Example outputs are listed below (below is for reference, output is subject to change):

```shell
$ amd-smi metric --usage
GPU: 0
    USAGE:
        GFX_ACTIVITY: 0 %
        UMC_ACTIVITY: 0 %
        MM_ACTIVITY: N/A
        VCN_ACTIVITY: [0 %, N/A, N/A, N/A]
        JPEG_ACTIVITY: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A,
            N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
            N/A, N/A, N/A]
        GFX_BUSY_INST:
            XCP_0: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_1: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_2: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_3: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_4: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_5: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_6: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_7: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
        JPEG_BUSY:
            XCP_0: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_1: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_2: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_3: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_4: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_5: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_6: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_7: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
        VCN_BUSY:
            XCP_0: [0 %, N/A, N/A, N/A]
            XCP_1: [0 %, N/A, N/A, N/A]
            XCP_2: [0 %, N/A, N/A, N/A]
            XCP_3: [0 %, N/A, N/A, N/A]
            XCP_4: [0 %, N/A, N/A, N/A]
            XCP_5: [0 %, N/A, N/A, N/A]
            XCP_6: [0 %, N/A, N/A, N/A]
            XCP_7: [0 %, N/A, N/A, N/A]
        GFX_BUSY_ACC:
            XCP_0: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_1: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_2: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_3: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_4: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_5: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_6: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_7: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]

GPU: 1
    USAGE:
        GFX_ACTIVITY: 0 %
        UMC_ACTIVITY: 0 %
        MM_ACTIVITY: N/A
        VCN_ACTIVITY: [0 %, N/A, N/A, N/A]
        JPEG_ACTIVITY: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A,
            N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
            N/A, N/A, N/A]
        GFX_BUSY_INST:
            XCP_0: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_1: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_2: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_3: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_4: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_5: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_6: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_7: [0 %, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
        JPEG_BUSY:
            XCP_0: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_1: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_2: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_3: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_4: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_5: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_6: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
            XCP_7: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A,
                N/A, N/A, N/A]
        VCN_BUSY:
            XCP_0: [0 %, N/A, N/A, N/A]
            XCP_1: [0 %, N/A, N/A, N/A]
            XCP_2: [0 %, N/A, N/A, N/A]
            XCP_3: [0 %, N/A, N/A, N/A]
            XCP_4: [0 %, N/A, N/A, N/A]
            XCP_5: [0 %, N/A, N/A, N/A]
            XCP_6: [0 %, N/A, N/A, N/A]
            XCP_7: [0 %, N/A, N/A, N/A]
        GFX_BUSY_ACC:
            XCP_0: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_1: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_2: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_3: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_4: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_5: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_6: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]
            XCP_7: [N/A, N/A, N/A, N/A, N/A, N/A, N/A, N/A]

...
```

- **Added `LC_PERF_OTHER_END_RECOVERY` CLI output to `amd-smi metric --pcie` and updated `amdsmi_get_pcie_info()` to include this value**.  
  ***Feature is only available on MI300+ ASICs***  
  Users can now retrieve both through `amdsmi_get_pcie_info()` which has an updated structure:

```C
typedef struct {
  ...
  struct pcie_metric_ {
    uint16_t pcie_width;                  //!< current PCIe width
    uint32_t pcie_speed;                  //!< current PCIe speed in MT/s
    uint32_t pcie_bandwidth;              //!< current instantaneous PCIe bandwidth in Mb/s
    uint64_t pcie_replay_count;           //!< total number of the replays issued on the PCIe link
    uint64_t pcie_l0_to_recovery_count;   //!< total number of times the PCIe link transitioned from L0 to the recovery state
    uint64_t pcie_replay_roll_over_count; //!< total number of replay rollovers issued on the PCIe link
    uint64_t pcie_nak_sent_count;         //!< total number of NAKs issued on the PCIe link by the device
    uint64_t pcie_nak_received_count;     //!< total number of NAKs issued on the PCIe link by the receiver
    uint32_t pcie_lc_perf_other_end_recovery_count;  //!< PCIe other end recovery counter
    uint64_t reserved[12];
  } pcie_metric;
  uint64_t reserved[32];
} amdsmi_pcie_info_t;
```

  - Example outputs are listed below (below is for reference, output is subject to change):

```shell
$ amd-smi metric --pcie
GPU: 0
    PCIE:
        WIDTH: 16
        SPEED: 32 GT/s
        BANDWIDTH: 18 Mb/s
        REPLAY_COUNT: 0
        L0_TO_RECOVERY_COUNT: 0
        REPLAY_ROLL_OVER_COUNT: 0
        NAK_SENT_COUNT: 0
        NAK_RECEIVED_COUNT: 0
        CURRENT_BANDWIDTH_SENT: N/A
        CURRENT_BANDWIDTH_RECEIVED: N/A
        MAX_PACKET_SIZE: N/A
        LC_PERF_OTHER_END_RECOVERY: 0

GPU: 1
    PCIE:
        WIDTH: 16
        SPEED: 32 GT/s
        BANDWIDTH: 18 Mb/s
        REPLAY_COUNT: 0
        L0_TO_RECOVERY_COUNT: 0
        REPLAY_ROLL_OVER_COUNT: 0
        NAK_SENT_COUNT: 0
        NAK_RECEIVED_COUNT: 0
        CURRENT_BANDWIDTH_SENT: N/A
        CURRENT_BANDWIDTH_RECEIVED: N/A
        MAX_PACKET_SIZE: N/A
        LC_PERF_OTHER_END_RECOVERY: 0
...
```

- **Added retrieving a set of GPUs that are nearest to a given device at a specific link type level**.  
  - Added `amdsmi_get_link_topology_nearest()` function to amd-smi C and Python Libraries.

- **Added more supported utilization count types to `amdsmi_get_utilization_count()`**.  

- **Added `amd-smi set -L/--clk-limit ...` command**.  
  Equivalent to rocm-smi's '--extremum' command which sets sclk's or mclk's soft minimum or soft maximum clock frequency.

- **Added unittest functionality to test amdsmi API calls in Python**.  

- **Changed the `power` parameter in `amdsmi_get_energy_count()` to `energy_accumulator`**.  
  - Changes propagate forwards into the python interface as well, however we are maintaining backwards compatibility and keeping the `power` field in the python API until ROCm 6.4.

- **Added GPU memory overdrive percentage to `amd-smi metric -o`**.  
  - Added `amdsmi_get_gpu_mem_overdrive_level()` function to amd-smi C and Python Libraries.

- **Added retrieving connection type and P2P capabilities between two GPUs**.  
  - Added `amdsmi_topo_get_p2p_status()` function to amd-smi C and Python Libraries.
  - Added retrieving P2P link capabilities to CLI `amd-smi topology`.

```shell
$ amd-smi topology -h
usage: amd-smi topology [-h] [--json | --csv] [--file FILE] [--loglevel LEVEL]
                        [-g GPU [GPU ...]] [-a] [-w] [-o] [-t] [-b]

If no GPU is specified, returns information for all GPUs on the system.
If no topology argument is provided all topology information will be displayed.

Topology arguments:
  -h, --help               show this help message and exit
  -g, --gpu GPU [GPU ...]  Select a GPU ID, BDF, or UUID from the possible choices:
                           ID: 0 | BDF: 0000:0c:00.0 | UUID: <redacted>
                           ID: 1 | BDF: 0000:22:00.0 | UUID: <redacted>
                           ID: 2 | BDF: 0000:38:00.0 | UUID: <redacted>
                           ID: 3 | BDF: 0000:5c:00.0 | UUID: <redacted>
                           ID: 4 | BDF: 0000:9f:00.0 | UUID: <redacted>
                           ID: 5 | BDF: 0000:af:00.0 | UUID: <redacted>
                           ID: 6 | BDF: 0000:bf:00.0 | UUID: <redacted>
                           ID: 7 | BDF: 0000:df:00.0 | UUID: <redacted>
                             all | Selects all devices

  -a, --access             Displays link accessibility between GPUs
  -w, --weight             Displays relative weight between GPUs
  -o, --hops               Displays the number of hops between GPUs
  -t, --link-type          Displays the link type between GPUs
  -b, --numa-bw            Display max and min bandwidth between nodes
  -c, --coherent           Display cache coherent (or non-coherent) link capability between nodes
  -n, --atomics            Display 32 and 64-bit atomic io link capability between nodes
  -d, --dma                Display P2P direct memory access (DMA) link capability between nodes
  -z, --bi-dir             Display P2P bi-directional link capability between nodes

Command Modifiers:
  --json                   Displays output in JSON format (human readable by default).
  --csv                    Displays output in CSV format (human readable by default).
  --file FILE              Saves output into a file on the provided path (stdout by default).
  --loglevel LEVEL         Set the logging level from the possible choices:
                                DEBUG, INFO, WARNING, ERROR, CRITICAL
```

```shell
$ amd-smi topology -cndz
CACHE COHERENCY TABLE:
             0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
0000:0c:00.0 SELF         C            NC           NC           C            C            C            NC
0000:22:00.0 C            SELF         NC           C            C            C            NC           C
0000:38:00.0 NC           NC           SELF         C            C            NC           C            NC
0000:5c:00.0 NC           C            C            SELF         NC           C            NC           NC
0000:9f:00.0 C            C            C            NC           SELF         NC           NC           C
0000:af:00.0 C            C            NC           C            NC           SELF         C            C
0000:bf:00.0 C            NC           C            NC           NC           C            SELF         NC
0000:df:00.0 NC           C            NC           NC           C            C            NC           SELF

ATOMICS TABLE:
             0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
0000:0c:00.0 SELF         64,32        64,32        64           32           32           N/A          64,32
0000:22:00.0 64,32        SELF         64           32           32           N/A          64,32        64,32
0000:38:00.0 64,32        64           SELF         32           N/A          64,32        64,32        64,32
0000:5c:00.0 64           32           32           SELF         64,32        64,32        64,32        32
0000:9f:00.0 32           32           N/A          64,32        SELF         64,32        32           32
0000:af:00.0 32           N/A          64,32        64,32        64,32        SELF         32           N/A
0000:bf:00.0 N/A          64,32        64,32        64,32        32           32           SELF         64,32
0000:df:00.0 64,32        64,32        64,32        32           32           N/A          64,32        SELF

DMA TABLE:
             0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
0000:0c:00.0 SELF         T            T            F            F            T            F            T
0000:22:00.0 T            SELF         F            F            T            F            T            T
0000:38:00.0 T            F            SELF         T            F            T            T            T
0000:5c:00.0 F            F            T            SELF         T            T            T            F
0000:9f:00.0 F            T            F            T            SELF         T            F            F
0000:af:00.0 T            F            T            T            T            SELF         F            T
0000:bf:00.0 F            T            T            T            F            F            SELF         F
0000:df:00.0 T            T            T            F            F            T            F            SELF

BI-DIRECTIONAL TABLE:
             0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
0000:0c:00.0 SELF         T            T            F            F            T            F            T
0000:22:00.0 T            SELF         F            F            T            F            T            T
0000:38:00.0 T            F            SELF         T            F            T            T            T
0000:5c:00.0 F            F            T            SELF         T            T            T            F
0000:9f:00.0 F            T            F            T            SELF         T            F            F
0000:af:00.0 T            F            T            T            T            SELF         F            T
0000:bf:00.0 F            T            T            T            F            F            SELF         F
0000:df:00.0 T            T            T            F            F            T            F            SELF

Legend:
 SELF = Current GPU
 ENABLED / DISABLED = Link is enabled or disabled
 N/A = Not supported
 T/F = True / False
 C/NC = Coherent / Non-Coherent io links
 64,32 = 64 bit and 32 bit atomic support
 <BW from>-<BW to>
```

- **Created new amdsmi_kfd_info_t and added information under `amd-smi list`**.  
  - Due to fixes needed to properly enumerate all logical GPUs in CPX, new device identifiers were added in to a new `amdsmi_kfd_info_t` which gets populated via the API `amdsmi_get_gpu_kfd_info()`.
  - This info has been added to the `amd-smi list`.
  - These new fields are only available for BM/Guest Linux devices at this time.

```C
typedef struct {
  uint64_t kfd_id;  //< 0xFFFFFFFFFFFFFFFF if not supported
  uint32_t node_id;  //< 0xFFFFFFFF if not supported
  uint32_t current_partition_id;  //< 0xFFFFFFFF if not supported
  uint32_t reserved[12];
} amdsmi_kfd_info_t;
```

```shell
$ amd-smi list
GPU: 0
    BDF: 0000:23:00.0
    UUID: <redacted>
    KFD_ID: 45412
    NODE_ID: 1
    PARTITION_ID: 0

GPU: 1
    BDF: 0000:26:00.0
    UUID: <redacted>
    KFD_ID: 59881
    NODE_ID: 2
    PARTITION_ID: 0
```

- **Added Subsystem Device ID to `amd-smi static --asic`**.  
  - No underlying changes to amdsmi_get_gpu_asic_info

```shell
$ amd-smi static --asic
GPU: 0
    ASIC:
        MARKET_NAME: MI308X
        VENDOR_ID: 0x1002
        VENDOR_NAME: Advanced Micro Devices Inc. [AMD/ATI]
        SUBVENDOR_ID: 0x1002
        DEVICE_ID: 0x74a2
        SUBSYSTEM_ID: 0x74a2
        REV_ID: 0x00
        ASIC_SERIAL: <redacted>
        OAM_ID: 5
        NUM_COMPUTE_UNITS: 20
        TARGET_GRAPHICS_VERSION: gfx942
```

- **Added Target_Graphics_Version to `amd-smi static --asic` and `amdsmi_get_gpu_asic_info()`**.  

```C
typedef struct {
  char  market_name[AMDSMI_256_LENGTH];
  uint32_t vendor_id;   //< Use 32 bit to be compatible with other platform.
  char vendor_name[AMDSMI_MAX_STRING_LENGTH];
  uint32_t subvendor_id;   //< The subsystem vendor id
  uint64_t device_id;   //< The device id of a GPU
  uint32_t rev_id;
  char asic_serial[AMDSMI_NORMAL_STRING_LENGTH];
  uint32_t oam_id;   //< 0xFFFF if not supported
  uint32_t num_of_compute_units;   //< 0xFFFFFFFF if not supported
  uint64_t target_graphics_version;  //< 0xFFFFFFFFFFFFFFFF if not supported
  uint32_t reserved[15];
} amdsmi_asic_info_t;
```

```shell
$ amd-smi static --asic
GPU: 0
    ASIC:
        MARKET_NAME: MI308X
        VENDOR_ID: 0x1002
        VENDOR_NAME: Advanced Micro Devices Inc. [AMD/ATI]
        SUBVENDOR_ID: 0x1002
        DEVICE_ID: 0x74a2
        SUBSYSTEM_ID: 0x74a2
        REV_ID: 0x00
        ASIC_SERIAL: <redacted>
        OAM_ID: 5
        NUM_COMPUTE_UNITS: 20
        TARGET_GRAPHICS_VERSION: gfx942
```

### Changed

- **Improvement: Users now have the ability to set and reset without providing `-g all` using AMD SMI CLI**.  
Users can now provide set and reset without `-g all`. Previously, users were required to provide:   
`sudo amd-smi set -g all <set arguments>` or `sudo amd-smi reset -g all <set arguments>`  
This update allows users to set or reset without providing `-g all` arguments. Allowing commands:  
`sudo amd-smi set <set arguments>` or `sudo amd-smi reset <set arguments>`  
This action will default to try to set/reset for all AMD GPUs on the user's system.

- **Improvement: `amd-smi set --memory-partition` now includes a warning banner and progress bar**.  
For devices which support dynamically changing memory partitions, we now provide a warning for users. We provide this warning to provide users knowledge that this action requires users to quit any gpu workloads. Also to let them know this process will trigger an AMD GPU driver reload. Since this process takes time to complete, a progress bar has been provided until actions can verified as a successful change. Otherwise, AMD SMI will report any errors to users and what actions can be taken. See example below:  
```shell
$ sudo amd-smi set -M NPS1

          ****** WARNING ******

          Setting Dynamic Memory (NPS) partition modes require users to quit all GPU workloads.
          AMD SMI will then attempt to change memory (NPS) partition mode.
          Upon a successful set, AMD SMI will then initiate an action to restart amdgpu driver.
          This action will change all GPU's in the hive to the requested memory (NPS) partition mode.

          Please use this utility with caution.

Do you accept these terms? [Y/N] y

Updating memory partition for gpu 0: [████████████████████████████████████████] 40/40 secs remain

GPU: 0
    MEMORYPARTITION: Successfully set memory partition to NPS1

GPU: 1
    MEMORYPARTITION: Successfully set memory partition to NPS1

GPU: 2
    MEMORYPARTITION: Successfully set memory partition to NPS1
...
```  

- **Updated `amdsmi_get_gpu_accelerator_partition_profile` to provide driver memory partition capabilities**.  
Driver now has the ability to report what the user can set memory partition modes to. User can now see available
memory partition modes upon an invalid argument return from memory partition mode set (`amdsmi_set_gpu_memory_partition`).
This change also updates `amd-smi partition`, `amd-smi partition --memory`, and `amd-smi partition --accelerator` (*see note below)   
***Note: *Subject to change for ROCm 6.4***

- **Updated `amdsmi_set_gpu_memory_partition` to not return until a successful restart of AMD GPU Driver**.  
This change keeps checking for ~ up to 40 seconds for a successful restart of the AMD GPU driver. Additionally, the API call continues to check if memory partition (NPS) SYSFS files are successfully updated to reflect the user's requested memory partition (NPS) mode change. Otherwise, reports an error back to the user. Due to these changes, we have updated AMD SMI's CLI to reflect the maximum wait of 40 seconds, while a memory partition change is in progress.

- **All APIs now have the ability to catch driver reporting invalid arguments**.  
Now AMD SMI APIs can show AMDSMI_STATUS_INVAL when driver returns EINVAL.  
For example, if user tries to set to NPS8, but the memory partition mode is not an available mode to set to. Commonly referred to as `CAPS` (see `amd-smi partition --memory`), provided by `amdsmi_get_gpu_accelerator_partition_profile`(*see note below).  
***Note: *Subject to change for ROCm 6.4***

- **Updated BDF commands to look use KFD SYSFS for BDF: `amdsmi_get_gpu_device_bdf()`**.  
This aligns BDF output with ROCm SMI.
See below for overview as seen from `rsmi_dev_pci_id_get()` now provides partition ID. See API for better detail. Previously these bits were reserved bits (right before domain) and partition id was within function.
  - bits [63:32] = domain
  - bits [31:28] = partition id
  - bits [27:16] = reserved
  - bits [15: 0] = pci bus/device/function

- **Moved python tests directory path install location**.  
  - `/opt/<rocm-path>/share/amd_smi/pytest/..` to `/opt/<rocm-path>/share/amd_smi/tests/python_unittest/..`
  - On amd-smi-lib-tests uninstall, the amd_smi tests folder is removed
  - Removed pytest dependency, our python testing now only depends on the unittest framework.

- **Updated Partition APIs and struct information and added and partition_id to `amd-smi static --partition`**.  
  - As part of an overhaul to partition information, some partition information will be made available in the `amdsmi_accelerator_partition_profile_t`.
  - This struct will be filled out by a new API, `amdsmi_get_gpu_accelerator_partition_profile()`.
  - Future data from these APIs will eventually get added to `amd-smi partition`.

```C
#define AMDSMI_MAX_ACCELERATOR_PROFILE    32
#define AMDSMI_MAX_CP_PROFILE_RESOURCES   32
#define AMDSMI_MAX_ACCELERATOR_PARTITIONS 8

/**
 * @brief Accelerator Partition. This enum is used to identify
 * various accelerator partitioning settings.
 */
typedef enum {
  AMDSMI_ACCELERATOR_PARTITION_INVALID = 0,
  AMDSMI_ACCELERATOR_PARTITION_SPX,        //!< Single GPU mode (SPX)- All XCCs work
                                       //!< together with shared memory
  AMDSMI_ACCELERATOR_PARTITION_DPX,        //!< Dual GPU mode (DPX)- Half XCCs work
                                       //!< together with shared memory
  AMDSMI_ACCELERATOR_PARTITION_TPX,        //!< Triple GPU mode (TPX)- One-third XCCs
                                       //!< work together with shared memory
  AMDSMI_ACCELERATOR_PARTITION_QPX,        //!< Quad GPU mode (QPX)- Quarter XCCs
                                       //!< work together with shared memory
  AMDSMI_ACCELERATOR_PARTITION_CPX,        //!< Core mode (CPX)- Per-chip XCC with
                                       //!< shared memory
} amdsmi_accelerator_partition_type_t;

/**
 * @brief Possible Memory Partition Modes.
 * This union is used to identify various memory partitioning settings.
 */
typedef union {
    struct {
        uint32_t nps1_cap :1;  // bool 1 = true; 0 = false; Max uint32 means unsupported
        uint32_t nps2_cap :1;  // bool 1 = true; 0 = false; Max uint32 means unsupported
        uint32_t nps4_cap :1;  // bool 1 = true; 0 = false; Max uint32 means unsupported
        uint32_t nps8_cap :1;  // bool 1 = true; 0 = false; Max uint32 means unsupported
        uint32_t reserved :28;
    } amdsmi_nps_flags_t;

    uint32_t nps_cap_mask;
} amdsmi_nps_caps_t;

typedef struct {
  amdsmi_accelerator_partition_type_t  profile_type;   // SPX, DPX, QPX, CPX and so on
  uint32_t num_partitions;  // On MI300X, SPX: 1, DPX: 2, QPX: 4, CPX: 8, length of resources array
  uint32_t profile_index;
  amdsmi_nps_caps_t memory_caps;             // Possible memory partition capabilities
  uint32_t num_resources;                    // length of index_of_resources_profile
  uint32_t resources[AMDSMI_MAX_ACCELERATOR_PARTITIONS][AMDSMI_MAX_CP_PROFILE_RESOURCES];
  uint64_t reserved[6];
} amdsmi_accelerator_partition_profile_t;
```

```shell
$ amd-smi static --partition
GPU: 0
    PARTITION:
        COMPUTE_PARTITION: CPX
        MEMORY_PARTITION: NPS4
        PARTITION_ID: 0
```

### Removed

- **Removed `amd-smi reset --compute-partition` and `... --memory-partition` and associated APIs**.  
  - This change is part of the partition redesign.
  - associated APIs include `amdsmi_reset_gpu_compute_partition()` and `amdsmi_reset_gpu_memory_partition()`

- **Removed usage of _validate_positive in Parser and replaced with _positive_int and _not_negative_int as appropriate**.  
  - This will allow 0 to be a valid input for several options in setting CPUs where appropriate (for example, as a mode or NBIOID)

### Optimized

- **Adjusted ordering of gpu_metrics calls to ensure that pcie_bw values remain stable in `amd-smi metric` & `amd-smi monitor`**.  
  - With this change additional padding was added to PCIE_BW `amd-smi monitor --pcie`

### Resolved issues

- **Fixed `amdsmi_get_gpu_asic_info`'s `target_graphics_version` and `amd-smi --asic` not displaying properly for MI2x or Navi 3x ASICs**.  

- **Fixed `amd-smi reset` commands showing an AttributeError**.  

- **Improved Offline install process & lowered dependency for PyYAML**.  

- **Fixed CPX not showing total number of logical GPUs**.  
  - Updates were made to `amdsmi_init()` and `amdsmi_get_gpu_bdf_id(..)`. In order to display all logical devices, we needed a way to provide order to GPU's enumerated. This was done by adding a partition_id within the BDF optional pci_id bits.
  - Due to driver changes in KFD, some devices may report bits [31:28] or [2:0]. With the newly added `amdsmi_get_gpu_bdf_id(..)`, we provided this fallback to properly retrieve partition ID. We
plan to eventually remove partition ID from the function portion of the BDF (Bus Device Function). See below for PCI ID description.

    - bits [63:32] = domain
    - bits [31:28] or bits [2:0] = partition id
    - bits [27:16] = reserved
    - bits [15:8]  = Bus
    - bits [7:3] = Device
    - bits [2:0] = Function (partition id maybe in bits [2:0]) <-- Fallback for non SPX modes

  - Previously in non-SPX modes (ex. CPX/TPX/DPX/etc) some MI3x ASICs would not report all logical GPU devices within AMD SMI.

```shell
$ amd-smi monitor -p -t -v
GPU  POWER  GPU_TEMP  MEM_TEMP  VRAM_USED  VRAM_TOTAL
  0  248 W     55 °C     48 °C     283 MB   196300 MB
  1  247 W     55 °C     48 °C     283 MB   196300 MB
  2  247 W     55 °C     48 °C     283 MB   196300 MB
  3  247 W     55 °C     48 °C     283 MB   196300 MB
  4  221 W     50 °C     42 °C     283 MB   196300 MB
  5  221 W     50 °C     42 °C     283 MB   196300 MB
  6  222 W     50 °C     42 °C     283 MB   196300 MB
  7  221 W     50 °C     42 °C     283 MB   196300 MB
  8  239 W     53 °C     46 °C     283 MB   196300 MB
  9  239 W     53 °C     46 °C     283 MB   196300 MB
 10  239 W     53 °C     46 °C     283 MB   196300 MB
 11  239 W     53 °C     46 °C     283 MB   196300 MB
 12  219 W     51 °C     48 °C     283 MB   196300 MB
 13  219 W     51 °C     48 °C     283 MB   196300 MB
 14  219 W     51 °C     48 °C     283 MB   196300 MB
 15  219 W     51 °C     48 °C     283 MB   196300 MB
 16  222 W     51 °C     47 °C     283 MB   196300 MB
 17  222 W     51 °C     47 °C     283 MB   196300 MB
 18  222 W     51 °C     47 °C     283 MB   196300 MB
 19  222 W     51 °C     48 °C     283 MB   196300 MB
 20  241 W     55 °C     48 °C     283 MB   196300 MB
 21  241 W     55 °C     48 °C     283 MB   196300 MB
 22  241 W     55 °C     48 °C     283 MB   196300 MB
 23  240 W     55 °C     48 °C     283 MB   196300 MB
 24  211 W     51 °C     45 °C     283 MB   196300 MB
 25  211 W     51 °C     45 °C     283 MB   196300 MB
 26  211 W     51 °C     45 °C     283 MB   196300 MB
 27  211 W     51 °C     45 °C     283 MB   196300 MB
 28  227 W     51 °C     49 °C     283 MB   196300 MB
 29  227 W     51 °C     49 °C     283 MB   196300 MB
 30  227 W     51 °C     49 °C     283 MB   196300 MB
 31  227 W     51 °C     49 °C     283 MB   196300 MB
```

- **Fixed incorrect implementation of the Python API `amdsmi_get_gpu_metrics_header_info()`**.  

- **`amdsmitst` TestGpuMetricsRead now prints metric in correct units**.  

### Upcoming changes

- **Python API for `amdsmi_get_energy_count()` will deprecate the `power` field in ROCm 6.4 and use `energy_accumulator` field instead**.  

- **New memory and compute partition APIs incoming for ROCm 6.4**.  
  - These APIs will be updated to fully populate the CLI and allowing compute (accelerator) partitions to be set by profile ID.
  - One API will be provided, to reset both memory and compute (accelerator).
    - There are dependencies regarding available compute partitions when in other memory modes.
    - Driver will be providing these default modes
    - Memory partition resets (for BM) require driver reloads - this will allow us to notify users before taking this action, then change to the default compute partition modes.
  - The following APIs will remain:

```C
amdsmi_status_t
amdsmi_set_gpu_compute_partition(amdsmi_processor_handle processor_handle,
                                  amdsmi_compute_partition_type_t compute_partition);
amdsmi_status_t
amdsmi_get_gpu_compute_partition(amdsmi_processor_handle processor_handle,
                                  char *compute_partition, uint32_t len);
amdsmi_status_t
amdsmi_get_gpu_memory_partition(amdsmi_processor_handle processor_handle,

                                  char *memory_partition, uint32_t len);
amdsmi_status_t
amdsmi_set_gpu_memory_partition(amdsmi_processor_handle processor_handle,
                                  amdsmi_memory_partition_type_t memory_partition);
```

- **`amd-smi set --compute-partition` "SPX/DPX/CPX..." will modified to accept profile IDs in ROCm 6.4**.  
  - This is due to aligning with Host setups and providing more robust partition information through the APIs outlined above. Furthermore, new APIs which will be available on both BM/Host can set by profile ID. (functionality coming soon!)

- **Added preliminary `amd-smi partition` command**.  
  - The new partition command can be used to display GPU information, including memory and accelerator partition information.
  - The command will be at full functionality once additional partition information from `amdsmi_get_gpu_accelerator_partition_profile()` has been implemented.

## amd_smi_lib for ROCm 6.2.1

### Added

- **Removed `amd-smi metric --ecc` & `amd-smi metric --ecc-blocks` on Guest VMs**.  
Guest VMs do not support getting current ECC counts from the Host cards.

- **Added `amd-smi static --ras`on Guest VMs**.  
Guest VMs can view enabled/disabled ras features that are on Host cards.

### Resolved issues

- **Fixed TypeError in `amd-smi process -G`**.  

- **Updated CLI error strings to handle empty and invalid GPU/CPU inputs**.  

- **Fixed Guest VM showing passthrough options**.  

- **Fixed firmware formatting where leading 0s were missing**.  

## amd_smi_lib for ROCm 6.2.0

### Added

- **`amd-smi dmon` is now available as an alias to `amd-smi monitor`**.  

- **Added optional process table under `amd-smi monitor -q`**.  
The monitor subcommand within the CLI Tool now has the `-q` option to enable an optional process table underneath the original monitored output.

```shell
$ amd-smi monitor -q
GPU  POWER  GPU_TEMP  MEM_TEMP  GFX_UTIL  GFX_CLOCK  MEM_UTIL  MEM_CLOCK  ENC_UTIL  ENC_CLOCK  DEC_UTIL  DEC_CLOCK  SINGLE_ECC  DOUBLE_ECC  PCIE_REPLAY  VRAM_USED  VRAM_TOTAL   PCIE_BW
  0  199 W    103 °C     84 °C      99 %   1920 MHz      31 %   1000 MHz       N/A      0 MHz       N/A      0 MHz           0           0            0    1235 MB    16335 MB  N/A Mb/s

PROCESS INFO:
GPU                  NAME      PID  GTT_MEM  CPU_MEM  VRAM_MEM  MEM_USAGE     GFX     ENC
  0                   rvs  1564865    0.0 B    0.0 B    1.1 GB      0.0 B    0 ns    0 ns
```

- **Added Handling to detect VMs with passthrough configurations in CLI Tool**.  
CLI Tool had only allowed a restricted set of options for Virtual Machines with passthrough GPUs. Now we offer an expanded set of functions available to passthrough configured GPUs.

- **Added Process Isolation and Clear SRAM functionality to the CLI Tool for VMs**.  
VMs now have the ability to set the process isolation and clear the sram from the CLI tool. Using the following commands

```shell
amd-smi set --process-isolation <0 or 1>
amd-smi reset --clean_local_data
```

- **Added macros that were in `amdsmi.h` to the amdsmi Python library `amdsmi_interface.py`**.  
Added macros to reference max size limitations for certain amdsmi functions such as max dpm policies and max fanspeed.

- **Added Ring Hang event**.  
Added `AMDSMI_EVT_NOTIF_RING_HANG` to the possible events in the `amdsmi_evt_notification_type_t` enum.

### Optimized

- **Updated CLI error strings to specify invalid device type queried**  

```shell
$ amd-smi static --asic --gpu 123123
Can not find a device: GPU '123123' Error code: -3
```

- **Removed elevated permission requirements for `amdsmi_get_gpu_process_list()`**.  
Previously if a processes with elevated permissions was running amd-smi would required sudo to display all output. Now amd-smi will populate all process data and return N/A for elevated process names instead. However if ran with sudo you will be able to see the name like so:

```shell
$ amd-smi process
GPU: 0
    PROCESS_INFO:
        NAME: N/A
        PID: 1693982
        MEMORY_USAGE:
            GTT_MEM: 0.0 B
            CPU_MEM: 0.0 B
            VRAM_MEM: 10.1 GB
        MEM_USAGE: 0.0 B
        USAGE:
            GFX: 0 ns
            ENC: 0 ns
```

```shell
$ sudo amd-smi process
GPU: 0
    PROCESS_INFO:
        NAME: TransferBench
        PID: 1693982
        MEMORY_USAGE:
            GTT_MEM: 0.0 B
            CPU_MEM: 0.0 B
            VRAM_MEM: 10.1 GB
        MEM_USAGE: 0.0 B
        USAGE:
            GFX: 0 ns
            ENC: 0 ns
```

- **Updated naming for `amdsmi_set_gpu_clear_sram_data()` to `amdsmi_clean_gpu_local_data()`**.  
Changed the naming to be more accurate to what the function was doing. This change also extends to the CLI where we changed the `clear-sram-data` command to `clean_local_data`.

- **Updated `amdsmi_clk_info_t` struct in amdsmi.h and amdsmi_interface.py to align with host/guest**.  
Changed cur_clk to clk, changed sleep_clk to clk_deep_sleep, and added clk_locked value. New struct will be in the following format:

```shell
 typedef struct {
+  uint32_t clk;
   uint32_t min_clk;
   uint32_t max_clk;
+  uint8_t clk_locked;
+  uint8_t clk_deep_sleep;
   uint32_t reserved[4];
 } amdsmi_clk_info_t;
```

- **Multiple structure updates in amdsmi.h and amdsmi_interface.py to align with host/guest**.  
Multiple structures used by APIs were changed for alignment unification:
  - Changed `amdsmi_vram_info_t` `vram_size_mb` field changed to to `vram_size`
  - Updated `amdsmi_vram_type_t` struct updated to include new enums and added `AMDSMI` prefix
  - Updated `amdsmi_status_t` some enums were missing the `AMDSMI_STATUS` prefix
  - Added `AMDSMI_PROCESSOR_TYPE` prefix to `processor_type_t` enums
  - Removed the fields structure definition in favor for an anonymous definition in `amdsmi_bdf_t`

- **Added `AMDSMI` prefix in amdsmi.h and amdsmi_interface.py to align with host/guest**.  
Multiple structures used by APIs were changed for alignment unification. `AMDSMI` prefix was added to the following structures:
  - Added AMDSMI prefix to `amdsmi_container_types_t` enums
  - Added AMDSMI prefix to `amdsmi_clk_type_t` enums
  - Added AMDSMI prefix to `amdsmi_compute_partition_type_t` enums
  - Added AMDSMI prefix to `amdsmi_memory_partition_type_t` enums
  - Added AMDSMI prefix to `amdsmi_clk_type_t` enums
  - Added AMDSMI prefix to `amdsmi_temperature_type_t` enums
  - Added AMDSMI prefix to `amdsmi_fw_block_t` enums

- **Changed dpm_policy references to soc_pstate**.  
The file structure referenced to dpm_policy changed to soc_pstate and we have changed the APIs and CLI tool to be inline with the current structure. `amdsmi_get_dpm_policy()` and `amdsmi_set_dpm_policy()` is no longer valid with the new API being `amdsmi_get_soc_pstate()` and `amdsmi_set_soc_pstate()`. The CLI tool has been changed from `--policy` to `--soc-pstate`

- **Updated `amdsmi_get_gpu_board_info()` product_name to fallback to pciids**.  
Previously on devices without a FRU we would not populate the product name in the `amdsmi_board_info_t` structure, now we will fallback to using the name listed according to the pciids file if available.

- **Updated CLI voltage curve command output**.  
The output for `amd-smi metric --voltage-curve` now splits the frequency and voltage output by curve point or outputs N/A for each curve point if not applicable

```shell
GPU: 0
    VOLTAGE_CURVE:
        POINT_0_FREQUENCY: 872 Mhz
        POINT_0_VOLTAGE: 736 mV
        POINT_1_FREQUENCY: 1354 Mhz
        POINT_1_VOLTAGE: 860 mV
        POINT_2_FREQUENCY: 1837 Mhz
        POINT_2_VOLTAGE: 1186 mV
```

- **Updated `amdsmi_get_gpu_board_info()` now has larger structure sizes for `amdsmi_board_info_t`**.  
Updated sizes that work for retrieving relevant board information across AMD's
ASIC products. This requires users to update any ABIs using this structure.

### Resolved issues

- **Fixed Leftover Mutex deadlock when running multiple instances of the CLI tool**.  
When running `amd-smi reset --gpureset --gpu all` and then running an instance of `amd-smi static` (or any other subcommand that access the GPUs) a mutex would lock and not return requiring either a clear of the mutex in /dev/shm or rebooting the machine.

- **Fixed multiple processes not being registered in `amd-smi process` with json and csv format**.  
Multiple process outputs in the CLI tool were not being registered correctly. The json output did not handle multiple processes and is now in a new valid json format:

```shell
[
    {
        "gpu": 0,
        "process_list": [
            {
                "process_info": {
                    "name": "TransferBench",
                    "pid": 420157,
                    "mem_usage": {
                        "value": 0,
                        "unit": "B"
                    }
                }
            },
            {
                "process_info": {
                    "name": "rvs",
                    "pid": 420315,
                    "mem_usage": {
                        "value": 0,
                        "unit": "B"
                    }
                }
            }
        ]
    }
]
```

- **Removed `throttle-status` from `amd-smi monitor` as it is no longer reliably supported**.  
Throttle status may work for older ASICs, but will be replaced with PVIOL and TVIOL metrics for future ASIC support. It remains a field in the gpu_metrics API and in `amd-smi metric --power`.

- **`amdsmi_get_gpu_board_info()` no longer returns junk char strings**.  
Previously if there was a partial failure to retrieve character strings, we would return
garbage output to users using the API. This fix intends to populate as many values as possible.
Then any failure(s) found along the way, `\0` is provided to `amdsmi_board_info_t`
structures data members which cannot be populated. Ensuring empty char string values.

- **Fixed parsing of `pp_od_clk_voltage` within `amdsmi_get_gpu_od_volt_info`**.  
The parsing of `pp_od_clk_voltage` was not dynamic enough to work with the dropping of voltage curve support on MI series cards. This propagates down to correcting the CLI's output `amd-smi metric --voltage-curve` to N/A if voltage curve is not enabled.

### Known issues

- **`amdsmi_get_gpu_process_isolation` and `amdsmi_clean_gpu_local_data` commands do no currently work and will be supported in a future release**.  

## amd_smi_lib for ROCm 6.1.2

### Added

- **Added process isolation and clean shader APIs and CLI commands**.  
Added APIs CLI and APIs to address LeftoverLocals security issues. Allowing clearing the sram data and setting process isolation on a per GPU basis. New APIs:
  - `amdsmi_get_gpu_process_isolation()`
  - `amdsmi_set_gpu_process_isolation()`
  - `amdsmi_set_gpu_clear_sram_data()`

- **Added `MIN_POWER` to output of `amd-smi static --limit`**.  
This change helps users identify the range to which they can change the power cap of the GPU. The change is added to simplify why a device supports (or does not support) power capping (also known as overdrive). See `amd-smi set -g all --power-cap <value in W>` or `amd-smi reset -g all --power-cap`.

```shell
$ amd-smi static --limit
GPU: 0
    LIMIT:
        MAX_POWER: 203 W
        MIN_POWER: 0 W
        SOCKET_POWER: 203 W
        SLOWDOWN_EDGE_TEMPERATURE: 100 °C
        SLOWDOWN_HOTSPOT_TEMPERATURE: 110 °C
        SLOWDOWN_VRAM_TEMPERATURE: 100 °C
        SHUTDOWN_EDGE_TEMPERATURE: 105 °C
        SHUTDOWN_HOTSPOT_TEMPERATURE: 115 °C
        SHUTDOWN_VRAM_TEMPERATURE: 105 °C

GPU: 1
    LIMIT:
        MAX_POWER: 213 W
        MIN_POWER: 213 W
        SOCKET_POWER: 213 W
        SLOWDOWN_EDGE_TEMPERATURE: 109 °C
        SLOWDOWN_HOTSPOT_TEMPERATURE: 110 °C
        SLOWDOWN_VRAM_TEMPERATURE: 100 °C
        SHUTDOWN_EDGE_TEMPERATURE: 114 °C
        SHUTDOWN_HOTSPOT_TEMPERATURE: 115 °C
        SHUTDOWN_VRAM_TEMPERATURE: 105 °C
```

### Optimized

- **Updated `amd-smi monitor --pcie` output**.  
The source for pcie bandwidth monitor output was a legacy file we no longer support and was causing delays within the monitor command. The output is no longer using TX/RX but instantaneous bandwidth from gpu_metrics instead; updated output:

```shell
$ amd-smi monitor --pcie
GPU   PCIE_BW
  0   26 Mb/s
```

- **`amdsmi_get_power_cap_info` now returns values in uW instead of W**.  
`amdsmi_get_power_cap_info` will return in uW as originally reflected by driver. Previously `amdsmi_get_power_cap_info` returned W values, this conflicts with our sets and modifies values retrieved from driver. We decided to keep the values returned from driver untouched (in original units, uW). Then in CLI we will convert to watts (as previously done - no changes here). Additionally, driver made updates to min power cap displayed for devices when overdrive is disabled which prompted for this change (in this case min_power_cap and max_power_cap are the same).

- **Updated Python Library return types for amdsmi_get_gpu_memory_reserved_pages & amdsmi_get_gpu_bad_page_info**.  
Previously calls were returning "No bad pages found." if no pages were found, now it only returns the list type and can be empty.

- **Updated `amd-smi metric --ecc-blocks` output**.  
The ecc blocks argument was outputting blocks without counters available, updated the filtering show blocks that counters are available for:

``` shell
$ amd-smi metric --ecc-block
GPU: 0
    ECC_BLOCKS:
        UMC:
            CORRECTABLE_COUNT: 0
            UNCORRECTABLE_COUNT: 0
            DEFERRED_COUNT: 0
        SDMA:
            CORRECTABLE_COUNT: 0
            UNCORRECTABLE_COUNT: 0
            DEFERRED_COUNT: 0
        GFX:
            CORRECTABLE_COUNT: 0
            UNCORRECTABLE_COUNT: 0
            DEFERRED_COUNT: 0
        MMHUB:
            CORRECTABLE_COUNT: 0
            UNCORRECTABLE_COUNT: 0
            DEFERRED_COUNT: 0
        PCIE_BIF:
            CORRECTABLE_COUNT: 0
            UNCORRECTABLE_COUNT: 0
            DEFERRED_COUNT: 0
        HDP:
            CORRECTABLE_COUNT: 0
            UNCORRECTABLE_COUNT: 0
            DEFERRED_COUNT: 0
        XGMI_WAFL:
            CORRECTABLE_COUNT: 0
            UNCORRECTABLE_COUNT: 0
            DEFERRED_COUNT: 0
```

- **Removed `amdsmi_get_gpu_process_info` from Python library**.  
amdsmi_get_gpu_process_info was removed from the C library in an earlier build, but the API was still in the Python interface.

### Resolved issues

- **Fixed `amd-smi metric --power` now provides power output for Navi2x/Navi3x/MI1x**.  
These systems use an older version of gpu_metrics in amdgpu. This fix only updates what CLI outputs.
No change in any of our APIs.

```shell
$ amd-smi metric --power
GPU: 0
    POWER:
        SOCKET_POWER: 11 W
        GFX_VOLTAGE: 768 mV
        SOC_VOLTAGE: 925 mV
        MEM_VOLTAGE: 1250 mV
        POWER_MANAGEMENT: ENABLED
        THROTTLE_STATUS: UNTHROTTLED

GPU: 1
    POWER:
        SOCKET_POWER: 17 W
        GFX_VOLTAGE: 781 mV
        SOC_VOLTAGE: 806 mV
        MEM_VOLTAGE: 1250 mV
        POWER_MANAGEMENT: ENABLED
        THROTTLE_STATUS: UNTHROTTLED
```

- **Fixed `amdsmitstReadWrite.TestPowerCapReadWrite` test for Navi3X, Navi2X, MI100**.  
Updates required `amdsmi_get_power_cap_info` to return in uW as originally reflected by driver. Previously `amdsmi_get_power_cap_info` returned W values, this conflicts with our sets and modifies values retrieved from driver. We decided to keep the values returned from driver untouched (in original units, uW). Then in CLI we will convert to watts (as previously done - no changes here). Additionally, driver made updates to min power cap displayed for devices when overdrive is disabled which prompted for this change (in this case min_power_cap and max_power_cap are the same).

- **Fixed Python interface call amdsmi_get_gpu_memory_reserved_pages & amdsmi_get_gpu_bad_page_info**.  
Previously Python interface calls to populated bad pages resulted in a `ValueError: NULL pointer access`. This fixes the bad-pages subcommand CLI  subcommand as well.

## amd_smi_lib for ROCm 6.1.1

### Changed

- **Updated metrics --clocks**.  
Output for `amd-smi metric --clock` is updated to reflect each engine and bug fixes for the clock lock status and deep sleep status.

``` shell
$ amd-smi metric --clock
GPU: 0
    CLOCK:
        GFX_0:
            CLK: 113 MHz
            MIN_CLK: 500 MHz
            MAX_CLK: 1800 MHz
            CLK_LOCKED: DISABLED
            DEEP_SLEEP: ENABLED
        GFX_1:
            CLK: 113 MHz
            MIN_CLK: 500 MHz
            MAX_CLK: 1800 MHz
            CLK_LOCKED: DISABLED
            DEEP_SLEEP: ENABLED
        GFX_2:
            CLK: 112 MHz
            MIN_CLK: 500 MHz
            MAX_CLK: 1800 MHz
            CLK_LOCKED: DISABLED
            DEEP_SLEEP: ENABLED
        GFX_3:
            CLK: 113 MHz
            MIN_CLK: 500 MHz
            MAX_CLK: 1800 MHz
            CLK_LOCKED: DISABLED
            DEEP_SLEEP: ENABLED
        GFX_4:
            CLK: 113 MHz
            MIN_CLK: 500 MHz
            MAX_CLK: 1800 MHz
            CLK_LOCKED: DISABLED
            DEEP_SLEEP: ENABLED
        GFX_5:
            CLK: 113 MHz
            MIN_CLK: 500 MHz
            MAX_CLK: 1800 MHz
            CLK_LOCKED: DISABLED
            DEEP_SLEEP: ENABLED
        GFX_6:
            CLK: 113 MHz
            MIN_CLK: 500 MHz
            MAX_CLK: 1800 MHz
            CLK_LOCKED: DISABLED
            DEEP_SLEEP: ENABLED
        GFX_7:
            CLK: 113 MHz
            MIN_CLK: 500 MHz
            MAX_CLK: 1800 MHz
            CLK_LOCKED: DISABLED
            DEEP_SLEEP: ENABLED
        MEM_0:
            CLK: 900 MHz
            MIN_CLK: 900 MHz
            MAX_CLK: 1200 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: DISABLED
        VCLK_0:
            CLK: 29 MHz
            MIN_CLK: 914 MHz
            MAX_CLK: 1480 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: ENABLED
        VCLK_1:
            CLK: 29 MHz
            MIN_CLK: 914 MHz
            MAX_CLK: 1480 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: ENABLED
        VCLK_2:
            CLK: 29 MHz
            MIN_CLK: 914 MHz
            MAX_CLK: 1480 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: ENABLED
        VCLK_3:
            CLK: 29 MHz
            MIN_CLK: 914 MHz
            MAX_CLK: 1480 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: ENABLED
        DCLK_0:
            CLK: 22 MHz
            MIN_CLK: 711 MHz
            MAX_CLK: 1233 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: ENABLED
        DCLK_1:
            CLK: 22 MHz
            MIN_CLK: 711 MHz
            MAX_CLK: 1233 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: ENABLED
        DCLK_2:
            CLK: 22 MHz
            MIN_CLK: 711 MHz
            MAX_CLK: 1233 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: ENABLED
        DCLK_3:
            CLK: 22 MHz
            MIN_CLK: 711 MHz
            MAX_CLK: 1233 MHz
            CLK_LOCKED: N/A
            DEEP_SLEEP: ENABLED
```

- **Added deferred ecc counts**.  
Added deferred error correctable counts to `amd-smi metric --ecc --ecc-blocks`

```shell
$ amd-smi metric --ecc --ecc-blocks
GPU: 0
    ECC:
        TOTAL_CORRECTABLE_COUNT: 0
        TOTAL_UNCORRECTABLE_COUNT: 0
        TOTAL_DEFERRED_COUNT: 0
        CACHE_CORRECTABLE_COUNT: 0
        CACHE_UNCORRECTABLE_COUNT: 0
    ECC_BLOCKS:
        UMC:
            CORRECTABLE_COUNT: 0
            UNCORRECTABLE_COUNT: 0
            DEFERRED_COUNT: 0
        SDMA:
            CORRECTABLE_COUNT: 0
            UNCORRECTABLE_COUNT: 0
            DEFERRED_COUNT: 0
        ...
```

- **Updated `amd-smi topology --json` to align with host/guest**.  
Topology's `--json` output now is changed to align with output host/guest systems. Additionally, users can select/filter specific topology details as desired (refer to `amd-smi topology -h` for full list). See examples shown below.

*Previous format:*

```shell
$ amd-smi topology --json
[
    {
        "gpu": 0,
        "link_accessibility": {
            "gpu_0": "ENABLED",
            "gpu_1": "DISABLED"
        },
        "weight": {
            "gpu_0": 0,
            "gpu_1": 40
        },
        "hops": {
            "gpu_0": 0,
            "gpu_1": 2
        },
        "link_type": {
            "gpu_0": "SELF",
            "gpu_1": "PCIE"
        },
        "numa_bandwidth": {
            "gpu_0": "N/A",
            "gpu_1": "N/A"
        }
    },
    {
        "gpu": 1,
        "link_accessibility": {
            "gpu_0": "DISABLED",
            "gpu_1": "ENABLED"
        },
        "weight": {
            "gpu_0": 40,
            "gpu_1": 0
        },
        "hops": {
            "gpu_0": 2,
            "gpu_1": 0
        },
        "link_type": {
            "gpu_0": "PCIE",
            "gpu_1": "SELF"
        },
        "numa_bandwidth": {
            "gpu_0": "N/A",
            "gpu_1": "N/A"
        }
    }
]
```

*New format:*

```shell
$ amd-smi topology --json
[
    {
        "gpu": 0,
        "bdf": "0000:01:00.0",
        "links": [
            {
                "gpu": 0,
                "bdf": "0000:01:00.0",
                "weight": 0,
                "link_status": "ENABLED",
                "link_type": "SELF",
                "num_hops": 0,
                "bandwidth": "N/A",
            },
            {
                "gpu": 1,
                "bdf": "0001:01:00.0",
                "weight": 15,
                "link_status": "ENABLED",
                "link_type": "XGMI",
                "num_hops": 1,
                "bandwidth": "50000-100000",
            },
        ...
        ]
    },
    ...
]
```

```shell
$ /opt/rocm/bin/amd-smi topology -a -t --json
[
    {
        "gpu": 0,
        "bdf": "0000:08:00.0",
        "links": [
            {
                "gpu": 0,
                "bdf": "0000:08:00.0",
                "link_status": "ENABLED",
                "link_type": "SELF"
            },
            {
                "gpu": 1,
                "bdf": "0000:44:00.0",
                "link_status": "DISABLED",
                "link_type": "PCIE"
            }
        ]
    },
    {
        "gpu": 1,
        "bdf": "0000:44:00.0",
        "links": [
            {
                "gpu": 0,
                "bdf": "0000:08:00.0",
                "link_status": "DISABLED",
                "link_type": "PCIE"
            },
            {
                "gpu": 1,
                "bdf": "0000:44:00.0",
                "link_status": "ENABLED",
                "link_type": "SELF"
            }
        ]
    }
]
```

### Resolved issues

- **Fix for GPU reset error on non-amdgpu cards**.  
Previously our reset could attempting to reset non-amd GPUS- resulting in "Unable to reset non-amd GPU" error. Fix
updates CLI to target only AMD ASICs.

- **Fix for `amd-smi static --pcie` and `amdsmi_get_pcie_info()` Navi32/31 cards**.  
Updated API to include `amdsmi_card_form_factor_t.AMDSMI_CARD_FORM_FACTOR_CEM`. Previously, this would report "UNKNOWN". This fix
provides the correct board `SLOT_TYPE` associated with these ASICs (and other Navi cards).

- **Fix for `amd-smi process`**.  
Fixed output results when getting processes running on a device.

- **Improved Error handling for `amd-smi process`**.  
Fixed Attribute Error when getting process in csv format

### Known issues

- `amd-smi bad-pages` can results with "ValueError: NULL pointer access" with certain PM FW versions.

## amd_smi_lib for ROCm 6.1.0

### Added

- **Added Monitor Command**.  
Provides users the ability to customize GPU metrics to capture, collect, and observe. Output is provided in a table view. This aligns closer to ROCm SMI `rocm-smi` (no argument), additionally allows users to customize what data is helpful for their use-case.

```shell
$ amd-smi monitor -h
usage: amd-smi monitor [-h] [--json | --csv] [--file FILE] [--loglevel LEVEL]
                       [-g GPU [GPU ...] | -U CPU [CPU ...] | -O CORE [CORE ...]]
                       [-w INTERVAL] [-W TIME] [-i ITERATIONS] [-p] [-t] [-u] [-m] [-n]
                       [-d] [-s] [-e] [-v] [-r]

Monitor a target device for the specified arguments.
If no arguments are provided, all arguments will be enabled.
Use the watch arguments to run continuously

Monitor Arguments:
  -h, --help                   show this help message and exit
  -g, --gpu GPU [GPU ...]      Select a GPU ID, BDF, or UUID from the possible choices:
                               ID: 0 | BDF: 0000:01:00.0 | UUID: <redacted>
                                 all | Selects all devices
  -U, --cpu CPU [CPU ...]      Select a CPU ID from the possible choices:
                               ID: 0
                                 all | Selects all devices
  -O, --core CORE [CORE ...]   Select a Core ID from the possible choices:
                               ID: 0 - 23
                                 all  | Selects all devices
  -w, --watch INTERVAL         Reprint the command in a loop of INTERVAL seconds
  -W, --watch_time TIME        The total TIME to watch the given command
  -i, --iterations ITERATIONS  Total number of ITERATIONS to loop on the given command
  -p, --power-usage            Monitor power usage in Watts
  -t, --temperature            Monitor temperature in Celsius
  -u, --gfx                    Monitor graphics utilization (%) and clock (MHz)
  -m, --mem                    Monitor memory utilization (%) and clock (MHz)
  -n, --encoder                Monitor encoder utilization (%) and clock (MHz)
  -d, --decoder                Monitor decoder utilization (%) and clock (MHz)
  -s, --throttle-status        Monitor thermal throttle status
  -e, --ecc                    Monitor ECC single bit, ECC double bit, and PCIe replay error counts
  -v, --vram-usage             Monitor memory usage in MB
  -r, --pcie                   Monitor PCIe Tx/Rx in MB/s

Command Modifiers:
  --json                       Displays output in JSON format (human readable by default).
  --csv                        Displays output in CSV format (human readable by default).
  --file FILE                  Saves output into a file on the provided path (stdout by default).
  --loglevel LEVEL             Set the logging level from the possible choices:
                                DEBUG, INFO, WARNING, ERROR, CRITICAL
```

```shell
$ amd-smi monitor -ptumv
GPU  POWER  GPU_TEMP  MEM_TEMP  GFX_UTIL  GFX_CLOCK  MEM_UTIL  MEM_CLOCK  VRAM_USED  VRAM_TOTAL
  0  171 W     32 °C     33 °C       0 %    114 MHz       0 %    900 MHz     283 MB   196300 MB
  1  175 W     33 °C     34 °C       0 %    113 MHz       0 %    900 MHz     283 MB   196300 MB
  2  177 W     31 °C     33 °C       0 %    113 MHz       0 %    900 MHz     283 MB   196300 MB
  3  172 W     33 °C     32 °C       0 %    113 MHz       0 %    900 MHz     283 MB   196300 MB
  4  178 W     32 °C     32 °C       0 %    113 MHz       0 %    900 MHz     284 MB   196300 MB
  5  176 W     33 °C     35 °C       0 %    113 MHz       0 %    900 MHz     283 MB   196300 MB
  6  176 W     32 °C     32 °C       0 %    113 MHz       0 %    900 MHz     283 MB   196300 MB
  7  175 W     34 °C     32 °C       0 %    113 MHz       0 %    900 MHz     283 MB   196300 MB
```

- **Integrated ESMI Tool**.  
Users can get CPU metrics and telemetry through our API and CLI tools. This information can be seen in `amd-smi static` and `amd-smi metric` commands. Only available for limited target processors. As of ROCm 6.0.2, this is listed as:
  - AMD Zen3 based CPU Family 19h Models 0h-Fh and 30h-3Fh
  - AMD Zen4 based CPU Family 19h Models 10h-1Fh and A0-AFh

  See a few examples listed below.

```shell
$ amd-smi static -U all
CPU: 0
    SMU:
        FW_VERSION: 85.90.0
    INTERFACE_VERSION:
        PROTO VERSION: 6
```

```shell
$ amd-smi metric -O 0 1 2
CORE: 0
    BOOST_LIMIT:
        VALUE: 400 MHz
    CURR_ACTIVE_FREQ_CORE_LIMIT:
        VALUE: 400 MHz
    CORE_ENERGY:
        VALUE: N/A

CORE: 1
    BOOST_LIMIT:
        VALUE: 400 MHz
    CURR_ACTIVE_FREQ_CORE_LIMIT:
        VALUE: 400 MHz
    CORE_ENERGY:
        VALUE: N/A

CORE: 2
    BOOST_LIMIT:
        VALUE: 400 MHz
    CURR_ACTIVE_FREQ_CORE_LIMIT:
        VALUE: 400 MHz
    CORE_ENERGY:
        VALUE: N/A
```

```shell
$ amd-smi metric -U all
CPU: 0
    POWER_METRICS:
        SOCKET POWER: 102675 mW
        SOCKET POWER LIMIT: 550000 mW
        SOCKET MAX POWER LIMIT: 550000 mW
    PROCHOT:
        PROCHOT_STATUS: 0
    FREQ_METRICS:
        FCLKMEMCLK:
            FCLK: 2000 MHz
            MCLK: 1300 MHz
        CCLKFREQLIMIT: 400 MHz
        SOC_CURRENT_ACTIVE_FREQ_LIMIT:
            FREQ: 400 MHz
            FREQ_SRC: [HSMP Agent]
        SOC_FREQ_RANGE:
            MAX_SOCKET_FREQ: 3700 MHz
            MIN_SOCKET_FREQ: 400 MHz
    C0_RESIDENCY:
        RESIDENCY: 4 %
    SVI_TELEMETRY_ALL_RAILS:
        POWER: 102673 mW
    METRIC_VERSION:
        VERSION: 11
    METRICS_TABLE:
        CPU_FAMILY: 25
        CPU_MODEL: 144
        RESPONSE:
            MTBL_ACCUMULATION_COUNTER: 2887162626
            MTBL_MAX_SOCKET_TEMPERATURE: 41.0 °C
            MTBL_MAX_VR_TEMPERATURE: 39.0 °C
            MTBL_MAX_HBM_TEMPERATURE: 40.0 °C
            MTBL_MAX_SOCKET_TEMPERATURE_ACC: 108583340881.125 °C
            MTBL_MAX_VR_TEMPERATURE_ACC: 109472702595.0 °C
            MTBL_MAX_HBM_TEMPERATURE_ACC: 111516663941.0 °C
            MTBL_SOCKET_POWER_LIMIT: 550.0 W
            MTBL_MAX_SOCKET_POWER_LIMIT: 550.0 W
            MTBL_SOCKET_POWER: 102.678 W
            MTBL_TIMESTAMP_RAW: 288731677361880
            MTBL_TIMESTAMP_READABLE: Tue Mar 19 12:32:21 2024
            MTBL_SOCKET_ENERGY_ACC: 166127.84 kJ
            MTBL_CCD_ENERGY_ACC: 3317.837 kJ
            MTBL_XCD_ENERGY_ACC: 21889.147 kJ
            MTBL_AID_ENERGY_ACC: 121932.397 kJ
            MTBL_HBM_ENERGY_ACC: 18994.108 kJ
            MTBL_CCLK_FREQUENCY_LIMIT: 3.7 GHz
            MTBL_GFXCLK_FREQUENCY_LIMIT: 0.0 MHz
            MTBL_FCLK_FREQUENCY: 1999.988 MHz
            MTBL_UCLK_FREQUENCY: 1299.993 MHz
            MTBL_SOCCLK_FREQUENCY: [35.716, 35.715, 35.714, 35.714] MHz
            MTBL_VCLK_FREQUENCY: [0.0, 53.749, 53.749, 53.749] MHz
            MTBL_DCLK_FREQUENCY: [7.143, 44.791, 44.791, 44.791] MHz
            MTBL_LCLK_FREQUENCY: [20.872, 18.75, 35.938, 599.558] MHz
            MTBL_FCLK_FREQUENCY_TABLE: [1200.0, 1600.0, 1900.0, 2000.0] MHz
            MTBL_UCLK_FREQUENCY_TABLE: [900.0, 1100.0, 1200.0, 1300.0] MHz
            MTBL_SOCCLK_FREQUENCY_TABLE: [800.0, 1000.0, 1142.857, 1142.857] MHz
            MTBL_VCLK_FREQUENCY_TABLE: [914.286, 1300.0, 1560.0, 1720.0] MHz
            MTBL_DCLK_FREQUENCY_TABLE: [711.111, 975.0, 1300.0, 1433.333] MHz
            MTBL_LCLK_FREQUENCY_TABLE: [600.0, 844.444, 1150.0, 1150.0] MHz
            MTBL_CCLK_FREQUENCY_ACC: [4399751656.639, 4399751656.639, 4399751656.639, 4399751656.639,
                4399751656.639, 4399751656.639, 4399751656.639, 4399751656.639, 4399751656.639,
                4399751656.639, 4399751656.639, 4399751656.639, 4399751656.639, 4399751656.639,
                4399751656.639, 4399751656.639, 4399751656.639, 4399751656.639, 4399751656.639,
                4399751656.639, 4399751656.639, 4399751656.639, 4399751656.639, 4399751656.639,
                0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0,
                0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0,
                0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0,
                0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0,
                0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0] GHz
            MTBL_GFXCLK_FREQUENCY_ACC: [0.0, 0.0, 250534397827.603, 251546257401.82, 250811364089.836,
                249999070486.505, 251622633562.855, 251342375116.05] MHz
            MTBL_GFXCLK_FREQUENCY: [0.0, 0.0, 31.091, 31.414, 31.141, 31.478, 31.32, 31.453]
                MHz
            MTBL_MAX_CCLK_FREQUENCY: 3.7 GHz
            MTBL_MIN_CCLK_FREQUENCY: 0.4 GHz
            MTBL_MAX_GFXCLK_FREQUENCY: 2100.0 MHz
            MTBL_MIN_GFXCLK_FREQUENCY: 500.0 MHz
            MTBL_MAX_LCLK_DPM_RANGE: 2
            MTBL_MIN_LCLK_DPM_RANGE: 0
            MTBL_XGMI_WIDTH: 0.0
            MTBL_XGMI_BITRATE: 0.0 Gbps
            MTBL_XGMI_READ_BANDWIDTH_ACC: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0] Gbps
            MTBL_XGMI_WRITE_BANDWIDTH_ACC: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0] Gbps
            MTBL_SOCKET_C0_RESIDENCY: 4.329 %
            MTBL_SOCKET_GFX_BUSY: 0.0 %
            MTBL_HBM_BANDWIDTH_UTILIZATION: 0.001 %
            MTBL_SOCKET_C0_RESIDENCY_ACC: 311523106.34
            MTBL_SOCKET_GFX_BUSY_ACC: 84739.281
            MTBL_HBM_BANDWIDTH_ACC: 33231180.073 Gbps
            MTBL_MAX_HBM_BANDWIDTH: 5324.801 Gbps
            MTBL_DRAM_BANDWIDTH_UTILIZATION_ACC: 612843.699
            MTBL_PCIE_BANDWIDTH_ACC: [0.0, 0.0, 0.0, 0.0] Gbps
            MTBL_PROCHOT_RESIDENCY_ACC: 0
            MTBL_PPT_RESIDENCY_ACC: 2887162626
            MTBL_SOCKET_THM_RESIDENCY_ACC: 2887162626
            MTBL_VR_THM_RESIDENCY_ACC: 0
            MTBL_HBM_THM_RESIDENCY_ACC: 2887162626
    SOCKET_ENERGY:
        RESPONSE: N/A
    DDR_BANDWIDTH:
        RESPONSE: N/A
    CPU_TEMP:
        RESPONSE: N/A
```

- **Added support for new metrics: VCN, JPEG engines, and PCIe errors**.  
Using the AMD SMI tool, users can retrieve VCN, JPEG engines, and PCIe errors by calling `amd-smi metric -P` or `amd-smi metric --usage`. Depending on device support, `VCN_ACTIVITY` will update for MI3x ASICs (with 4 separate VCN engine activities) for older asics `MM_ACTIVITY` with UVD/VCN engine activity (average of all engines). `JPEG_ACTIVITY` is a new field for MI3x ASICs, where device can support up to 32 JPEG engine activities. See our documentation for more in-depth understanding of these new fields.

```shell
$ amd-smi metric -P
GPU: 0
    PCIE:
        WIDTH: 16
        SPEED: 16 GT/s
        REPLAY_COUNT: 0
        L0_TO_RECOVERY_COUNT: 1
        REPLAY_ROLL_OVER_COUNT: 0
        NAK_SENT_COUNT: 0
        NAK_RECEIVED_COUNT: 0
        CURRENT_BANDWIDTH_SENT: N/A
        CURRENT_BANDWIDTH_RECEIVED: N/A
        MAX_PACKET_SIZE: N/A
```

```shell
$ amd-smi metric --usage
GPU: 0
    USAGE:
        GFX_ACTIVITY: 0 %
        UMC_ACTIVITY: 0 %
        MM_ACTIVITY: N/A
        VCN_ACTIVITY: [0 %, 0 %, 0 %, 0 %]
        JPEG_ACTIVITY: [0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0
            %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %, 0 %,
            0 %, 0 %, 0 %, 0 %]

```

- **Added AMDSMI Tool Version**.  
AMD SMI will report ***three versions***: AMDSMI Tool, AMDSMI Library version, and ROCm version.
The AMDSMI Tool version is the CLI/tool version number with commit ID appended after `+` sign.
The AMDSMI Library version is the library package version number.
The ROCm version is the system's installed ROCm version, if ROCm is not installed it will report N/A.

```shell
$ amd-smi version
AMDSMI Tool: 23.4.2+505b858 | AMDSMI Library version: 24.2.0.0 | ROCm version: 6.1.0
```

- **Added XGMI table**.  
Displays XGMI information for AMD GPU devices in a table format. Only available on supported ASICs (eg. MI300). Here users can view read/write data XGMI or PCIe accumulated data transfer size (in KiloBytes).

```shell
$ amd-smi xgmi
LINK METRIC TABLE:
       bdf          bit_rate max_bandwidth link_type 0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
GPU0   0000:0c:00.0 32 Gb/s  512 Gb/s      XGMI
 Read                                                N/A          2 KB         2 KB         1 KB         2 KB         1 KB         2 KB         2 KB
 Write                                               N/A          1 KB         1 KB         1 KB         1 KB         1 KB         1 KB         1 KB
GPU1   0000:22:00.0 32 Gb/s  512 Gb/s      XGMI
 Read                                                0 KB         N/A          2 KB         2 KB         1 KB         2 KB         1 KB         2 KB
 Write                                               0 KB         N/A          1 KB         1 KB         1 KB         1 KB         1 KB         1 KB
GPU2   0000:38:00.0 32 Gb/s  512 Gb/s      XGMI
 Read                                                0 KB         1 KB         N/A          2 KB         1 KB         2 KB         0 KB         0 KB
 Write                                               0 KB         1 KB         N/A          1 KB         1 KB         1 KB         1 KB         1 KB
GPU3   0000:5c:00.0 32 Gb/s  512 Gb/s      XGMI
 Read                                                0 KB         0 KB         2 KB         N/A          1 KB         0 KB         0 KB         2 KB
 Write                                               0 KB         1 KB         1 KB         N/A          1 KB         1 KB         1 KB         1 KB
GPU4   0000:9f:00.0 32 Gb/s  512 Gb/s      XGMI
 Read                                                0 KB         1 KB         0 KB         0 KB         N/A          2 KB         0 KB         2 KB
 Write                                               0 KB         1 KB         1 KB         1 KB         N/A          1 KB         1 KB         1 KB
GPU5   0000:af:00.0 32 Gb/s  512 Gb/s      XGMI
 Read                                                0 KB         2 KB         0 KB         0 KB         0 KB         N/A          2 KB         0 KB
 Write                                               0 KB         1 KB         1 KB         1 KB         1 KB         N/A          1 KB         1 KB
GPU6   0000:bf:00.0 32 Gb/s  512 Gb/s      XGMI
 Read                                                0 KB         0 KB         0 KB         0 KB         0 KB         0 KB         N/A          0 KB
 Write                                               0 KB         1 KB         1 KB         1 KB         1 KB         1 KB         N/A          1 KB
GPU7   0000:df:00.0 32 Gb/s  512 Gb/s      XGMI
 Read                                                0 KB         0 KB         0 KB         0 KB         0 KB         0 KB         0 KB         N/A
 Write                                               0 KB         1 KB         1 KB         1 KB         1 KB         1 KB         1 KB         N/A

```

- **Added units of measure to JSON output**.  
We added unit of measure to JSON/CSV `amd-smi metric`, `amd-smi static`, and `amd-smi monitor` commands.

Ex.

```shell
amd-smi metric -p --json
[
    {
        "gpu": 0,
        "power": {
            "socket_power": {
                "value": 10,
                "unit": "W"
            },
            "gfx_voltage": {
                "value": 6,
                "unit": "mV"
            },
            "soc_voltage": {
                "value": 918,
                "unit": "mV"
            },
            "mem_voltage": {
                "value": 1250,
                "unit": "mV"
            },
            "power_management": "ENABLED",
            "throttle_status": "UNTHROTTLED"
        }
    }
]
```

### Changed

- **Topology is now left-aligned with BDF of each device listed individual table's row/columns**.  
We provided each device's BDF for every table's row/columns, then left aligned data. We want AMD SMI Tool output to be easy to understand and digest for our users. Having users scroll up to find this information made it difficult to follow, especially for devices which have many devices associated with one ASIC.

```shell
$ amd-smi topology
ACCESS TABLE:
             0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
0000:0c:00.0 ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED
0000:22:00.0 ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED
0000:38:00.0 ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED
0000:5c:00.0 ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED
0000:9f:00.0 ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED
0000:af:00.0 ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED
0000:bf:00.0 ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED
0000:df:00.0 ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED      ENABLED

WEIGHT TABLE:
             0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
0000:0c:00.0 0            15           15           15           15           15           15           15
0000:22:00.0 15           0            15           15           15           15           15           15
0000:38:00.0 15           15           0            15           15           15           15           15
0000:5c:00.0 15           15           15           0            15           15           15           15
0000:9f:00.0 15           15           15           15           0            15           15           15
0000:af:00.0 15           15           15           15           15           0            15           15
0000:bf:00.0 15           15           15           15           15           15           0            15
0000:df:00.0 15           15           15           15           15           15           15           0

HOPS TABLE:
             0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
0000:0c:00.0 0            1            1            1            1            1            1            1
0000:22:00.0 1            0            1            1            1            1            1            1
0000:38:00.0 1            1            0            1            1            1            1            1
0000:5c:00.0 1            1            1            0            1            1            1            1
0000:9f:00.0 1            1            1            1            0            1            1            1
0000:af:00.0 1            1            1            1            1            0            1            1
0000:bf:00.0 1            1            1            1            1            1            0            1
0000:df:00.0 1            1            1            1            1            1            1            0

LINK TYPE TABLE:
             0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
0000:0c:00.0 SELF         XGMI         XGMI         XGMI         XGMI         XGMI         XGMI         XGMI
0000:22:00.0 XGMI         SELF         XGMI         XGMI         XGMI         XGMI         XGMI         XGMI
0000:38:00.0 XGMI         XGMI         SELF         XGMI         XGMI         XGMI         XGMI         XGMI
0000:5c:00.0 XGMI         XGMI         XGMI         SELF         XGMI         XGMI         XGMI         XGMI
0000:9f:00.0 XGMI         XGMI         XGMI         XGMI         SELF         XGMI         XGMI         XGMI
0000:af:00.0 XGMI         XGMI         XGMI         XGMI         XGMI         SELF         XGMI         XGMI
0000:bf:00.0 XGMI         XGMI         XGMI         XGMI         XGMI         XGMI         SELF         XGMI
0000:df:00.0 XGMI         XGMI         XGMI         XGMI         XGMI         XGMI         XGMI         SELF

NUMA BW TABLE:
             0000:0c:00.0 0000:22:00.0 0000:38:00.0 0000:5c:00.0 0000:9f:00.0 0000:af:00.0 0000:bf:00.0 0000:df:00.0
0000:0c:00.0 N/A          50000-50000  50000-50000  50000-50000  50000-50000  50000-50000  50000-50000  50000-50000
0000:22:00.0 50000-50000  N/A          50000-50000  50000-50000  50000-50000  50000-50000  50000-50000  50000-50000
0000:38:00.0 50000-50000  50000-50000  N/A          50000-50000  50000-50000  50000-50000  50000-50000  50000-50000
0000:5c:00.0 50000-50000  50000-50000  50000-50000  N/A          50000-50000  50000-50000  50000-50000  50000-50000
0000:9f:00.0 50000-50000  50000-50000  50000-50000  50000-50000  N/A          50000-50000  50000-50000  50000-50000
0000:af:00.0 50000-50000  50000-50000  50000-50000  50000-50000  50000-50000  N/A          50000-50000  50000-50000
0000:bf:00.0 50000-50000  50000-50000  50000-50000  50000-50000  50000-50000  50000-50000  N/A          50000-50000
0000:df:00.0 50000-50000  50000-50000  50000-50000  50000-50000  50000-50000  50000-50000  50000-50000  N/A
```

### Resolved issues

- **Fix for Navi3X/Navi2X/MI100 `amdsmi_get_gpu_pci_bandwidth()` in frequencies_read tests**.  
Devices which do not report (eg. Navi3X/Navi2X/MI100) we have added checks to confirm these devices return AMDSMI_STATUS_NOT_SUPPORTED. Otherwise, tests now display a return string.
- **Fix for devices which have an older pyyaml installed**.  
Platforms which are identified as having an older pyyaml version or pip, we no manually update both pip and pyyaml as needed. This corrects issues identified below. Fix impacts the following CLI commands:
  - `amd-smi list`
  - `amd-smi static`
  - `amd-smi firmware`
  - `amd-smi metric`
  - `amd-smi topology`

```shell
TypeError: dump_all() got an unexpected keyword argument 'sort_keys'
```

- **Fix for crash when user is not a member of video/render groups**.  
AMD SMI now uses same mutex handler for devices as rocm-smi. This helps avoid crashes when DRM/device data is inaccessible to the logged in user.

## amd_smi_lib for ROCm 6.0.0

### Added

- **Integrated the E-SMI (EPYC-SMI) library**.  
You can now query CPU-related information directly through AMD SMI. Metrics include power, energy, performance, and other system details.

- **Added support for gfx942 metrics**.  
You can now query MI300 device metrics to get real-time information. Metrics include power, temperature, energy, and performance.

- **Compute and memory partition support**.  
Users can now view, set, and reset partitions. The topology display can provide a more in-depth look at the device's current configuration.

### Changed

- **GPU index sorting made consistent with other tools**.  
To ensure alignment with other ROCm software tools, GPU index sorting is optimized to use Bus:Device.Function (BDF) rather than the card number.
- **Topology output is now aligned with GPU BDF table**.  
Earlier versions of the topology output were difficult to read since each GPU was displayed linearly.
Now the information is displayed as a table by each GPU's BDF, which closer resembles rocm-smi output.

### Optimized

- Updated to C++17, gtest-1.14, and cmake 3.14

### Resolved issues

- **Fix for driver not initialized**.  
If driver module is not loaded, user retrieve error response indicating amdgpu module is not loaded.
