30.30.2 AMD GPU Driver added (#6177)

* 30.30.2 AMD GPU Driver added

* Table formatting updated

* Vertial space optimized

* Table optimized

.readthedocs.yaml

@@ -20,3 +20,7 @@ build:
      - "doxygen"
      - "gfortran" # For pre-processing fortran sources
      - "graphviz" # For dot graphs in doxygen
+
+search:
+  ignore:
+    - "**/previous-versions/**"

README.md

@@ -1,49 +1,165 @@
-# AMD ROCm Software
+<div align="center">
+<img src="docs/data/amd-rocm-logo.png" width="200px" alt="ROCm logo">
+
+<h3 align="center">
+Open-source stack designed for GPU computation
+</h3>
+
+<p align="center">
+<a href="https://rocm.docs.amd.com/en/latest/"><b>Docs</b></a> • <a href="https://rocm.blogs.amd.com/"><b>Blogs</b></a> • <a href="https://rocm.docs.amd.com/projects/ai-developer-hub/en/latest/"><b>Tutorials</b></a> • <a href="https://rocm.docs.amd.com/en/latest/how-to/deep-learning-rocm.html"><b>Deep learning frameworks</b></a> • <a href="https://rocm.docs.amd.com/en/latest/how-to/rocm-for-ai/index.html"><b>ROCm for AI</b></a>
+</p>
+
+</div>
+
+# AMD ROCm™ software
 
 ROCm is an open-source stack, composed primarily of open-source software, designed for graphics
 processing unit (GPU) computation. ROCm consists of a collection of drivers, development tools, and
 APIs that enable GPU programming from low-level kernel to end-user applications.
 
-With ROCm, you can customize your GPU software to meet your specific needs. You can develop,
-collaborate, test, and deploy your applications in a free, open source, integrated, and secure software
+You can customize the ROCm software to meet your specific needs. You can develop,
+collaborate, test, and deploy your applications in a free, open-source, integrated, and secure software
 ecosystem. ROCm is particularly well-suited to GPU-accelerated high-performance computing (HPC),
-artificial intelligence (AI), scientific computing, and computer aided design (CAD).
+artificial intelligence (AI), scientific computing, and computer-aided design (CAD).
 
-ROCm is powered by AMD’s
-[HIP](https://github.com/ROCm/HIP),
-an open-source software C++ GPU programming environment and its corresponding runtime. HIP
-allows ROCm developers to create portable applications on different platforms by deploying code on a
-range of platforms, from dedicated gaming GPUs to exascale HPC clusters.
+ROCm is powered by [HIP](https://github.com/ROCm/rocm-systems/tree/develop/projects/hip),
+a C++ runtime API and kernel language for AMD GPUs. HIP allows developers to create portable
+applications by providing a programming interface that is similar to NVIDIA CUDA™.
 
-ROCm supports programming models, such as OpenMP and OpenCL, and includes all necessary open
-source software compilers, debuggers, and libraries. ROCm is fully integrated into machine learning
+ROCm supports programming models, such as OpenMP and OpenCL, and includes all necessary
+open-source software compilers, debuggers, and libraries. ROCm is fully integrated into machine learning
 (ML) frameworks, such as PyTorch and TensorFlow.
 
 > [!IMPORTANT]
-> A new open source build platform for ROCm is under development at
+> A new open-source build platform for ROCm is under development at
 > https://github.com/ROCm/TheRock, featuring a unified CMake build with bundled
-> dependencies, Windows support, and more.
+> dependencies, Microsoft Windows support, and more.
 
-## Getting and Building ROCm from Source
+## Table of contents
 
-Please use [TheRock](https://github.com/ROCm/TheRock) build system to build ROCm from source.
+- [Supported hardware and operating systems](#supported-hardware-and-operating-systems)
+- [Quick start](#quick-start)
+  - [Get started with ROCm](#get-started-with-rocm)
+  - [Get started with PyTorch on ROCm](#get-started-with-pytorch-on-rocm)
+- [Core components](#core-components)
+  - [Math libraries](#math-libraries)
+  - [ML and computer vision](#ml-and-computer-vision)
+  - [Collective communication and primitives](#collective-communication-and-primitives)
+  - [System management tools](#system-management-tools)
+  - [Profiling tools](#profiling-tools)
+  - [Development tools](#development-tools)
+  - [Runtimes and compilers](#runtimes-and-compilers)
+- [Release notes](#release-notes)
+- [Licenses](#licenses)
+- [ROCm release history](#rocm-release-history)
+- [Contribute](#contribute)
 
-## ROCm documentation
+---
 
-This repository contains the [manifest file](https://gerrit.googlesource.com/git-repo/+/HEAD/docs/manifest-format.md)
-for ROCm releases, changelogs, and release information.
+## Supported hardware and operating systems
 
-The `default.xml` file contains information for all repositories and the associated commit used to build
-the current ROCm release; `default.xml` uses the [Manifest Format repository](https://gerrit.googlesource.com/git-repo/).
+Use the [Compatibility matrix](https://rocm.docs.amd.com/projects/install-on-linux/en/latest/reference/system-requirements.html) for official support across ROCm versions, operating system kernels, and GPU architectures (CDNA/Instinct™, RDNA/Radeon™, and Radeon Pro). Recent releases cover Ubuntu, RHEL, SLES, Oracle Linux, Debian, Rocky Linux, and more. GPU targets include CDNA4, CDNA3, CDNA2, RDNA4, and RDNA3.
 
-Source code for our documentation is located in the `/docs` folder of most ROCm repositories. The
-`develop` branch of our repositories contains content for the next ROCm release.
+If you’re using AMD Radeon GPUs or Ryzen APUs in a workstation setting with a display connected, see the [ROCm on Radeon and Ryzen documentation](https://rocm.docs.amd.com/projects/radeon-ryzen/en/latest/index.html) for operating system/framework support and step-by-step installation instructions.
 
-The ROCm documentation homepage is [rocm.docs.amd.com](https://rocm.docs.amd.com).
+---
 
-For information on how to contribute to the ROCm documentation, see [Contributing to the ROCm documentation](https://rocm.docs.amd.com/en/latest/contribute/contributing.html).
+## Quick start
 
-## Older ROCm releases
+Follow these instructions to start using ROCm.
 
-For release information for older ROCm releases, refer to the
+### Get started with ROCm
+
+Follow the [ROCm installation guide](https://rocm.docs.amd.com/projects/install-on-linux/en/latest/install/quick-start.html) to install ROCm on your system.
+
+### Get started with PyTorch on ROCm
+
+Follow the [PyTorch on ROCm installation guide](https://rocm.docs.amd.com/projects/install-on-linux/en/latest/install/3rd-party/pytorch-install.html) to install PyTorch with ROCm support in a Docker environment.
+
+---
+
+## Core components
+
+The core ROCm stack consists of the following components:
+
+### Math libraries
+
+- [rocBLAS](https://github.com/ROCm/rocm-libraries/tree/develop/projects/rocblas), [hipBLAS](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipblas), and [hipBLASLt](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipblaslt)
+- [rocFFT](https://github.com/ROCm/rocm-libraries/tree/develop/projects/rocfft) and [hipFFT](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipfft)
+- [rocRAND](https://github.com/ROCm/rocm-libraries/tree/develop/projects/rocrand) and [hipRAND](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hiprand)
+- [rocSOLVER](https://github.com/ROCm/rocm-libraries/tree/develop/projects/rocsolver) and [hipSOLVER](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipsolver)
+- [rocSPARSE](https://github.com/ROCm/rocm-libraries/tree/develop/projects/rocsparse) and [hipSPARSE](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipsparse)
+- [rocWMMA](https://github.com/ROCm/rocm-libraries/tree/develop/projects/rocwmma) and [hipTensor](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hiptensor)
+
+### ML and computer vision
+
+- [Composable Kernel](https://github.com/ROCm/rocm-libraries/tree/develop/projects/composablekernel)
+- [MIGraphX](https://github.com/ROCm/AMDMIGraphX/)
+- [MIOpen](https://github.com/ROCm/rocm-libraries/tree/develop/projects/miopen)
+- [MIVisionX](https://github.com/ROCm/MIVisionX)
+- [ROCm Performance Primitives (RPP)](https://github.com/ROCm/rpp)
+
+### Collective communication and primitives
+
+- [hipCUB](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipcub)
+- [RCCL](https://github.com/ROCm/rocm-systems/tree/develop/projects/rccl)
+- [rocPRIM](https://github.com/ROCm/rocm-libraries/tree/develop/projects/rocprim)
+- [rocSHMEM](https://github.com/ROCm/rocm-systems/tree/develop/projects/rocshmem)
+- [rocThrust](https://github.com/ROCm/rocm-libraries/tree/develop/projects/rocthrust)
+
+### System management tools
+
+- [AMD SMI](https://github.com/ROCm/rocm-systems/tree/develop/projects/amdsmi)
+- [rocminfo](https://github.com/ROCm/rocm-systems/tree/develop/projects/rocminfo)
+
+### Profiling tools
+
+- [ROCprofiler-SDK](https://github.com/ROCm/rocm-systems/tree/develop/projects/rocprofiler-sdk)
+- [ROCm Compute Profiler](https://github.com/ROCm/rocm-systems/tree/develop/projects/rocprofiler-compute)
+
+### Development tools
+
+- [ROCm Debugger (ROCgdb)](https://github.com/ROCm/ROCgdb)
+- [ROCdbgapi](https://github.com/ROCm/rocm-systems/tree/develop/projects/rocdbgapi)
+
+### Runtimes and compilers
+
+- [HIP](https://github.com/ROCm/rocm-systems/tree/develop/projects/hip)
+- [LLVM](https://github.com/ROCm/llvm-project)
+- [ROCR Runtime (ROCR)](https://github.com/ROCm/rocm-systems/tree/develop/projects/rocr-runtime)
+
+For a complete list of ROCm components and version information, see the
+[ROCm components](https://rocm.docs.amd.com/en/latest/about/release-notes.html#rocm-components).
+
+---
+
+## Release notes
+
+- [Latest version of ROCm](https://rocm.docs.amd.com/en/latest/about/release-notes.html) - production
+- [ROCm 7.12.0](https://rocm.docs.amd.com/en/7.12.0-preview/about/release-notes.html) – preview stream
+
+---
+
+## Licenses
+
+- [ROCm licenses](https://rocm.docs.amd.com/en/latest/about/license.html)
+
+---
+
+## ROCm release history
+
+For information on older ROCm releases, see the
 [ROCm release history](https://rocm.docs.amd.com/en/latest/release/versions.html).
+
+---
+
+## Contribute
+
+AMD welcomes ROCm contributions using GitHub PRs or issues. See the links
+below for contribution guidelines.
+
+- [ROCm](CONTRIBUTING.md)
+- [TheRock](https://github.com/ROCm/TheRock/blob/main/CONTRIBUTING.md)
+- [ROCm documentation](https://rocm.docs.amd.com/en/latest/contribute/contributing.html)
+- [ROCm Systems](https://github.com/ROCm/rocm-systems/blob/develop/CONTRIBUTING.md)
+- [ROCm Libraries](https://github.com/ROCm/rocm-libraries/blob/develop/CONTRIBUTING.md)

RELEASE.md

@@ -10,15 +10,157 @@
 <!-- markdownlint-disable reference-links-images            -->
 <!-- markdownlint-disable no-missing-space-atx              -->
 <!-- spellcheck-disable                                     -->
-# ROCm 7.2.1 release notes
+
+# ROCm 7.2.2 release notes
+
+ROCm 7.2.2 is a quality release that resolves the issue listed in the Release highlights.
+
+## Release highlights
+
+The following are the notable changes in ROCm 7.2.2.
+
+### ROCTracer failure to report kernel operations is fixed
+
+In ROCm 7.2.1, applications using [ROCTracer](https://rocm.docs.amd.com/projects/roctracer/en/latest/index.html) failed to receive some or all kernel operation events due to a ROCTracer reporting failure. This issue has been resolved, and the fix has been applied to ROCTracer.
+
+### User space, driver, and firmware dependent changes
+
+The software for AMD Data Center GPU products requires maintaining a hardware
+and software stack with interdependencies among the GPU and baseboard
+firmware, AMD GPU drivers, and the ROCm user space software. While AMD publishes drivers and ROCm user space components, your server or infrastructure provider publishes the GPU and baseboard firmware by bundling AMD firmware releases via an AMD Platform Level Data Model (PLDM) bundle, which includes the Integrated Firmware Image (IFWI).
+
+GPU and baseboard firmware versioning might differ across GPU families.
+
+<div class="pst-scrollable-table-container">
+  <table class="table table--middle-left">
+    <thead>
+      <tr>
+          <th class="head">
+            <p>ROCm Version</p>
+          </th>
+          <th class="head">
+            <p>GPU</p>
+          </th>
+          <th class="head">
+            <p>PLDM Bundle (Firmware)</p>
+          </th>
+          <th class="head">
+            <p>AMD GPU Driver (amdgpu)</p>
+          </th>
+          <th class="head">
+            <p>AMD GPU <br>
+              Virtualization Driver (GIM)</p>
+          </th>
+      </tr>
+    </thead>
+    <style>
+        tbody#virtualization-support-instinct tr:last-child {
+          border-bottom: 2px solid var(--pst-color-primary);
+        }
+    </style>
+      <tr>
+          <td rowspan="9" style="vertical-align: middle;">ROCm 7.2.2</td>
+          <td>MI355X</td>
+          <td>
+              01.26.00.02<br>
+              01.25.17.07<br>
+              01.25.16.03
+          </td>
+          <td>
+              30.30.x where x (0-2)<br>
+              30.20.x where x (0-1)<br>
+              30.10.x where x (0-2)
+            </td>
+          <td rowspan="3" style="vertical-align: middle;">8.7.1.K</td>
+      </tr>
+      <tr>
+          <td>MI350X</td>
+          <td>
+              01.26.00.02<br>
+              01.25.17.07<br>
+              01.25.16.03
+          </td>
+          <td>
+              30.30.x where x (0-2)<br>
+              30.20.x where x (0-1)<br>
+              30.10.x where x (0-2)
+            </td>
+      </tr>
+      <tr>
+          <td>MI325X<a href="#footnote1"><sup>[1]</sup></a></td>
+          <td>
+              01.25.06.08<br>
+              01.25.04.02
+          </td>
+          <td>30.30.x where x (0-2)<br>
+              30.20.x where x (0-1)<a href="#footnote1"><sup>[1]</sup></a><br>
+              30.10.x where x (0-2)<br>
+              6.4.z where z (0-3)<br>
+              6.3.3
+          </td>
+      </tr>
+      <tr>
+          <td>MI300X<a href="#footnote2"><sup>[2]</sup></a></td>
+          <td>01.25.06.04<br>
+              01.25.03.12<br>
+              01.25.02.04</td>
+          <td rowspan="6" style="vertical-align: middle;">
+              30.30.x where x (0-2)<br>
+              30.20.x where x (0-1)<br>
+              30.10.x where x (0-2)<br>
+              6.4.z where z (0–3)<br>
+              6.3.3
+          </td>
+          <td>8.7.1.K</td>
+      </tr>
+      <tr>
+          <td>MI300A</td>
+          <td>BKC 26.1</td>
+          <td rowspan="3" style="vertical-align: middle;">Not Applicable</td>
+      </tr>
+      <tr>
+          <td>MI250X</td>
+          <td>IFWI 47 (or later)</td>
+      </tr>
+      <tr>
+          <td>MI250</td>
+          <td>MU5 w/ IFWI 75 (or later)</td>
+      </tr>
+      <tr>
+          <td>MI210</td>
+          <td>MU5 w/ IFWI 75 (or later)</td>
+          <td>8.7.1.K</td>
+      </tr>
+      <tr>
+          <td>MI100</td>
+          <td>VBIOS D3430401-037</td>
+          <td>Not Applicable</td>
+      </tr>
+  </table>
+</div>
+
+<p id="footnote1">[1]: For AMD Instinct MI325X KVM SR-IOV users, don't use AMD GPU driver (amdgpu) 30.20.0.</p>
+<p id="footnote2">[2]: AMD Instinct MI300X KVM SR-IOV with Multi-VF (8 VF) support requires a compatible firmware BKC bundle, which will be released in the coming months.</p>
+
+### ROCm documentation updates
+
+ROCm documentation continues to be updated to provide clearer and more comprehensive guidance for a wider range of user needs and use cases.
+
+* The new [AMD RDNA3.5 system optimization](https://rocm.docs.amd.com/en/latest/how-to/system-optimization/rdna3-5.html) topic describes how to optimize systems powered by AMD Ryzen APUs with RDNA3.5 architecture. These APUs combine high-performance CPU cores with integrated RDNA3.5 graphics, and support LPDDR5X-8000 or DDR5 memory.     
+
+```{note}
+ROCm 7.2.2 doesn't include any other significant changes or feature additions. For comprehensive changes, new features, and enhancements in ROCm 7.2.1, refer to the [ROCm 7.2.1 release notes](#rocm-7-2-1-release-notes) below.
+```
+
+## ROCm 7.2.1 release notes
 
 The release notes provide a summary of notable changes since the previous ROCm release.
 
-- [Release highlights](#release-highlights)
+- [Release highlights](#id1)
 
 - [Supported hardware, operating system, and virtualization changes](#supported-hardware-operating-system-and-virtualization-changes)
 
-- [User space, driver, and firmware dependent changes](#user-space-driver-and-firmware-dependent-changes)
+- [User space, driver, and firmware dependent changes](#id2)
 
 - [ROCm components versioning](#rocm-components)
 
@@ -31,16 +173,15 @@ The release notes provide a summary of notable changes since the previous ROCm r
 - [ROCm upcoming changes](#rocm-upcoming-changes)
 
 ```{note}
-If you’re using AMD Radeon GPUs or Ryzen APUs in a workstation setting with a display connected, see the [Use ROCm on Radeon and Ryzen](https://rocm.docs.amd.com/projects/radeon-ryzen/en/latest/index.html)
-documentation to verify compatibility and system requirements.
+If you’re using AMD Radeon™ GPUs or Ryzen™ for graphics workloads, see the [Use ROCm on Radeon and Ryzen](https://rocm.docs.amd.com/projects/radeon-ryzen/en/latest/index.html) documentation to verify compatibility and system requirements.
 ```
 
-## Release highlights
+### Release highlights
 
 The following are notable new features and improvements in ROCm 7.2.1. For changes to individual components, see
 [Detailed component changes](#detailed-component-changes).
 
-### Supported hardware, operating system, and virtualization changes
+#### Supported hardware, operating system, and virtualization changes
 
 Hardware support remains unchanged in this release.
 
@@ -52,11 +193,11 @@ For more information about:
 
 * Operating systems, see [Supported operating systems](https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.1/reference/system-requirements.html#supported-operating-systems) and [ROCm installation for Linux](https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.1/).
 
-#### Virtualization support
+##### Virtualization support
 
 Virtualization support remains unchanged in this release. For more information, see  [Virtualization support](https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.1/reference/system-requirements.html#virtualization-support).
 
-### User space, driver, and firmware dependent changes
+#### User space, driver, and firmware dependent changes
 
 The software for AMD Data Center GPU products requires maintaining a hardware
 and software stack with interdependencies among the GPU and baseboard
@@ -100,13 +241,9 @@ GPU and baseboard firmware versioning might differ across GPU families.
               01.25.16.03
           </td>
           <td>
-              30.30.1<br>
-              30.30.0<br>
-              30.20.1<br>
-              30.20.0<br>
-              30.10.2<br>
-              30.10.1<br>
-              30.10
+              30.30.x where x (0-2)<br>
+              30.20.x where x (0-1)<br>
+              30.10.X where x (0-2)
             </td>
           <td rowspan="3" style="vertical-align: middle;">8.7.1.K</td>
       </tr>
@@ -118,28 +255,21 @@ GPU and baseboard firmware versioning might differ across GPU families.
               01.25.16.03
           </td>
           <td>
-              30.30.1<br>
-              30.30.0<br>
-              30.20.1<br>
-              30.20.0<br>
-              30.10.2<br>
-              30.10.1<br>
-              30.10
+              30.30.x where x (0-2)<br>
+              30.20.x where x (0-1)<br>
+              30.10.X where x (0-2)
             </td>
       </tr>
       <tr>
           <td>MI325X<a href="#footnote1"><sup>[1]</sup></a></td>
           <td>
-              01.25.06.05<br>
+              01.25.06.08<br>
               01.25.04.02
           </td>
-          <td>30.30.1<br>
-              30.30.0<br>
-              30.20.1<br>
-              30.20.0<a href="#footnote1"><sup>[1]</sup></a><br>
-              30.10.2<br>
-              30.10.1<br>
-              30.10<br>
+          <td>
+              30.30.x where x (0-2)<br>
+              30.20.x where x (0-1)<a href="#footnote1"><sup>[1]</sup></a><br>
+              30.10.X where x (0-2)<br>
               6.4.z where z (0-3)<br>
               6.3.3
           </td>
@@ -150,13 +280,9 @@ GPU and baseboard firmware versioning might differ across GPU families.
               01.25.03.12<br>
               01.25.02.04</td>
           <td rowspan="6" style="vertical-align: middle;">
-              30.30.1<br>
-              30.30.0<br>
-              30.20.1<br>
-              30.20.0<br>
-              30.10.2<br>
-              30.10.1<br>
-              30.10<br>
+              30.30.x where x (0-2)<br>
+              30.20.x where x (0-1)<br>
+              30.10.X where x (0-2)<br>
               6.4.z where z (0–3)<br>
               6.3.3
           </td>
@@ -191,24 +317,24 @@ GPU and baseboard firmware versioning might differ across GPU families.
 <p id="footnote1">[1]: For AMD Instinct MI325X KVM SR-IOV users, don't use AMD GPU driver (amdgpu) 30.20.0.</p>
 <p id="footnote2">[2]: For AMD Instinct MI300X KVM SR-IOV with Multi-VF (8 VF) support requires a compatible firmware BKC bundle which will be released in coming months.</p>
 
-### hipBLASLt updates
+#### hipBLASLt updates
 
 hipBLASLt has improved performance for MXFP8 and MXFP4 GEMMs.
 
-### Deep learning and AI framework updates
+#### Deep learning and AI framework updates
 
 ROCm provides a comprehensive ecosystem for deep learning development. For more information, see [Deep learning frameworks for ROCm](../../docs/how-to/deep-learning-rocm.rst) and the [Compatibility
 matrix](../../docs/compatibility/compatibility-matrix.rst) for the complete list of Deep learning and AI framework versions tested for compatibility with ROCm. AMD ROCm has officially updated support for the following Deep learning and AI frameworks:
 
-#### JAX
+##### JAX
 
 ROCm 7.2.1 enables support for JAX 0.8.2. For more information, see [JAX compatibility](../../docs/compatibility/ml-compatibility/jax-compatibility.rst).
 
-#### ROCm Offline Installer Creator discontinuation
+### ROCm Offline Installer Creator discontinuation
 
 The ROCm Offline Installer Creator is discontinued in ROCm 7.2.1. Equivalent installation capabilities are available through the ROCm Runfile Installer, a self-extracting installer that is not based on OS package managers. For more information, see [ROCm Runfile Installer](https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.1/install/rocm-runfile-installer.html).
 
-### ROCm documentation updates
+#### ROCm documentation updates
 
 ROCm documentation continues to be updated to provide clearer and more comprehensive guidance for a wider range of user needs and use cases.
 
@@ -232,7 +358,7 @@ ROCm documentation continues to be updated to provide clearer and more comprehen
     * [Host software glossary](https://rocm.docs.amd.com/en/docs-7.2.1/reference/glossary/host-software.html): Provides brief definitions of development tools, compilers, libraries, and runtime environments for programming AMD GPUs.
     * [Performance glossary](https://rocm.docs.amd.com/en/docs-7.2.1/reference/glossary/performance.html): Provides brief definitions of performance analysis concepts and optimization techniques.
 
-## ROCm components
+### ROCm components
 
 The following table lists the versions of ROCm components for ROCm 7.2.1, including any version
 changes from 7.2.0 to 7.2.1. Click the component's updated version to go to a list of its changes.
@@ -260,7 +386,7 @@ Click {fab}`github` to go to the component's source code on GitHub.
                 <th rowspan="9">Machine learning and computer vision</th>
                 <td><a href="https://rocm.docs.amd.com/projects/composable_kernel/en/docs-7.2.1/index.html">Composable Kernel</a></td>
                 <td>1.2.0</a></td>
-                <td><a href="https://github.com/ROCm/composable_kernel"><i class="fab fa-github fa-lg"></i></a></td>
+                <td><a href="https://github.com/ROCm/rocm-libraries/tree/develop/projects/composablekernel"><i class="fab fa-github fa-lg"></i></a></td>
             </tr>
             <tr>
                 <td><a href="https://rocm.docs.amd.com/projects/AMDMIGraphX/en/docs-7.2.1/index.html">MIGraphX</a></td>
@@ -397,7 +523,7 @@ Click {fab}`github` to go to the component's source code on GitHub.
             </tr>
             <tr>
                 <td><a href="https://rocm.docs.amd.com/projects/Tensile/en/docs-7.2.1/src/index.html">Tensile</a></td>
-                <td>4.44.0</td>
+                <td>4.45.0</td>
                 <td><a href="https://github.com/ROCm/rocm-libraries/tree/develop/shared/tensile"><i class="fab fa-github fa-lg"></i></a></td>
             </tr>
         </tbody>
@@ -562,7 +688,7 @@ Click {fab}`github` to go to the component's source code on GitHub.
     </table>
 </div>
 
-## Detailed component changes
+### Detailed component changes
 
 The following sections describe key changes to ROCm components.
 
@@ -570,13 +696,13 @@ The following sections describe key changes to ROCm components.
 For a historical overview of ROCm component updates, see the {doc}`ROCm consolidated changelog </release/changelog>`.
 ```
 
-### **AMD SMI** (26.2.2) 
+#### **AMD SMI** (26.2.2) 
 
-#### Added
+##### Added
 
 * GPU board and base board temperature sensors to `amd-smi monitor` command.
 
-#### Resolved issues
+##### Resolved issues
 
 * JSON output was not formatted correctly when using watch mode with metrics.
 * Output was not properly redirected to file when using JSON format. 
@@ -584,75 +710,75 @@ For a historical overview of ROCm component updates, see the {doc}`ROCm consolid
 * Invalid CPER files caused garbage output for AFID lists.
 * JSON output was not formatted correctly for reset commands.
 
-### **HIP** (7.2.1)
+#### **HIP** (7.2.1)
 
-#### Resolved issues
+##### Resolved issues
 
 * Corrected the validation of stream capture in global‑capture mode. It is no longer affected by any thread‑local capture‑mode sequences occurring in other threads. 
 * Corrected the return value of `hipEventQuery` and `hipEventSynchronize`. The HIP runtime now properly handles and restricts stream capture within these APIs. 
 * Corrected an issue in the batch-dispatch doorbell for AQL packets to avoid a potential CPU hang.
 * To address potential delays in memory‑object destruction that could affect application logic, the HIP runtime disables memory‑object reference counting in direct‑dispatch mode.
 
-#### Changed
+##### Changed
 
 * The `AMD_DIRECT_DISPATCH` environment variable has been deprecated in the HIP runtime.
 
-### **hipBLASLt** (1.2.2)
+#### **hipBLASLt** (1.2.2)
 
-#### Changed
+##### Changed
 
 * Enumeration value update for the Sigmoid Activation Function feature.
 
-### **rocDecode** (1.7.0)
+#### **rocDecode** (1.7.0)
 
-#### Upcoming changes
+##### Upcoming changes
 
 * The rocDecode GitHub repository will be officially moved to [https://github.com/ROCm/rocm-systems/tree/develop/projects/rocdecode](https://github.com/ROCm/rocm-systems/tree/develop/projects/rocdecode) in an upcoming release.
 
-### **rocJPEG** (1.4.0)
+#### **rocJPEG** (1.4.0)
  
-#### Changed
+##### Changed
 
 * Bug fixes and performance improvements.
 
-#### Upcoming changes
+##### Upcoming changes
 
 * The rocJPEG GitHub repository will be officially moved to [https://github.com/ROCm/rocm-systems/tree/develop/projects/rocjpeg](https://github.com/ROCm/rocm-systems/tree/develop/projects/rocjpeg) in an upcoming release.
 
-### **rocSHMEM** (3.2.0)
+#### **rocSHMEM** (3.2.0)
 
-#### Added
+##### Added
 * Warnings to notify if large BAR is not available.
 
-#### Resolved issues
+##### Resolved issues
 
 * GDA Backend will disable itself when no GDA compatible NICs are available rather than crashing.
 * Fix memory coherency issues on gfx1201.
 
-#### Known issues
+##### Known issues
 
 * Only 64-bit rocSHMEM atomic APIs are implemented for the GDA conduit.
 
-### **RPP** (2.2.1)
+#### **RPP** (2.2.1)
 
-#### Added
+##### Added
  
 * Error-code capture in test scripts for all C++ tests.
  
-#### Optimized
+##### Optimized
  
 * Optimized F16 variants by replacing scalar load/store operations with AVX2 intrinsics for spatter, log, blend, color_cast, flip, crop_mirror_normalize, and exposure kernels.
 
-## ROCm known issues
+### ROCm known issues
 
 ROCm known issues are noted on {fab}`github` [GitHub](https://github.com/ROCm/ROCm/labels/Verified%20Issue). For known
 issues related to individual components, review the [Detailed component changes](#detailed-component-changes).
 
-### hipBLASLt performance regression for specific GEMM configurations
+#### hipBLASLt performance regression for specific GEMM configurations
 
 You might observe a noticeable performance regression if you’re using hipBLASLt with the following GPUs for LLMs with specific GEMM configurations:
 
-#### AMD Instinct MI300X and MI325X GPUs
+##### AMD Instinct MI300X and MI325X GPUs
 
 Affected GEMM configurations:
 
@@ -662,7 +788,7 @@ Affected GEMM configurations:
 
 * 9728 × 8192 × 65536 (F8F8S, TN)
 
-#### AMD Instinct MI350 Series GPUs
+##### AMD Instinct MI350 Series GPUs
 
 Affected GEMM configurations:
 
@@ -674,26 +800,38 @@ Affected GEMM configurations:
 
 * 8192 × 8192 × 1 × 16384
 
-Due to this issue, you might also observe a slight increase in the test or inference time. This issue is resolved in the {fab}`github`[hipBLASLt `develop` branch](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipblaslt) and will be part of a future ROCm release.
+Due to this issue, you might also observe a slight increase in the test or inference time. This issue is resolved in the {fab}`github`[hipBLASLt develop branch](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipblaslt) and will be part of a future ROCm release. See [GitHub issue #6065](https://github.com/ROCm/ROCm/issues/6065).
 
 ### Longer runtime for hipBLASLt GEMM operations on Instinct MI300X GPUs in partitioned mode
 
-GEMM operations using hipBLASLt might result in longer runtime on AMD Instinct MI300X GPUs configured in CPX or NPS4 partition mode (38 control units or CUs). This issue occurs when hipBLASLt fails to find applicable pre-tuned kernels. As a result, it performs an extensive kernel search, which increases both search time and the overall operation runtime. This issue is resolved in the {fab}`github`[hipBLASLt `develop` branch](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipblaslt) and will be part of a future ROCm release.
+GEMM operations using hipBLASLt might result in longer runtime on AMD Instinct MI300X GPUs configured in CPX or NPS4 partition mode (38 control units or CUs). This issue occurs when hipBLASLt fails to find applicable pre-tuned kernels. As a result, it performs an extensive kernel search, which increases both search time and the overall operation runtime. This issue is resolved in the {fab}`github`[hipBLASLt develop branch](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipblaslt) and will be part of a future ROCm release. See [GitHub issue #6066](https://github.com/ROCm/ROCm/issues/6066).
 
-## ROCm resolved issues
+### ROCTracer might fail to report kernel operations
+
+Applications that use [ROCTracer](https://rocm.docs.amd.com/projects/roctracer/en/latest/index.html) might fail to receive some or all kernel operation events due to a ROCTracer reporting failure. ROCTracer is already deprecated and is scheduled to reach end of support (EoS) by the end of 2026 Q2. For more details on ROCTracer deprecation, see  [ROCm upcoming changes](#roctracer-rocprofiler-rocprof-and-rocprofv2-deprecation). This issue will be resolved in a future PyTorch on ROCm release that replaces ROCTracer with [ROCprofiler-SDK](https://rocm.docs.amd.com/projects/rocprofiler-sdk/en/latest/). See [GitHub issue #6102](https://github.com/ROCm/ROCm/issues/6102).
+
+#### Longer runtime for hipBLASLt GEMM operations on Instinct MI300X GPUs in partitioned mode
+
+GEMM operations using hipBLASLt might result in longer runtime on AMD Instinct MI300X GPUs configured in CPX or NPS4 partition mode (38 control units or CUs). This issue occurs when hipBLASLt fails to find applicable pre-tuned kernels. As a result, it performs an extensive kernel search, which increases both search time and the overall operation runtime. This issue is resolved in the {fab}`github`[hipBLASLt develop branch](https://github.com/ROCm/rocm-libraries/tree/develop/projects/hipblaslt) and will be part of a future ROCm release. See [GitHub issue #6066](https://github.com/ROCm/ROCm/issues/6066).
+
+#### ROCTracer might fail to report kernel operations
+
+Applications that use [ROCTracer](https://rocm.docs.amd.com/projects/roctracer/en/latest/index.html) might fail to receive some or all kernel operation events due to a ROCTracer reporting failure. ROCTracer is already deprecated and is scheduled to reach end of support (EoS) by the end of 2026 Q2. For more details on ROCTracer deprecation, see  [ROCm upcoming changes](#roctracer-rocprofiler-rocprof-and-rocprofv2-deprecation). This issue will be resolved in a future PyTorch on ROCm release that replaces ROCTracer with [ROCprofiler-SDK](https://rocm.docs.amd.com/projects/rocprofiler-sdk/en/latest/). See [GitHub issue #6102](https://github.com/ROCm/ROCm/issues/6102).
+
+### ROCm resolved issues
 
 The following are previously known issues resolved in this release. For resolved issues related to
 individual components, review the [Detailed component changes](#detailed-component-changes).
 
-### Increased runtime latency of the HIP hipStreamCreate API
+#### Increased runtime latency of the HIP hipStreamCreate API
 
 As issue that resulted in doubling of the runtime latency of the [HIP](https://rocmdocs.amd.com/projects/HIP/en/latest/doxygen/html/group___stream.html) `hipStreamCreate` API has been resolved. See [GitHub issue #5978](https://github.com/ROCm/ROCm/issues/5978). 
 
-## ROCm upcoming changes
+### ROCm upcoming changes
 
 The following changes to the ROCm software stack are anticipated for future releases.
 
-### ROCTracer, ROCProfiler, rocprof, and rocprofv2 deprecation
+#### ROCTracer, ROCProfiler, rocprof, and rocprofv2 deprecation
 
 ROCTracer, ROCProfiler, `rocprof`, and `rocprofv2` are deprecated. It's strongly recommended to upgrade to the latest version of the [ROCprofiler-SDK](https://rocm.docs.amd.com/projects/rocprofiler-sdk/en/latest/) library and the (`rocprofv3`) tool to ensure continued support and access to new features. 
 
@@ -701,7 +839,7 @@ To learn about key feature improvements and benefits of ROCprofiler-SDK over the
 
 It's anticipated that ROCTracer, ROCProfiler, `rocprof`, and `rocprofv2` will reach end of support (EoS) by the end of 2026 Q2.
 
-### ROCm SMI deprecation
+#### ROCm SMI deprecation
 
 [ROCm SMI](https://github.com/ROCm/rocm_smi_lib) will be phased out in an
 upcoming ROCm release and will enter maintenance mode. After this transition,
@@ -714,7 +852,7 @@ includes all the features of the ROCm SMI and will continue to receive regular
 updates, new functionality, and ongoing support. For more information on AMD
 SMI, see the [AMD SMI documentation](https://rocm.docs.amd.com/projects/amdsmi/en/latest/).
 
-### Changes to ROCm Object Tooling
+#### Changes to ROCm Object Tooling
 
 ROCm Object Tooling tools ``roc-obj-ls``, ``roc-obj-extract``, and ``roc-obj`` were
 deprecated in ROCm 6.4, and will be removed in a future release. Functionality
@@ -723,4 +861,4 @@ clang-offload-bundles into individual code objects found within the objects
 or executables passed as input.  The ``llvm-objdump --offloading`` tool option also
 supports the ``--arch-name`` option, and only extracts code objects found with
 the specified target architecture. See [llvm-objdump](https://llvm.org/docs/CommandGuide/llvm-objdump.html)
-for more information. 
+for more information. 

docs/compatibility/compatibility-matrix-historical-6.0.csv

@@ -1,4 +1,4 @@
-ROCm Version,7.2.1,7.2.0,7.1.1,7.1.0,7.0.2,7.0.1/7.0.0,6.4.3,6.4.2,6.4.1,6.4.0,6.3.3,6.3.2,6.3.1,6.3.0,6.2.4,6.2.2,6.2.1,6.2.0, 6.1.5, 6.1.2, 6.1.1, 6.1.0, 6.0.2, 6.0.0
+ROCm Version,7.2.2/7.2.1,7.2.0,7.1.1,7.1.0,7.0.2,7.0.1/7.0.0,6.4.3,6.4.2,6.4.1,6.4.0,6.3.3,6.3.2,6.3.1,6.3.0,6.2.4,6.2.2,6.2.1,6.2.0, 6.1.5, 6.1.2, 6.1.1, 6.1.0, 6.0.2, 6.0.0
       :ref:`Operating systems & kernels <OS-kernel-versions>` [#os-compatibility-past-60]_,Ubuntu 24.04.3,Ubuntu 24.04.3,Ubuntu 24.04.3,Ubuntu 24.04.3,Ubuntu 24.04.3,Ubuntu 24.04.3,Ubuntu 24.04.2,Ubuntu 24.04.2,Ubuntu 24.04.2,Ubuntu 24.04.2,Ubuntu 24.04.2,Ubuntu 24.04.2,Ubuntu 24.04.2,Ubuntu 24.04.2,"Ubuntu 24.04.1, 24.04","Ubuntu 24.04.1, 24.04","Ubuntu 24.04.1, 24.04",Ubuntu 24.04,,,,,,
       ,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5,"Ubuntu 22.04.5, 22.04.4","Ubuntu 22.04.5, 22.04.4","Ubuntu 22.04.5, 22.04.4","Ubuntu 22.04.5, 22.04.4","Ubuntu 22.04.5, 22.04.4, 22.04.3","Ubuntu 22.04.4, 22.04.3","Ubuntu 22.04.4, 22.04.3","Ubuntu 22.04.4, 22.04.3","Ubuntu 22.04.4, 22.04.3, 22.04.2","Ubuntu 22.04.4, 22.04.3, 22.04.2"
       ,,,,,,,,,,,,,,,,,,,"Ubuntu 20.04.6, 20.04.5","Ubuntu 20.04.6, 20.04.5","Ubuntu 20.04.6, 20.04.5","Ubuntu 20.04.6, 20.04.5","Ubuntu 20.04.6, 20.04.5","Ubuntu 20.04.6, 20.04.5"
@@ -33,13 +33,7 @@ ROCm Version,7.2.1,7.2.0,7.1.1,7.1.0,7.0.2,7.0.1/7.0.0,6.4.3,6.4.2,6.4.1,6.4.0,6
       :doc:`PyTorch <../compatibility/ml-compatibility/pytorch-compatibility>`,"2.9.1, 2.8.0, 2.7.1","2.9.1, 2.8.0, 2.7.1","2.9, 2.8, 2.7","2.8, 2.7, 2.6","2.8, 2.7, 2.6","2.7, 2.6, 2.5","2.6, 2.5, 2.4, 2.3","2.6, 2.5, 2.4, 2.3","2.6, 2.5, 2.4, 2.3","2.6, 2.5, 2.4, 2.3","2.4, 2.3, 2.2, 1.13","2.4, 2.3, 2.2, 1.13","2.4, 2.3, 2.2, 1.13","2.4, 2.3, 2.2, 2.1, 2.0, 1.13","2.3, 2.2, 2.1, 2.0, 1.13","2.3, 2.2, 2.1, 2.0, 1.13","2.3, 2.2, 2.1, 2.0, 1.13","2.3, 2.2, 2.1, 2.0, 1.13","2.1, 2.0, 1.13","2.1, 2.0, 1.13","2.1, 2.0, 1.13","2.1, 2.0, 1.13","2.1, 2.0, 1.13","2.1, 2.0, 1.13"
       :doc:`TensorFlow <../compatibility/ml-compatibility/tensorflow-compatibility>`,"2.20.0, 2.19.1, 2.18.1","2.20.0, 2.19.1, 2.18.1","2.20.0, 2.19.1, 2.18.1","2.20.0, 2.19.1, 2.18.1","2.19.1, 2.18.1, 2.17.1 [#tf-mi350-past-60]_","2.19.1, 2.18.1, 2.17.1 [#tf-mi350-past-60]_","2.18.1, 2.17.1, 2.16.2","2.18.1, 2.17.1, 2.16.2","2.18.1, 2.17.1, 2.16.2","2.18.1, 2.17.1, 2.16.2","2.17.0, 2.16.2, 2.15.1","2.17.0, 2.16.2, 2.15.1","2.17.0, 2.16.2, 2.15.1","2.17.0, 2.16.2, 2.15.1","2.16.1, 2.15.1, 2.14.1","2.16.1, 2.15.1, 2.14.1","2.16.1, 2.15.1, 2.14.1","2.16.1, 2.15.1, 2.14.1","2.15.0, 2.14.0, 2.13.1","2.15.0, 2.14.0, 2.13.1","2.15.0, 2.14.0, 2.13.1","2.15.0, 2.14.0, 2.13.1","2.14.0, 2.13.1, 2.12.1","2.14.0, 2.13.1, 2.12.1"
       :doc:`JAX <../compatibility/ml-compatibility/jax-compatibility>`,0.8.2,0.8.0,0.7.1,0.7.1,0.6.0,0.6.0,0.4.35,0.4.35,0.4.35,0.4.35,0.4.31,0.4.31,0.4.31,0.4.31,0.4.26,0.4.26,0.4.26,0.4.26,0.4.26,0.4.26,0.4.26,0.4.26,0.4.26,0.4.26
-      :doc:`verl <../compatibility/ml-compatibility/verl-compatibility>` [#verl_compat-past-60]_,N/A,N/A,N/A,N/A,N/A,0.6.0,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,0.3.0.post0,N/A,N/A,N/A,N/A,N/A,N/A
-      :doc:`Stanford Megatron-LM <../compatibility/ml-compatibility/stanford-megatron-lm-compatibility>` [#stanford-megatron-lm_compat-past-60]_,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,85f95ae,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
       :doc:`DGL <../compatibility/ml-compatibility/dgl-compatibility>` [#dgl_compat-past-60]_,N/A,N/A,N/A,N/A,N/A,2.4.0,2.4.0,N/A,N/A,2.4.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
-      :doc:`Megablocks <../compatibility/ml-compatibility/megablocks-compatibility>` [#megablocks_compat-past-60]_,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,0.7.0,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
-      :doc:`Ray <../compatibility/ml-compatibility/ray-compatibility>` [#ray_compat-past-60]_,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,2.48.0.post0,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
-      :doc:`llama.cpp <../compatibility/ml-compatibility/llama-cpp-compatibility>` [#llama-cpp_compat-past-60]_,N/A,N/A,N/A,N/A,N/A,b6652,b6356,b6356,b6356,b5997,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
-      :doc:`FlashInfer <../compatibility/ml-compatibility/flashinfer-compatibility>` [#flashinfer_compat-past-60]_,N/A,N/A,v0.2.5,N/A,N/A,N/A,N/A,N/A,v0.2.5,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
       `ONNX Runtime <https://onnxruntime.ai/docs/build/eps.html#amd-migraphx>`_,1.23.2,1.23.2,1.23.1,1.22.0,1.22.0,1.22.0,1.20.0,1.20.0,1.20.0,1.20.0,1.17.3,1.17.3,1.17.3,1.17.3,1.17.3,1.17.3,1.17.3,1.17.3,1.17.3,1.17.3,1.17.3,1.17.3,1.14.1,1.14.1
       ,,,,,,,,,,,,,,,,,,,,,,,,
       ,,,,,,,,,,,,,,,,,,,,,,,,
@@ -52,7 +46,7 @@ ROCm Version,7.2.1,7.2.0,7.1.1,7.1.0,7.0.2,7.0.1/7.0.0,6.4.3,6.4.2,6.4.1,6.4.0,6
       CUB,2.8.5,2.8.5,2.8.5,2.8.5,2.6.0,2.6.0,2.5.0,2.5.0,2.5.0,2.5.0,2.3.2,2.3.2,2.3.2,2.3.2,2.2.0,2.2.0,2.2.0,2.2.0,2.1.0,2.1.0,2.1.0,2.1.0,2.0.1,2.0.1
       ,,,,,,,,,,,,,,,,,,,,,,,,
      DRIVER & USER SPACE [#kfd_support-past-60]_,.. _kfd-userspace-support-compatibility-matrix-past-60:,,,,,,,,,,,,,,,,,,,,,,,
-      :doc:`AMD GPU Driver <rocm-install-on-linux:reference/user-kernel-space-compat-matrix>`,"30.30.1, 30.30.0, 30.20.1, 30.20.0 [#mi325x_KVM-past-60]_, 30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x","30.30.0, 30.20.1, 30.20.0 [#mi325x_KVM-past-60]_, 30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x","30.20.1, 30.20.0 [#mi325x_KVM-past-60]_, 30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x","30.20.0 [#mi325x_KVM-past-60]_, 30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x","30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x, 6.3.x","30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x, 6.3.x, 6.2.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.7.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.7.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.7.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.7.x","6.2.x, 6.1.x, 6.0.x, 5.7.x, 5.6.x","6.2.x, 6.1.x, 6.0.x, 5.7.x, 5.6.x"
+      :doc:`AMD GPU Driver <rocm-install-on-linux:reference/user-kernel-space-compat-matrix>`,"30.30.2, 30.30.1, 30.30.0, 30.20.1, 30.20.0 [#mi325x_KVM-past-60]_, 30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x","30.30.0, 30.20.1, 30.20.0 [#mi325x_KVM-past-60]_, 30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x","30.20.1, 30.20.0 [#mi325x_KVM-past-60]_, 30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x","30.20.0 [#mi325x_KVM-past-60]_, 30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x","30.10.2, 30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x, 6.3.x","30.10.1 [#driver_patch-past-60]_, 30.10, 6.4.x, 6.3.x, 6.2.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.7.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.7.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.7.x","6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.7.x","6.2.x, 6.1.x, 6.0.x, 5.7.x, 5.6.x","6.2.x, 6.1.x, 6.0.x, 5.7.x, 5.6.x"
       ,,,,,,,,,,,,,,,,,,,,,,,,
       ML & COMPUTER VISION,.. _mllibs-support-compatibility-matrix-past-60:,,,,,,,,,,,,,,,,,,,,,,,
       :doc:`Composable Kernel <composable_kernel:index>`,1.2.0,1.2.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0,1.1.0
@@ -96,7 +90,7 @@ ROCm Version,7.2.1,7.2.0,7.1.1,7.1.0,7.0.2,7.0.1/7.0.0,6.4.3,6.4.2,6.4.1,6.4.0,6
       ,,,,,,,,,,,,,,,,,,,,,,,,
       SUPPORT LIBS,,,,,,,,,,,,,,,,,,,,,,,,
       `hipother <https://github.com/ROCm/hipother>`_,7.2.53211,7.2.26015,7.1.52802,7.1.25424,7.0.51831,7.0.51830,6.4.43483,6.4.43483,6.4.43483,6.4.43482,6.3.42134,6.3.42134,6.3.42133,6.3.42131,6.2.41134,6.2.41134,6.2.41134,6.2.41133,6.1.40093,6.1.40093,6.1.40092,6.1.40091,6.1.32831,6.1.32830
-      `rocm-core <https://github.com/ROCm/rocm-core>`_,7.2.1,7.2.0,7.1.1,7.1.0,7.0.2,7.0.1/7.0.0,6.4.3,6.4.2,6.4.1,6.4.0,6.3.3,6.3.2,6.3.1,6.3.0,6.2.4,6.2.2,6.2.1,6.2.0,6.1.5,6.1.2,6.1.1,6.1.0,6.0.2,6.0.0
+      `rocm-core <https://github.com/ROCm/rocm-core>`_,7.2.2/7.2.1,7.2.0,7.1.1,7.1.0,7.0.2,7.0.1/7.0.0,6.4.3,6.4.2,6.4.1,6.4.0,6.3.3,6.3.2,6.3.1,6.3.0,6.2.4,6.2.2,6.2.1,6.2.0,6.1.5,6.1.2,6.1.1,6.1.0,6.0.2,6.0.0
       `ROCT-Thunk-Interface <https://github.com/ROCm/ROCT-Thunk-Interface>`_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,N/A [#ROCT-rocr-past-60]_,20240607.5.7,20240607.5.7,20240607.4.05,20240607.1.4246,20240125.5.08,20240125.5.08,20240125.5.08,20240125.3.30,20231016.2.245,20231016.2.245
       ,,,,,,,,,,,,,,,,,,,,,,,,
       SYSTEM MGMT TOOLS,.. _tools-support-compatibility-matrix-past-60:,,,,,,,,,,,,,,,,,,,,,,,
@@ -110,9 +104,9 @@ ROCm Version,7.2.1,7.2.0,7.1.1,7.1.0,7.0.2,7.0.1/7.0.0,6.4.3,6.4.2,6.4.1,6.4.0,6
       :doc:`ROCm Bandwidth Test <rocm_bandwidth_test:index>`,2.6.0,2.6.0,2.6.0,2.6.0,2.6.0,2.6.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0,1.4.0
       :doc:`ROCm Compute Profiler <rocprofiler-compute:index>`,3.4.0,3.4.0,3.3.1,3.3.0,3.2.3,3.2.3,3.1.1,3.1.1,3.1.0,3.1.0,3.0.0,3.0.0,3.0.0,3.0.0,2.0.1,2.0.1,2.0.1,2.0.1,N/A,N/A,N/A,N/A,N/A,N/A
       :doc:`ROCm Systems Profiler <rocprofiler-systems:index>`,1.3.0,1.3.0,1.2.1,1.2.0,1.1.1,1.1.0,1.0.2,1.0.2,1.0.1,1.0.0,0.1.2,0.1.1,0.1.0,0.1.0,1.11.2,1.11.2,1.11.2,1.11.2,N/A,N/A,N/A,N/A,N/A,N/A
-      :doc:`ROCProfiler <rocprofiler:index>`,2.0.70201,2.0.70200,2.0.70101,2.0.70100,2.0.70002,2.0.70000,2.0.60403,2.0.60402,2.0.60401,2.0.60400,2.0.60303,2.0.60302,2.0.60301,2.0.60300,2.0.60204,2.0.60202,2.0.60201,2.0.60200,2.0.60105,2.0.60102,2.0.60101,2.0.60100,2.0.60002,2.0.60000
+      :doc:`ROCProfiler <rocprofiler:index>`,2.0.70202/2.0.70201,2.0.70200,2.0.70101,2.0.70100,2.0.70002,2.0.70000,2.0.60403,2.0.60402,2.0.60401,2.0.60400,2.0.60303,2.0.60302,2.0.60301,2.0.60300,2.0.60204,2.0.60202,2.0.60201,2.0.60200,2.0.60105,2.0.60102,2.0.60101,2.0.60100,2.0.60002,2.0.60000
       :doc:`ROCprofiler-SDK <rocprofiler-sdk:index>`,1.1.0,1.1.0,1.0.0,1.0.0,1.0.0,1.0.0,0.6.0,0.6.0,0.6.0,0.6.0,0.5.0,0.5.0,0.5.0,0.5.0,0.4.0,0.4.0,0.4.0,0.4.0,N/A,N/A,N/A,N/A,N/A,N/A
-      :doc:`ROCTracer <roctracer:index>`,4.1.70201,4.1.70200,4.1.70101,4.1.70100,4.1.70002,4.1.70000,4.1.60403,4.1.60402,4.1.60401,4.1.60400,4.1.60303,4.1.60302,4.1.60301,4.1.60300,4.1.60204,4.1.60202,4.1.60201,4.1.60200,4.1.60105,4.1.60102,4.1.60101,4.1.60100,4.1.60002,4.1.60000
+      :doc:`ROCTracer <roctracer:index>`,4.1.70202/4.1.70201,4.1.70200,4.1.70101,4.1.70100,4.1.70002,4.1.70000,4.1.60403,4.1.60402,4.1.60401,4.1.60400,4.1.60303,4.1.60302,4.1.60301,4.1.60300,4.1.60204,4.1.60202,4.1.60201,4.1.60200,4.1.60105,4.1.60102,4.1.60101,4.1.60100,4.1.60002,4.1.60000
       ,,,,,,,,,,,,,,,,,,,,,,,,
       DEVELOPMENT TOOLS,,,,,,,,,,,,,,,,,,,,,,,,
       :doc:`HIPIFY <hipify:index>`,22.0.0,22.0.0,20.0.0,20.0.0,20.0.0,20.0.0,19.0.0,19.0.0,19.0.0,19.0.0,18.0.0.25012,18.0.0.25012,18.0.0.24491,18.0.0.24455,18.0.0.24392,18.0.0.24355,18.0.0.24355,18.0.0.24232,17.0.0.24193,17.0.0.24193,17.0.0.24154,17.0.0.24103,17.0.0.24012,17.0.0.23483

docs/compatibility/compatibility-matrix.rst

@@ -22,12 +22,12 @@ compatibility and system requirements.
 .. container:: format-big-table
 
   .. csv-table::
-      :header: "ROCm Version", "7.2.1", "7.2.0", "6.4.0"
+      :header: "ROCm Version", "7.2.2/7.2.1", "7.2.0", "6.4.0"
       :stub-columns: 1
 
       :ref:`Operating systems & kernels <OS-kernel-versions>` [#os-compatibility]_,Ubuntu 24.04.4,Ubuntu 24.04.3,Ubuntu 24.04.2
       ,Ubuntu 22.04.5,Ubuntu 22.04.5,Ubuntu 22.04.5
-      ,"RHEL 10.1, 10.0, 9.7, 9.6, 9.4","RHEL 10.1, 10.0, 9.7, 9.6, 9.4","RHEL 9.5, 9.4"
+      ,"RHEL 10.1, 10.0, |br| 9.7, 9.6, 9.4","RHEL 10.1, 10.0, |br| 9.7, 9.6, 9.4","RHEL 9.5, 9.4"
       ,RHEL 8.10,RHEL 8.10,RHEL 8.10
       ,SLES 15 SP7,SLES 15 SP7,SLES 15 SP6
       ,"Oracle Linux 10, 9, 8","Oracle Linux 10, 9, 8","Oracle Linux 9, 8"
@@ -58,7 +58,6 @@ compatibility and system requirements.
       :doc:`TensorFlow <../compatibility/ml-compatibility/tensorflow-compatibility>`,"2.20.0, 2.19.1, 2.18.1","2.20.0, 2.19.1, 2.18.1","2.18.1, 2.17.1, 2.16.2"
       :doc:`JAX <../compatibility/ml-compatibility/jax-compatibility>`,0.8.2,0.8.0,0.4.35
       :doc:`DGL <../compatibility/ml-compatibility/dgl-compatibility>` [#dgl_compat]_,N/A,N/A,2.4.0
-      :doc:`llama.cpp <../compatibility/ml-compatibility/llama-cpp-compatibility>` [#llama-cpp_compat]_,N/A,N/A,b5997
       `ONNX Runtime <https://onnxruntime.ai/docs/build/eps.html#amd-migraphx>`_,1.23.2,1.23.2,1.20.0
       ,,,
       THIRD PARTY COMMS,.. _thirdpartycomms-support-compatibility-matrix:,,
@@ -70,7 +69,7 @@ compatibility and system requirements.
       CUB,2.8.5,2.8.5,2.5.0
       ,,,
       DRIVER & USER SPACE [#kfd_support]_,.. _kfd-userspace-support-compatibility-matrix:,,
-      :doc:`AMD GPU Driver <rocm-install-on-linux:reference/user-kernel-space-compat-matrix>`,"30.30.1, 30.30.0, 30.20.1, |br| 30.20.0 [#mi325x_KVM]_, 30.10.2, |br| 30.10.1 [#driver_patch]_, 30.10, 6.4.x","30.30.0, 30.20.1, 30.20.0 [#mi325x_KVM]_, |br| 30.10.2, 30.10.1 [#driver_patch]_, |br| 30.10, 6.4.x","6.4.x, 6.3.x, 6.2.x, 6.1.x"
+      :doc:`AMD GPU Driver <rocm-install-on-linux:reference/user-kernel-space-compat-matrix>`,"30.30.2, 30.30.1, 30.30.0, |br|  30.20.1, 30.20.0 [#mi325x_KVM]_, 30.10.2, |br| 30.10.1 [#driver_patch]_, 30.10, 6.4.x","30.30.0, 30.20.1, 30.20.0 [#mi325x_KVM]_, |br| 30.10.2, 30.10.1 [#driver_patch]_, |br| 30.10, 6.4.x","6.4.x, 6.3.x, 6.2.x, 6.1.x"
       ,,,
       ML & COMPUTER VISION,.. _mllibs-support-compatibility-matrix:,,
       :doc:`Composable Kernel <composable_kernel:index>`,1.2.0,1.2.0,1.1.0
@@ -114,7 +113,7 @@ compatibility and system requirements.
       ,,,
       SUPPORT LIBS,,,
       `hipother <https://github.com/ROCm/hipother>`_,7.2.53211,7.2.26015,6.4.43482
-      `rocm-core <https://github.com/ROCm/rocm-core>`_,7.2.1,7.2.0,6.4.0
+      `rocm-core <https://github.com/ROCm/rocm-core>`_,7.2.2/7.2.1,7.2.0,6.4.0
       `ROCT-Thunk-Interface <https://github.com/ROCm/ROCT-Thunk-Interface>`_,N/A [#ROCT-rocr]_,N/A [#ROCT-rocr]_,N/A [#ROCT-rocr]_
       ,,,
       SYSTEM MGMT TOOLS,.. _tools-support-compatibility-matrix:,,
@@ -128,9 +127,9 @@ compatibility and system requirements.
       :doc:`ROCm Bandwidth Test <rocm_bandwidth_test:index>`,2.6.0,2.6.0,1.4.0
       :doc:`ROCm Compute Profiler <rocprofiler-compute:index>`,3.4.0,3.4.0,3.1.0
       :doc:`ROCm Systems Profiler <rocprofiler-systems:index>`,1.3.0,1.3.0,1.0.0
-      :doc:`ROCProfiler <rocprofiler:index>`,2.0.70201,2.0.70200,2.0.60400
+      :doc:`ROCProfiler <rocprofiler:index>`,2.0.70202/2.0.70201,2.0.70200,2.0.60400
       :doc:`ROCprofiler-SDK <rocprofiler-sdk:index>`,1.1.0,1.1.0,0.6.0
-      :doc:`ROCTracer <roctracer:index>`,4.1.70201,4.1.70200,4.1.60400
+      :doc:`ROCTracer <roctracer:index>`,4.1.70202/4.1.70201,4.1.70200,4.1.60400
       ,,,
       DEVELOPMENT TOOLS,,,
       :doc:`HIPIFY <hipify:index>`,22.0.0,22.0.0,19.0.0
@@ -156,10 +155,9 @@ compatibility and system requirements.
 
 .. rubric:: Footnotes
 
-.. [#os-compatibility] Some operating systems are supported on specific GPUs. For detailed information about operating systems supported on ROCm 7.2.1, see the latest :ref:`supported_distributions`. For version specific information, see `ROCm 7.2.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.0/reference/system-requirements.html#supported-operating-systems>`__, and `ROCm 6.4.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-6.4.0/reference/system-requirements.html#supported-operating-systems>`__.
-.. [#gpu-compatibility] Some GPUs have limited operating system support. For detailed information about GPUs supporting ROCm 7.2.1, see the latest :ref:`supported_GPUs`. For version specific information, see `ROCm 7.2.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.0/reference/system-requirements.html#supported-gpus>`__, and `ROCm 6.4.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-6.4.0/reference/system-requirements.html#supported-gpus>`__.
+.. [#os-compatibility] Some operating systems are supported on specific GPUs. For detailed information about operating systems supported on ROCm 7.2.2/7.2.1, see the latest :ref:`supported_distributions`. For version specific information, see `ROCm 7.2.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.0/reference/system-requirements.html#supported-operating-systems>`__, and `ROCm 6.4.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-6.4.0/reference/system-requirements.html#supported-operating-systems>`__.
+.. [#gpu-compatibility] Some GPUs have limited operating system support. For detailed information about GPUs supporting ROCm 7.2.2/7.2.1, see the latest :ref:`supported_GPUs`. For version specific information, see `ROCm 7.2.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.0/reference/system-requirements.html#supported-gpus>`__, and `ROCm 6.4.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-6.4.0/reference/system-requirements.html#supported-gpus>`__.
 .. [#dgl_compat] DGL is supported only on ROCm 7.0.0, ROCm 6.4.3, and ROCm 6.4.0.
-.. [#llama-cpp_compat] llama.cpp is supported only on ROCm 7.0.0 and ROCm 6.4.x.
 .. [#mi325x_KVM] For AMD Instinct MI325X KVM SR-IOV users, do not use AMD GPU Driver (amdgpu) 30.20.0.
 .. [#driver_patch] AMD GPU Driver (amdgpu) 30.10.1 is a quality release that resolves an issue identified in the 30.10 release. There are no other significant changes or feature additions in ROCm 7.0.1 from ROCm 7.0.0. AMD GPU Driver (amdgpu) 30.10.1 is compatible with ROCm 7.0.1 and ROCm 7.0.0.
 .. [#kfd_support] As of ROCm 6.4.0, forward and backward compatibility between the AMD GPU Driver (amdgpu) and its user space software is provided up to a year apart. For earlier ROCm releases, the compatibility is provided for +/- 2 releases. The supported user space versions on this page were accurate as of the time of initial ROCm release. For the most up-to-date information, see the latest version of this information at `User and AMD GPU Driver support matrix <https://rocm.docs.amd.com/projects/install-on-linux/en/latest/reference/user-kernel-space-compat-matrix.html>`_.
@@ -170,7 +168,7 @@ compatibility and system requirements.
 Operating systems, kernel and Glibc versions
 *********************************************
 
-For detailed information on operating system supported on ROCm 7.2.1 and associated Kernel and Glibc version, see the latest :ref:`supported_distributions`. For version specific information, see `ROCm 7.2.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.0/reference/system-requirements.html#supported-operating-systems>`__, and `ROCm 6.4.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-6.4.0/reference/system-requirements.html#supported-operating-systems>`__.
+For detailed information on operating system supported on ROCm 7.2.2/7.2.1 and associated Kernel and Glibc version, see the latest :ref:`supported_distributions`. For version specific information, see `ROCm 7.2.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-7.2.0/reference/system-requirements.html#supported-operating-systems>`__, and `ROCm 6.4.0 <https://rocm.docs.amd.com/projects/install-on-linux/en/docs-6.4.0/reference/system-requirements.html#supported-operating-systems>`__.
 
 .. note::
 
@@ -205,13 +203,7 @@ Expand for full historical view of:
    .. [#os-compatibility-past-60] Some operating systems are supported on specific GPUs. For detailed information, see :ref:`supported_distributions` and select the required ROCm version for version specific support.
    .. [#gpu-compatibility-past-60] Some GPUs have limited operating system support. For detailed information, see :ref:`supported_GPUs` and select the required ROCm version for version specific support.
    .. [#tf-mi350-past-60] TensorFlow 2.17.1 is not supported on AMD Instinct MI350 Series GPUs. Use TensorFlow 2.19.1 or 2.18.1 with MI350 Series GPUs instead.
-   .. [#verl_compat-past-60] verl is supported only on ROCm 6.2.0.
-   .. [#stanford-megatron-lm_compat-past-60] Stanford Megatron-LM is supported only on ROCm 6.3.0.
    .. [#dgl_compat-past-60] DGL is supported only on ROCm 7.0.0, ROCm 6.4.3, and ROCm 6.4.0.
-   .. [#megablocks_compat-past-60] Megablocks is supported only on ROCm 6.3.0.
-   .. [#ray_compat-past-60] Ray is supported only on ROCm 6.4.1.
-   .. [#llama-cpp_compat-past-60] llama.cpp is supported only on ROCm 7.0.0 and 6.4.x.
-   .. [#flashinfer_compat-past-60] FlashInfer is supported only on ROCm 6.4.1.
    .. [#mi325x_KVM-past-60] For AMD Instinct MI325X KVM SR-IOV users, do not use AMD GPU Driver (amdgpu) 30.20.0.
    .. [#driver_patch-past-60] AMD GPU Driver (amdgpu) 30.10.1 is a quality release that resolves an issue identified in the 30.10 release. There are no other significant changes or feature additions in ROCm 7.0.1 from ROCm 7.0.0. AMD GPU Driver (amdgpu) 30.10.1 is compatible with ROCm 7.0.1 and ROCm 7.0.0.
    .. [#kfd_support-past-60] As of ROCm 6.4.0, forward and backward compatibility between the AMD GPU Driver (amdgpu) and its user space software is provided up to a year apart. For earlier ROCm releases, the compatibility is provided for +/- 2 releases. The supported user space versions on this page were accurate as of the time of initial ROCm release. For the most up-to-date information, see the latest version of this information at `User and AMD GPU Driver support matrix <https://rocm.docs.amd.com/projects/install-on-linux/en/latest/reference/user-kernel-space-compat-matrix.html>`_.

docs/compatibility/ml-compatibility/flashinfer-compatibility.rst

@@ -1,113 +0,0 @@
-:orphan:
-
-.. meta::
-    :description: FlashInfer compatibility
-    :keywords: GPU, LLM, FlashInfer, deep learning, framework compatibility
-
-.. version-set:: rocm_version latest
-
-********************************************************************************
-FlashInfer compatibility
-********************************************************************************
-
-`FlashInfer <https://docs.flashinfer.ai/index.html>`__ is a library and kernel generator 
-for Large Language Models (LLMs) that provides a high-performance implementation of graphics 
-processing units (GPUs) kernels. FlashInfer focuses on LLM serving and inference, as well 
-as advanced performance across diverse scenarios.
-
-FlashInfer features highly efficient attention kernels, load-balanced scheduling, and memory-optimized 
-techniques, while supporting customized attention variants. It’s compatible with ``torch.compile``, and 
-offers high-performance LLM-specific operators, with easy integration through PyTorch, and C++ APIs.
-
-.. note::
-
-  The ROCm port of FlashInfer is under active development, and some features are not yet available. 
-  For the latest feature compatibility matrix, refer to the ``README`` of the 
-  `https://github.com/ROCm/flashinfer <https://github.com/ROCm/flashinfer>`__ repository.
-
-Support overview
-================================================================================
-
-- The ROCm-supported version of FlashInfer is maintained in the official `https://github.com/ROCm/flashinfer 
-  <https://github.com/ROCm/flashinfer>`__ repository, which differs from the 
-  `https://github.com/flashinfer-ai/flashinfer <https://github.com/flashinfer-ai/flashinfer>`__ 
-  upstream repository.
-
-- To get started and install FlashInfer on ROCm, use the prebuilt :ref:`Docker images <flashinfer-docker-compat>`, 
-  which include ROCm, FlashInfer, and all required dependencies.
-
-  - See the :doc:`ROCm FlashInfer installation guide <rocm-install-on-linux:install/3rd-party/flashinfer-install>` 
-    for installation and setup instructions.
-
-  - You can also consult the upstream `Installation guide <https://docs.flashinfer.ai/installation.html>`__ 
-    for additional context.
-
-.. _flashinfer-docker-compat:
-
-Compatibility matrix
-================================================================================
-
-.. |docker-icon| raw:: html
-
-   <i class="fab fa-docker"></i>
-
-AMD validates and publishes `FlashInfer images <https://hub.docker.com/r/rocm/flashinfer/tags>`__
-with ROCm backends on Docker Hub. The following Docker image tag and associated
-inventories represent the latest available FlashInfer version from the official Docker Hub. 
-Click |docker-icon| to view the image on Docker Hub.
-
-.. list-table:: 
-    :header-rows: 1
-    :class: docker-image-compatibility
-
-    * - Docker image
-      - ROCm
-      - FlashInfer
-      - PyTorch
-      - Ubuntu
-      - Python
-      - GPU
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/flashinfer/flashinfer-0.2.5.amd2_rocm7.1.1_ubuntu24.04_py3.12_pytorch2.8/images/sha256-9ab6426750a11dbab9bcddeaccaf492683bfd96a1d60b21dd9fc3a609a98175b"><i class="fab fa-docker fa-lg"></i> rocm/flashinfer</a>
-      - `7.1.1 <https://repo.radeon.com/rocm/apt/7.1.1/>`__
-      - `v0.2.5 <https://github.com/flashinfer-ai/flashinfer/releases/tag/v0.2.5>`__
-      - `2.8.0 <https://github.com/ROCm/pytorch/releases/tag/v2.8.0>`__
-      - 24.04
-      - `3.12 <https://www.python.org/downloads/release/python-3129/>`__
-      - MI325X, MI300X
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/flashinfer/flashinfer-0.2.5_rocm6.4_ubuntu24.04_py3.12_pytorch2.7/images/sha256-558914838821c88c557fb6d42cfbc1bdb67d79d19759f37c764a9ee801f93313"><i class="fab fa-docker fa-lg"></i> rocm/flashinfer</a>
-      - `6.4.1 <https://repo.radeon.com/rocm/apt/6.4.1/>`__
-      - `v0.2.5 <https://github.com/flashinfer-ai/flashinfer/releases/tag/v0.2.5>`__
-      - `2.7.1 <https://github.com/ROCm/pytorch/releases/tag/v2.7.1>`__
-      - 24.04
-      - `3.12 <https://www.python.org/downloads/release/python-3129/>`__
-      - MI300X
-
-.. _flashinfer-recommendations:
-
-Use cases and recommendations
-================================================================================
-
-FlashInfer on ROCm enables you to perform LLM inference for both prefill and decode:
-during prefill, your model efficiently processes input prompts to build KV caches
-and internal activations; during decode, it generates tokens sequentially based on
-prior outputs and context. Use the attention mode supported upstream (Multi-Head
-Attention, Grouped-Query Attention, or Multi-Query Attention) that matches your
-model configuration.
-
-FlashInfer on ROCm also includes capabilities such as load balancing, 
-sparse and dense attention optimizations, and single and batch decode, alongside
-prefill for high‑performance execution on MI300X GPUs.
-
-For currently supported use cases and recommendations, refer to the `AMD ROCm blog <https://rocm.blogs.amd.com/search.html?q=flashinfer>`__, 
-where you can search for examples and best practices to optimize your workloads on AMD GPUs.
-
-Previous versions
-===============================================================================
-See :doc:`rocm-install-on-linux:install/3rd-party/previous-versions/flashinfer-history` to find documentation for previous releases
-of the ``ROCm/flashinfer`` Docker image.

docs/compatibility/ml-compatibility/llama-cpp-compatibility.rst

@@ -1,275 +0,0 @@
-:orphan:
-
-.. meta::
-    :description: llama.cpp compatibility
-    :keywords: GPU, GGML, llama.cpp, deep learning, framework compatibility
-
-.. version-set:: rocm_version latest
-
-********************************************************************************
-llama.cpp compatibility
-********************************************************************************
-
-`llama.cpp <https://github.com/ggml-org/llama.cpp>`__ is an open-source framework 
-for Large Language Model (LLM) inference that runs on both central processing units 
-(CPUs) and graphics processing units (GPUs). It is written in plain C/C++, providing 
-a simple, dependency-free setup. 
-
-The framework supports multiple quantization options, from 1.5-bit to 8-bit integers, 
-to accelerate inference and reduce memory usage. Originally built as a CPU-first library, 
-llama.cpp is easy to integrate with other programming environments and is widely 
-adopted across diverse platforms, including consumer devices. 
-
-Support overview
-================================================================================
-
-- The ROCm-supported version of llama.cpp is maintained in the official `https://github.com/ROCm/llama.cpp 
-  <https://github.com/ROCm/llama.cpp>`__ repository, which differs from the 
-  `https://github.com/ggml-org/llama.cpp <https://github.com/ggml-org/llama.cpp>`__ upstream repository.
-
-- To get started and install llama.cpp on ROCm, use the prebuilt :ref:`Docker images <llama-cpp-docker-compat>`, 
-  which include ROCm, llama.cpp, and all required dependencies.
-
-  - See the :doc:`ROCm llama.cpp installation guide <rocm-install-on-linux:install/3rd-party/llama-cpp-install>` 
-    for installation and setup instructions.
-
-  - You can also consult the upstream `Installation guide <https://github.com/ggml-org/llama.cpp/blob/master/docs/build.md>`__ 
-    for additional context.
-
-.. _llama-cpp-docker-compat:
-
-Compatibility matrix
-================================================================================
-
-.. |docker-icon| raw:: html
-
-   <i class="fab fa-docker"></i>
-
-AMD validates and publishes `llama.cpp images <https://hub.docker.com/r/rocm/llama.cpp/tags>`__
-with ROCm backends on Docker Hub. The following Docker image tags and associated
-inventories represent the latest available llama.cpp versions from the official Docker Hub.
-Click |docker-icon| to view the image on Docker Hub.
-
-.. important::
-
-   Tag endings of ``_full``, ``_server``, and ``_light`` serve different purposes for entrypoints as follows:
-
-   - Full: This image includes both the main executable file and the tools to convert ``LLaMA`` models into ``ggml`` and convert into 4-bit quantization.
-   - Server: This image only includes the server executable file.
-   - Light: This image only includes the main executable file.
-
-.. list-table::
-    :header-rows: 1
-    :class: docker-image-compatibility
-
-    * - Full Docker
-      - Server Docker
-      - Light Docker
-      - llama.cpp
-      - ROCm
-      - Ubuntu
-      - GPU
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6652.amd0_rocm7.0.0_ubuntu24.04_full/images/sha256-a94f0c7a598cc6504ff9e8371c016d7a2f93e69bf54a36c870f9522567201f10g"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6652.amd0_rocm7.0.0_ubuntu24.04_server/images/sha256-be175932c3c96e882dfbc7e20e0e834f58c89c2925f48b222837ee929dfc47ee"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6652.amd0_rocm7.0.0_ubuntu24.04_light/images/sha256-d8ba0c70603da502c879b1f8010b439c8e7fa9f6cbdac8bbbbbba97cb41ebc9e"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - `b6652 <https://github.com/ROCm/llama.cpp/tree/release/b6652>`__
-      - `7.0.0 <https://repo.radeon.com/rocm/apt/7.0/>`__
-      - 24.04
-      - MI325X, MI300X, MI210
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6652.amd0_rocm7.0.0_ubuntu22.04_full/images/sha256-37582168984f25dce636cc7288298e06d94472ea35f65346b3541e6422b678ee"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6652.amd0_rocm7.0.0_ubuntu22.04_server/images/sha256-7e70578e6c3530c6591cc2c26da24a9ee68a20d318e12241de93c83224f83720"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6652.amd0_rocm7.0.0_ubuntu22.04_light/images/sha256-9a5231acf88b4a229677bc2c636ea3fe78a7a80f558bd80910b919855de93ad5"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - `b6652 <https://github.com/ROCm/llama.cpp/tree/release/b6652>`__
-      - `7.0.0 <https://repo.radeon.com/rocm/apt/7.0/>`__
-      - 22.04
-      - MI325X, MI300X, MI210
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.3_ubuntu24.04_full/images/sha256-5960fc850024a8a76451f9eaadd89b7e59981ae9f393b407310c1ddf18892577"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.3_ubuntu24.04_server/images/sha256-1b79775d9f546065a6aaf9ca426e1dd4ed4de0b8f6ee83687758cc05af6538e6"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.3_ubuntu24.04_light/images/sha256-8f863c4c2857ae42bebd64e4f1a0a1e7cc3ec4503f243e32b4a4dcad070ec361"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - `b6356 <https://github.com/ROCm/llama.cpp/tree/release/b6356>`__
-      - `6.4.3 <https://repo.radeon.com/rocm/apt/6.4.3/>`__
-      - 24.04
-      - MI325X, MI300X, MI210
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.3_ubuntu22.04_full/images/sha256-888879b3ee208f9247076d7984524b8d1701ac72611689e89854a1588bec9867"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.3_ubuntu22.04_server/images/sha256-90e4ff99a66743e33fd00728cd71a768588e5f5ef355aaa196669fe65ac70672"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.3_ubuntu22.04_light/images/sha256-bd447a049939cb99054f8fbf3f2352870fe906a75e2dc3339c845c08b9c53f9b"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - `b6356 <https://github.com/ROCm/llama.cpp/tree/release/b6356>`__
-      - `6.4.3 <https://repo.radeon.com/rocm/apt/6.4.3/>`__
-      - 22.04
-      - MI325X, MI300X, MI210
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.2_ubuntu24.04_full/images/sha256-5b3a1bc4889c1fcade434b937fbf9cc1c22ff7dc0317c130339b0c9238bc88c4"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.2_ubuntu24.04_server/images/sha256-5228ff99d0f627a9032d668f4381b2e80dc1e301adc3e0821f26d8354b175271"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.2_ubuntu24.04_light/images/sha256-b12723b332a826a89b7252dddf868cbe4d1a869562fc4aa4032f59e1a683b968"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - `b6356 <https://github.com/ROCm/llama.cpp/tree/release/b6356>`__
-      - `6.4.2 <https://repo.radeon.com/rocm/apt/6.4.2/>`__
-      - 24.04
-      - MI325X, MI300X, MI210
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.2_ubuntu22.04_full/images/sha256-cd6e21a6a73f59b35dd5309b09dd77654a94d783bf13a55c14eb8dbf8e9c2615"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.2_ubuntu22.04_server/images/sha256-c2b4689ab2c47e6626e8fea22d7a63eb03d47c0fde9f5ef8c9f158d15c423e58"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.2_ubuntu22.04_light/images/sha256-1acc28f29ed87db9cbda629cb29e1989b8219884afe05f9105522be929e94da4"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - `b6356 <https://github.com/ROCm/llama.cpp/tree/release/b6356>`__
-      - `6.4.2 <https://repo.radeon.com/rocm/apt/6.4.2/>`__
-      - 22.04
-      - MI325X, MI300X, MI210
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.1_ubuntu24.04_full/images/sha256-2f8ae8a44510d96d52dea6cb398b224f7edeb7802df7ec488c6f63d206b3cdc9"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.1_ubuntu24.04_server/images/sha256-fece497ff9f4a28b12f645de52766941da8ead8471aa1ea84b61d4b4568e51f2"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.1_ubuntu24.04_light/images/sha256-3e14352fa6f8c6128b23cf9342531c20dbfb522550b626e09d83b260a1947022"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - `b6356 <https://github.com/ROCm/llama.cpp/tree/release/b6356>`__
-      - `6.4.1 <https://repo.radeon.com/rocm/apt/6.4.1/>`__
-      - 24.04
-      - MI325X, MI300X, MI210
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.1_ubuntu22.04_full/images/sha256-80763062ef0bec15038c35fd01267f1fc99a5dd171d4b48583cc668b15efad69"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.1_ubuntu22.04_server/images/sha256-db2a6c957555ed83b819bbc54aea884a93192da0fb512dae63d32e0dc4e8ab8f"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b6356_rocm6.4.1_ubuntu22.04_light/images/sha256-c6dbb07cc655fb079d5216e4b77451cb64a9daa0585d23b6fb8b32cb22021197"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - `b6356 <https://github.com/ROCm/llama.cpp/tree/release/b6356>`__
-      - `6.4.1 <https://repo.radeon.com/rocm/apt/6.4.1/>`__
-      - 22.04
-      - MI325X, MI300X, MI210
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b5997_rocm6.4.0_ubuntu24.04_full/images/sha256-f78f6c81ab2f8e957469415fe2370a1334fe969c381d1fe46050c85effaee9d5"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b5997_rocm6.4.0_ubuntu24.04_server/images/sha256-275ad9e18f292c26a00a2de840c37917e98737a88a3520bdc35fd3fc5c9a6a9b"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/llama.cpp/llama.cpp-b5997_rocm6.4.0_ubuntu24.04_light/images/sha256-cc324e6faeedf0e400011f07b49d2dc41a16bae257b2b7befa0f4e2e97231320"><i class="fab fa-docker fa-lg"></i> rocm/llama.cpp</a>
-      - `b5997 <https://github.com/ROCm/llama.cpp/tree/release/b5997>`__
-      - `6.4.0 <https://repo.radeon.com/rocm/apt/6.4/>`__
-      - 24.04
-      - MI300X, MI210
-
-.. _llama-cpp-key-rocm-libraries:
-
-Key ROCm libraries for llama.cpp
-================================================================================
-
-llama.cpp functionality on ROCm is determined by its underlying library
-dependencies. These ROCm components affect the capabilities, performance, and
-feature set available to developers. Ensure you have the required libraries for 
-your corresponding ROCm version.
-
-.. list-table::
-    :header-rows: 1
-
-    * - ROCm library
-      - ROCm 7.0.0 version
-      - ROCm 6.4.x version
-      - Purpose
-      - Usage
-    * - `hipBLAS <https://github.com/ROCm/hipBLAS>`__
-      - 3.0.0
-      - 2.4.0
-      - Provides GPU-accelerated Basic Linear Algebra Subprograms (BLAS) for
-        matrix and vector operations.
-      - Supports operations such as matrix multiplication, matrix-vector
-        products, and tensor contractions. Utilized in both dense and batched
-        linear algebra operations.
-    * - `hipBLASLt <https://github.com/ROCm/hipBLASLt>`__
-      - 1.0.0
-      - 0.12.0
-      - hipBLASLt is an extension of the hipBLAS library, providing additional
-        features like epilogues fused into the matrix multiplication kernel or
-        use of integer tensor cores.
-      - By setting the flag ``ROCBLAS_USE_HIPBLASLT``, you can dispatch hipblasLt
-        kernels where possible.
-    * - `rocWMMA <https://github.com/ROCm/rocWMMA>`__
-      - 2.0.0
-      - 1.7.0
-      - Accelerates warp-level matrix-multiply and matrix-accumulate to speed up matrix
-        multiplication (GEMM) and accumulation operations with mixed precision
-        support.
-      - Can be used to enhance the flash attention performance on AMD compute, by enabling
-        the flag during compile time.
-
-.. _llama-cpp-uses-recommendations:
-
-Use cases and recommendations
-================================================================================
-
-llama.cpp can be applied in a variety of scenarios, particularly when you need to meet one or more of the following requirements:
-
-- Plain C/C++ implementation with no external dependencies
-- Support for 1.5-bit, 2-bit, 3-bit, 4-bit, 5-bit, 6-bit, and 8-bit integer quantization for faster inference and reduced memory usage
-- Custom HIP (Heterogeneous-compute Interface for Portability) kernels for running large language models (LLMs) on AMD GPUs (graphics processing units)
-- CPU (central processing unit) + GPU (graphics processing unit) hybrid inference for partially accelerating models larger than the total available VRAM (video random-access memory)
-
-llama.cpp is also used in a range of real-world applications, including:
-
-- Games such as `Lucy's Labyrinth <https://github.com/MorganRO8/Lucys_Labyrinth>`__:
-  A simple maze game where AI-controlled agents attempt to trick the player.
-- Tools such as `Styled Lines <https://marketplace.unity.com/packages/tools/ai-ml-integration/style-text-webgl-ios-stand-alone-llm-llama-cpp-wrapper-292902>`__:
-  A proprietary, asynchronous inference wrapper for Unity3D game development, including pre-built mobile and web platform wrappers and a model example.
-- Various other AI applications use llama.cpp as their inference engine;  
-  for a detailed list, see the `user interfaces (UIs) section <https://github.com/ggml-org/llama.cpp?tab=readme-ov-file#description>`__.
-
-For more use cases and recommendations, refer to the `AMD ROCm blog <https://rocm.blogs.amd.com/>`__, 
-where you can search for llama.cpp examples and best practices to optimize your workloads on AMD GPUs.
-
-- The `Llama.cpp Meets Instinct: A New Era of Open-Source AI Acceleration <https://rocm.blogs.amd.com/ecosystems-and-partners/llama-cpp/README.html>`__ 
-  blog post outlines how the open-source llama.cpp framework enables efficient LLM inference—including interactive inference with ``llama-cli``, 
-  server deployment with ``llama-server``, GGUF model preparation and quantization, performance benchmarking, and optimizations tailored for 
-  AMD Instinct GPUs within the ROCm ecosystem. 
-
-
-Previous versions
-===============================================================================
-See :doc:`rocm-install-on-linux:install/3rd-party/previous-versions/llama-cpp-history` to find documentation for previous releases
-of the ``ROCm/llama.cpp`` Docker image.

docs/compatibility/ml-compatibility/megablocks-compatibility.rst

@@ -1,104 +0,0 @@
-:orphan:
-
-.. meta::
-    :description: Megablocks compatibility
-    :keywords: GPU, megablocks, deep learning, framework compatibility
-
-.. version-set:: rocm_version latest
-
-********************************************************************************
-Megablocks compatibility
-********************************************************************************
-
-`Megablocks <https://github.com/databricks/megablocks>`__ is a lightweight library 
-for mixture-of-experts `(MoE) <https://huggingface.co/blog/moe>`__ training. 
-The core of the system is efficient "dropless-MoE" and standard MoE layers. 
-Megablocks is integrated with `https://github.com/stanford-futuredata/Megatron-LM 
-<https://github.com/stanford-futuredata/Megatron-LM>`__, 
-where data and pipeline parallel training of MoEs is supported.
-
-Support overview
-================================================================================
-
-- The ROCm-supported version of Megablocks is maintained in the official `https://github.com/ROCm/megablocks 
-  <https://github.com/ROCm/megablocks>`__ repository, which differs from the 
-  `https://github.com/stanford-futuredata/Megatron-LM <https://github.com/stanford-futuredata/Megatron-LM>`__ upstream repository.
-
-- To get started and install Megablocks on ROCm, use the prebuilt :ref:`Docker image <megablocks-docker-compat>`, 
-  which includes ROCm, Megablocks, and all required dependencies.
-
-  - See the :doc:`ROCm Megablocks installation guide <rocm-install-on-linux:install/3rd-party/megablocks-install>` 
-    for installation and setup instructions.
-
-  - You can also consult the upstream `Installation guide <https://github.com/databricks/megablocks>`__ 
-    for additional context.
-
-.. _megablocks-docker-compat:
-
-Compatibility matrix
-================================================================================
-
-.. |docker-icon| raw:: html
-
-   <i class="fab fa-docker"></i>
-
-AMD validates and publishes `Megablocks images <https://hub.docker.com/r/rocm/megablocks/tags>`__
-with ROCm backends on Docker Hub. The following Docker image tag and associated
-inventories represent the latest available Megablocks version from the official Docker Hub. 
-Click |docker-icon| to view the image on Docker Hub.
-
-.. list-table:: 
-    :header-rows: 1
-    :class: docker-image-compatibility
-
-    * - Docker image
-      - ROCm
-      - Megablocks
-      - PyTorch
-      - Ubuntu
-      - Python
-      - GPU
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/megablocks/megablocks-0.7.0_rocm6.3.0_ubuntu24.04_py3.12_pytorch2.4.0/images/sha256-372ff89b96599019b8f5f9db469c84add2529b713456781fa62eb9a148659ab4"><i class="fab fa-docker fa-lg"></i> rocm/megablocks</a>
-      - `6.3.0 <https://repo.radeon.com/rocm/apt/6.3/>`_
-      - `0.7.0 <https://github.com/databricks/megablocks/releases/tag/v0.7.0>`_
-      - `2.4.0 <https://github.com/ROCm/pytorch/tree/release/2.4>`_
-      - 24.04
-      - `3.12.9 <https://www.python.org/downloads/release/python-3129/>`_
-      - MI300X
-
-Supported models and features with ROCm 6.3.0
-================================================================================
-
-This section summarizes the Megablocks features supported by ROCm.
-
-* Distributed Pre-training
-* Activation Checkpointing and Recomputation
-* Distributed Optimizer
-* Mixture-of-Experts
-* dropless-Mixture-of-Experts
-
-.. _megablocks-recommendations:
-
-Use cases and recommendations
-================================================================================
-
-* The `Efficient MoE training on AMD ROCm: How-to use Megablocks on AMD GPUs 
-  <https://rocm.blogs.amd.com/artificial-intelligence/megablocks/README.html>`__ 
-  blog post guides how to leverage the ROCm platform for pre-training using the 
-  Megablocks framework. It introduces a streamlined approach for training Mixture-of-Experts 
-  (MoE) models using the Megablocks library on AMD hardware. Focusing on GPT-2, it 
-  demonstrates how block-sparse computations can enhance scalability and efficiency in MoE 
-  training. The guide provides step-by-step instructions for setting up the environment, 
-  including cloning the repository, building the Docker image, and running the training container. 
-  Additionally, it offers insights into utilizing the ``oscar-1GB.json`` dataset for pre-training 
-  language models. By leveraging Megablocks and the ROCm platform, you can optimize your MoE 
-  training workflows for large-scale transformer models.
-
-It features how to pre-process datasets and how to begin pre-training on AMD GPUs through:
-
-* Single-GPU pre-training
-* Multi-GPU pre-training
-

docs/compatibility/ml-compatibility/ray-compatibility.rst

@@ -1,114 +0,0 @@
-:orphan:
-
-.. meta::
-    :description: Ray compatibility
-    :keywords: GPU, Ray, deep learning, framework compatibility
-
-.. version-set:: rocm_version latest
-
-*******************************************************************************
-Ray compatibility
-*******************************************************************************
-
-Ray is a unified framework for scaling AI and Python applications from your laptop 
-to a full cluster, without changing your code. Ray consists of `a core distributed 
-runtime  <https://docs.ray.io/en/latest/ray-core/walkthrough.html>`__ and a set of 
-`AI libraries <https://docs.ray.io/en/latest/ray-air/getting-started.html>`__ for 
-simplifying machine learning computations.
-
-Ray is a general-purpose framework that runs many types of workloads efficiently. 
-Any Python application can be scaled with Ray, without extra infrastructure.
-
-Support overview
-================================================================================
-
-- The ROCm-supported version of Ray is maintained in the official `https://github.com/ROCm/ray 
-  <https://github.com/ROCm/ray>`__ repository, which differs from the 
-  `https://github.com/ray-project/ray <https://github.com/ray-project/ray>`__ upstream repository.
-
-- To get started and install Ray on ROCm, use the prebuilt :ref:`Docker image <ray-docker-compat>`, 
-  which includes ROCm, Ray, and all required dependencies.
-
-  - See the :doc:`ROCm Ray installation guide <rocm-install-on-linux:install/3rd-party/ray-install>`
-    for installation and setup instructions.
-
-  - You can also consult the upstream `Installation guide <https://docs.ray.io/en/latest/ray-overview/installation.html>`__ 
-    for additional context.
-
-.. _ray-docker-compat:
-
-Compatibility matrix
-================================================================================
-
-.. |docker-icon| raw:: html
-
-   <i class="fab fa-docker"></i>
-
-AMD validates and publishes `ROCm Ray Docker images <https://hub.docker.com/r/rocm/ray/tags>`__
-with ROCm backends on Docker Hub. The following Docker image tags and
-associated inventories represent the latest Ray version from the official Docker Hub.
-Click |docker-icon| to view the image on Docker Hub.
-
-.. list-table::
-    :header-rows: 1
-    :class: docker-image-compatibility
-
-    * - Docker image
-      - ROCm
-      - Ray
-      - Pytorch
-      - Ubuntu
-      - Python
-      - GPU
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/ray/ray-2.51.1_rocm7.0.0_ubuntu22.04_py3.12_pytorch2.9.0/images/sha256-a02f6766b4ba406f88fd7e85707ec86c04b569834d869a08043ec9bcbd672168"><i class="fab fa-docker fa-lg"></i> rocm/ray</a>
-      - `7.0.0 <https://repo.radeon.com/rocm/apt/7.0/>`__
-      - `2.51.1 <https://github.com/ROCm/ray/tree/release/2.51.1>`__
-      - 2.9.0a0+git1c57644
-      - 22.04
-      - `3.12.12 <https://www.python.org/downloads/release/python-31212/>`__
-      - MI300X
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/ray/ray-2.48.0.post0_rocm6.4.1_ubuntu24.04_py3.12_pytorch2.6.0/images/sha256-0d166fe6bdced38338c78eedfb96eff92655fb797da3478a62dd636365133cc0"><i class="fab fa-docker fa-lg"></i> rocm/ray</a>
-      - `6.4.1 <https://repo.radeon.com/rocm/apt/6.4.1/>`__
-      - `2.48.0.post0 <https://github.com/ROCm/ray/tree/release/2.48.0.post0>`__
-      - 2.6.0+git684f6f2
-      - 24.04
-      - `3.12.10 <https://www.python.org/downloads/release/python-31210/>`__
-      - MI300X, MI210
-
-Use cases and recommendations
-================================================================================
-
-* The `Reinforcement Learning from Human Feedback on AMD GPUs with verl and ROCm 
-  Integration <https://rocm.blogs.amd.com/artificial-intelligence/verl-large-scale/README.html>`__  
-  blog provides an overview of Volcano Engine Reinforcement Learning (verl) 
-  for large language models (LLMs) and discusses its benefits in large-scale 
-  reinforcement learning from human feedback (RLHF). It uses Ray as part of a 
-  hybrid orchestration engine to schedule and coordinate training and inference 
-  tasks in parallel, enabling optimized resource utilization and potential overlap 
-  between these phases. This dynamic resource allocation strategy significantly 
-  improves overall system efficiency. The blog presents verl’s performance results, 
-  focusing on throughput and convergence accuracy achieved on AMD Instinct™ MI300X 
-  GPUs. Follow this guide to get started with verl on AMD Instinct GPUs and 
-  accelerate your RLHF training with ROCm-optimized performance.
-
-* The `Exploring Use Cases for Scalable AI: Implementing Ray with ROCm Support for Efficient ML Workflows 
-  <https://rocm.blogs.amd.com/artificial-intelligence/rocm-ray/README.html>`__
-  blog post describes key use cases such as training and inference for large language models (LLMs), 
-  model serving, hyperparameter tuning, reinforcement learning, and the orchestration of large-scale 
-  workloads using Ray in the ROCm environment.
-
-For more use cases and recommendations, see the AMD GPU tabs in the `Accelerator Support 
-topic <https://docs.ray.io/en/latest/ray-core/scheduling/accelerators.html#accelerator-support>`__ 
-of the Ray core documentation and refer to the `AMD ROCm blog <https://rocm.blogs.amd.com/>`__, 
-where you can search for Ray examples and best practices to optimize your workloads on AMD GPUs.
-
-Previous versions
-===============================================================================
-See :doc:`rocm-install-on-linux:install/3rd-party/previous-versions/ray-history` to find documentation for previous releases
-of the ``ROCm/ray`` Docker image.

docs/compatibility/ml-compatibility/stanford-megatron-lm-compatibility.rst

@@ -1,116 +0,0 @@
-:orphan:
-
-.. meta::
-    :description: Stanford Megatron-LM compatibility
-    :keywords: Stanford, Megatron-LM, deep learning, framework compatibility
-
-.. version-set:: rocm_version latest
-
-********************************************************************************
-Stanford Megatron-LM compatibility
-********************************************************************************
-
-Stanford Megatron-LM is a large-scale language model training framework developed 
-by NVIDIA at `https://github.com/NVIDIA/Megatron-LM <https://github.com/NVIDIA/Megatron-LM>`_. 
-It is designed to train massive transformer-based language models efficiently by model 
-and data parallelism. 
-
-It provides efficient tensor, pipeline, and sequence-based model parallelism for 
-pre-training transformer-based language models such as GPT (Decoder Only), BERT 
-(Encoder Only), and T5 (Encoder-Decoder). 
-
-Support overview
-================================================================================
-
-- The ROCm-supported version of Stanford Megatron-LM is maintained in the official `https://github.com/ROCm/Stanford-Megatron-LM 
-  <https://github.com/ROCm/Stanford-Megatron-LM>`__ repository, which differs from the 
-  `https://github.com/stanford-futuredata/Megatron-LM <https://github.com/stanford-futuredata/Megatron-LM>`__ upstream repository.
-
-- To get started and install Stanford Megatron-LM on ROCm, use the prebuilt :ref:`Docker image <megatron-lm-docker-compat>`, 
-  which includes ROCm, Stanford Megatron-LM, and all required dependencies.
-
-  - See the :doc:`ROCm Stanford Megatron-LM installation guide <rocm-install-on-linux:install/3rd-party/stanford-megatron-lm-install>` 
-    for installation and setup instructions.
-
-  - You can also consult the upstream `Installation guide <https://github.com/NVIDIA/Megatron-LM>`__ 
-    for additional context.
-
-.. _megatron-lm-docker-compat:
-
-Compatibility matrix
-================================================================================
-
-.. |docker-icon| raw:: html
-
-   <i class="fab fa-docker"></i>
-
-AMD validates and publishes `Stanford Megatron-LM images <https://hub.docker.com/r/rocm/stanford-megatron-lm/tags>`_
-with ROCm and Pytorch backends on Docker Hub. The following Docker image tags and associated
-inventories represent the latest Stanford Megatron-LM version from the official Docker Hub.
-Click |docker-icon| to view the image on Docker Hub.
-
-.. list-table:: 
-    :header-rows: 1
-    :class: docker-image-compatibility
-
-    * - Docker image
-      - ROCm
-      - Stanford Megatron-LM
-      - PyTorch
-      - Ubuntu
-      - Python
-      - GPU
-
-    * - .. raw:: html
-
-           <a href="https://hub.docker.com/layers/rocm/stanford-megatron-lm/stanford-megatron-lm85f95ae_rocm6.3.0_ubuntu24.04_py3.12_pytorch2.4.0/images/sha256-070556f078be10888a1421a2cb4f48c29f28b02bfeddae02588d1f7fc02a96a6"><i class="fab fa-docker fa-lg"></i> rocm/stanford-megatron-lm</a>
-
-      - `6.3.0 <https://repo.radeon.com/rocm/apt/6.3/>`_
-      - `85f95ae <https://github.com/stanford-futuredata/Megatron-LM/commit/85f95aef3b648075fe6f291c86714fdcbd9cd1f5>`_
-      - `2.4.0 <https://github.com/ROCm/pytorch/tree/release/2.4>`_
-      - 24.04
-      - `3.12.9 <https://www.python.org/downloads/release/python-3129/>`_
-      - MI300X
-
-Supported models and features with ROCm 6.3.0
-================================================================================
-
-This section details models & features that are supported by the ROCm version on Stanford Megatron-LM.
-
-Models:
-
-* BERT
-* GPT
-* T5
-* ICT
-
-Features:
-
-* Distributed Pre-training
-* Activation Checkpointing and Recomputation
-* Distributed Optimizer
-* Mixture-of-Experts
-
-.. _megatron-lm-recommendations:
-
-Use cases and recommendations
-================================================================================
-
-The following blog post mentions Megablocks, but you can run Stanford Megatron-LM with the same steps to pre-process datasets on AMD GPUs:
-
-* The `Efficient MoE training on AMD ROCm: How-to use Megablocks on AMD GPUs 
-  <https://rocm.blogs.amd.com/artificial-intelligence/megablocks/README.html>`__ 
-  blog post guides how to leverage the ROCm platform for pre-training using the 
-  Megablocks framework. It introduces a streamlined approach for training Mixture-of-Experts 
-  (MoE) models using the Megablocks library on AMD hardware. Focusing on GPT-2, it 
-  demonstrates how block-sparse computations can enhance scalability and efficiency in MoE 
-  training. The guide provides step-by-step instructions for setting up the environment, 
-  including cloning the repository, building the Docker image, and running the training container. 
-  Additionally, it offers insights into utilizing the ``oscar-1GB.json`` dataset for pre-training 
-  language models. By leveraging Megablocks and the ROCm platform, you can optimize your MoE 
-  training workflows for large-scale transformer models.
-
-It features how to pre-process datasets and how to begin pre-training on AMD GPUs through:
-
-* Single-GPU pre-training
-* Multi-GPU pre-training

docs/compatibility/ml-compatibility/verl-compatibility.rst

@@ -1,118 +0,0 @@
-:orphan:
-
-.. meta::
-   :description: verl compatibility
-   :keywords: GPU, verl, deep learning, framework compatibility
-
-.. version-set:: rocm_version latest
-
-*******************************************************************************
-verl compatibility
-*******************************************************************************
-
-Volcano Engine Reinforcement Learning for LLMs (`verl <https://verl.readthedocs.io/en/latest/>`__)  
-is a reinforcement learning framework designed for large language models (LLMs). 
-verl offers a scalable, open-source fine-tuning solution by using a hybrid programming model 
-that makes it easy to define and run complex post-training dataflows efficiently. 
-
-Its modular APIs separate computation from data, allowing smooth integration with other frameworks. 
-It also supports flexible model placement across GPUs for efficient scaling on different cluster sizes.
-verl achieves high training and generation throughput by building on existing LLM frameworks. 
-Its 3D-HybridEngine reduces memory use and communication overhead when switching between training 
-and inference, improving overall performance.
-
-Support overview
-================================================================================
-
-- The ROCm-supported version of verl is maintained in the official `https://github.com/ROCm/verl 
-  <https://github.com/ROCm/verl>`__ repository, which differs from the 
-  `https://github.com/volcengine/verl <https://github.com/volcengine/verl>`__ upstream repository.
-
-- To get started and install verl on ROCm, use the prebuilt :ref:`Docker image <verl-docker-compat>`, 
-  which includes ROCm, verl, and all required dependencies.
-
-  - See the :doc:`ROCm verl installation guide <rocm-install-on-linux:install/3rd-party/verl-install>`
-    for installation and setup instructions.
-
-  - You can also consult the upstream `verl documentation <https://verl.readthedocs.io/en/latest/>`__ 
-    for additional context.
-
-.. _verl-docker-compat:
-
-Compatibility matrix
-================================================================================
-
-.. |docker-icon| raw:: html
-
-   <i class="fab fa-docker"></i>
-
-AMD validates and publishes `verl Docker images <https://hub.docker.com/r/rocm/verl/tags>`_
-with ROCm backends on Docker Hub. The following Docker image tag and associated inventories 
-represent the latest verl version from the official Docker Hub. 
-Click |docker-icon| to view the image on Docker Hub.
-
-.. list-table::
-   :header-rows: 1
-   :class: docker-image-compatibility
-
-   * - Docker image
-     - ROCm
-     - verl
-     - Ubuntu
-     - PyTorch
-     - Python
-     - vllm
-     - GPU
-
-   * - .. raw:: html
-
-        <a href="https://hub.docker.com/layers/rocm/verl/verl-0.6.0.amd0_rocm7.0_vllm0.11.0.dev/images/sha256-f70a3ebc94c1f66de42a2fcc3f8a6a8d6d0881eb0e65b6958d7d6d24b3eecb0d"><i class="fab fa-docker fa-lg"></i> rocm/verl</a>
-     - `7.0.0 <https://repo.radeon.com/rocm/apt/7.0/>`__
-     - `0.6.0 <https://github.com/volcengine/verl/releases/tag/v0.6.0>`__
-     - 22.04
-     - `2.9.0 <https://github.com/ROCm/pytorch/tree/release/2.9-rocm7.x-gfx115x>`__
-     - `3.12.11 <https://www.python.org/downloads/release/python-31211/>`__
-     - `0.11.0 <https://github.com/vllm-project/vllm/releases/tag/v0.11.0>`__
-     - MI300X
-
-   * - .. raw:: html
-
-        <a href="https://hub.docker.com/layers/rocm/verl/verl-0.3.0.post0_rocm6.2_vllm0.6.3/images/sha256-cbe423803fd7850448b22444176bee06f4dcf22cd3c94c27732752d3a39b04b2"><i class="fab fa-docker fa-lg"></i> rocm/verl</a>
-     - `6.2.0 <https://repo.radeon.com/rocm/apt/6.2/>`__
-     - `0.3.0.post0 <https://github.com/volcengine/verl/releases/tag/v0.3.0.post0>`__
-     - 20.04
-     - `2.5.0 <https://github.com/ROCm/pytorch/tree/release/2.5>`__
-     - `3.9.19 <https://www.python.org/downloads/release/python-3919/>`__
-     - `0.6.3 <https://github.com/vllm-project/vllm/releases/tag/v0.6.3>`__
-     - MI300X
-
-.. _verl-supported_features:
-
-Supported modules with verl on ROCm
-===============================================================================
-
-The following GPU-accelerated modules are supported with verl on ROCm:
-
-- ``FSDP``: Training engine
-- ``vllm``: Inference engine
-
-.. _verl-recommendations:
-
-Use cases and recommendations
-================================================================================
-
-* The benefits of verl in large-scale reinforcement learning from human feedback 
-  (RLHF) are discussed in the `Reinforcement Learning from Human Feedback on AMD 
-  GPUs with verl and ROCm Integration <https://rocm.blogs.amd.com/artificial-intelligence/verl-large-scale/README.html>`__ 
-  blog. The blog post outlines how the Volcano Engine Reinforcement Learning 
-  (verl) framework integrates with the AMD ROCm platform to optimize training on 
-  AMD Instinct™ GPUs. The guide details the process of building a Docker image, 
-  setting up single-node and multi-node training environments, and highlights 
-  performance benchmarks demonstrating improved throughput and convergence accuracy. 
-  This resource serves as a comprehensive starting point for deploying verl on AMD GPUs, 
-  facilitating efficient RLHF training workflows.
-
-Previous versions
-===============================================================================
-See :doc:`rocm-install-on-linux:install/3rd-party/previous-versions/verl-history` to find documentation for previous releases
-of the ``ROCm/verl`` Docker image.

docs/conf.py

@@ -81,7 +81,7 @@ latex_elements = {
 }
 
 html_baseurl = os.environ.get("READTHEDOCS_CANONICAL_URL", "rocm.docs.amd.com")
-html_context = {"docs_header_version": "7.2.1"}
+html_context = {"docs_header_version": "7.2.2"}
 if os.environ.get("READTHEDOCS", "") == "True":
     html_context["READTHEDOCS"] = True
 
@@ -93,27 +93,21 @@ project = "ROCm Documentation"
 project_path = os.path.abspath(".").replace("\\", "/")
 author = "Advanced Micro Devices, Inc."
 copyright = "Copyright (c) 2026 Advanced Micro Devices, Inc. All rights reserved."
-version = "7.2.1"
-release = "7.2.1"
+version = "7.2.2"
+release = "7.2.2"
 setting_all_article_info = True
 all_article_info_os = ["linux", "windows"]
 all_article_info_author = ""
 
 # pages with specific settings
 article_pages = [
-    {"file": "about/release-notes", "os": ["linux"], "date": "2026-03-25"},
+    {"file": "about/release-notes", "os": ["linux"], "date": "2026-04-14"},
     {"file": "release/changelog", "os": ["linux"],},
     {"file": "compatibility/compatibility-matrix", "os": ["linux"]},
     {"file": "compatibility/ml-compatibility/pytorch-compatibility", "os": ["linux"]},
     {"file": "compatibility/ml-compatibility/tensorflow-compatibility", "os": ["linux"]},
     {"file": "compatibility/ml-compatibility/jax-compatibility", "os": ["linux"]},
-    {"file": "compatibility/ml-compatibility/verl-compatibility", "os": ["linux"]},
-    {"file": "compatibility/ml-compatibility/stanford-megatron-lm-compatibility", "os": ["linux"]},
     {"file": "compatibility/ml-compatibility/dgl-compatibility", "os": ["linux"]},
-    {"file": "compatibility/ml-compatibility/megablocks-compatibility", "os": ["linux"]},
-    {"file": "compatibility/ml-compatibility/ray-compatibility", "os": ["linux"]},
-    {"file": "compatibility/ml-compatibility/llama-cpp-compatibility", "os": ["linux"]},
-    {"file": "compatibility/ml-compatibility/flashinfer-compatibility", "os": ["linux"]},
     {"file": "how-to/deep-learning-rocm", "os": ["linux"]},
 
     {"file": "how-to/rocm-for-ai/index", "os": ["linux"]},
@@ -152,6 +146,7 @@ article_pages = [
     {"file": "how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.4", "os": ["linux"]},
     {"file": "how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.5", "os": ["linux"]},
     {"file": "how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.6", "os": ["linux"]},
+    {"file": "how-to/rocm-for-ai/inference/xdit-diffusion-inference", "os": ["linux"]},
     {"file": "how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.7", "os": ["linux"]},
     {"file": "how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.8", "os": ["linux"]},
     {"file": "how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.9", "os": ["linux"]},
@@ -210,6 +205,7 @@ article_pages = [
     {"file": "how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-25.13", "os": ["linux"]},
     {"file": "how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-26.1", "os": ["linux"]},
     {"file": "how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-26.2", "os": ["linux"]},
+    {"file": "how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-26.3", "os": ["linux"]},
 
     {"file": "how-to/rocm-for-ai/inference/deploy-your-model", "os": ["linux"]},
 
@@ -250,7 +246,7 @@ external_projects_current_project = "rocm"
 # external_projects_remote_repository = ""
 
 html_baseurl = os.environ.get("READTHEDOCS_CANONICAL_URL", "https://rocm-stg.amd.com/")
-html_context = {"docs_header_version": "7.2.1"}
+html_context = {"docs_header_version": "7.2.2"}
 if os.environ.get("READTHEDOCS", "") == "True":
     html_context["READTHEDOCS"] = True
 

docs/data/how-to/rocm-for-ai/inference/previous-versions/xdit_26.3-inference-models.yaml

@@ -0,0 +1,354 @@
+docker:
+  pull_tag: rocm/pytorch-xdit:v26.3
+  docker_hub_url: https://hub.docker.com/layers/rocm/pytorch-xdit/v26.3/images/sha256-ac78a03d2911bf1b49c001d3be2e8bd745c1bc455cb49ae972825a7986880902
+  ROCm: 7.12.0
+  whats_new:
+    - "Qwen-Image support"
+    - "Qwen-Image-Edit support"
+    - "Aiter update to support Sage attention v2"
+    - "xDiT update to support MXFP4 GEMMs in Wan2.2, Wan2.1 and Flux.2"
+  components:
+    TheRock: 
+      version: e40a6da
+      url: https://github.com/ROCm/TheRock
+    rocm-libraries:
+      version: 9e9e900
+      url: https://github.com/ROCm/rocm-libraries
+    rocm-systems:
+      version: ca89a1a
+      url: https://github.com/ROCm/rocm-systems
+    torch:
+      version: 91be249
+      url: https://github.com/ROCm/pytorch
+    torchaudio:
+      version: e3c6ee2
+      url: https://github.com/pytorch/audio
+    torchvision:
+      version: b919bd0
+      url: https://github.com/pytorch/vision
+    triton:
+      version: a272dfa
+      url: https://github.com/ROCm/triton
+    accelerate:
+      version: 46ba481
+      url: https://github.com/huggingface/accelerate
+    aiter:
+      version: 82d733f
+      url: https://github.com/ROCm/aiter
+    diffusers:
+      version: a80b192
+      url: https://github.com/huggingface/diffusers
+    xfuser:
+      version: 2882027
+      url: https://github.com/xdit-project/xDiT
+    yunchang:
+      version: 631bdfd
+      url: https://github.com/feifeibear/long-context-attention
+  supported_models:
+    - group: Hunyuan Video
+      js_tag: hunyuan
+      models:
+        - model: Hunyuan Video
+          model_repo: tencent/HunyuanVideo
+          revision: refs/pr/18
+          url: https://huggingface.co/tencent/HunyuanVideo
+          github: https://github.com/Tencent-Hunyuan/HunyuanVideo
+          mad_tag: pyt_xdit_hunyuanvideo
+          js_tag: hunyuan_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--prompt "In the large cage, two puppies were wagging their tails at each other." \'
+            - '--batch_size 1 \'
+            - '--height 720 --width 1280 \'
+            - '--seed 1168860793 \'
+            - '--num_frames 129 \'
+            - '--num_inference_steps 50 \'
+            - '--warmup_calls 1 \'
+            - '--num_iterations 1 \'
+            - '--ulysses_degree 8 \'
+            - '--enable_tiling --enable_slicing \'
+            - '--guidance_scale 6.0 \'
+            - '--use_torch_compile \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+        - model: Hunyuan Video 1.5
+          model_repo: hunyuanvideo-community/HunyuanVideo-1.5-Diffusers-720p_t2v
+          url: https://huggingface.co/hunyuanvideo-community/HunyuanVideo-1.5-Diffusers-720p_t2v
+          github: https://github.com/Tencent-Hunyuan/HunyuanVideo-1.5
+          mad_tag: pyt_xdit_hunyuanvideo_1_5
+          js_tag: hunyuan_1_5_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--prompt "In the large cage, two puppies were wagging their tails at each other." \'
+            - '--task t2v \'
+            - '--height 720 --width 1280 \'
+            - '--seed 1168860793 \'
+            - '--num_frames 129 \'
+            - '--num_inference_steps 50 \'
+            - '--num_iterations 1 \'
+            - '--ulysses_degree 8 \'
+            - '--enable_tiling --enable_slicing \'
+            - '--use_torch_compile \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+    - group: Wan-AI
+      js_tag: wan
+      models:
+        - model: Wan2.1
+          model_repo: Wan-AI/Wan2.1-I2V-14B-720P-Diffusers
+          url: https://huggingface.co/Wan-AI/Wan2.1-I2V-14B-720P-Diffusers
+          github: https://github.com/Wan-Video/Wan2.1
+          mad_tag: pyt_xdit_wan_2_1
+          js_tag: wan_21_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--prompt "Summer beach vacation style, a white cat wearing sunglasses sits on a surfboard. The fluffy-furred feline gazes directly at the camera with a relaxed expression. Blurred beach scenery forms the background featuring crystal-clear waters, distant green hills, and a blue sky dotted with white clouds. The cat assumes a naturally relaxed posture, as if savoring the sea breeze and warm sunlight. A close-up shot highlights the feline''s intricate details and the refreshing atmosphere of the seaside." \'
+            - '--height 720 \'
+            - '--width 1280 \'
+            - '--input_images /app/data/wan_input.jpg \'
+            - '--num_frames 81 \'
+            - '--ulysses_degree 8 \'
+            - '--seed 42 \'
+            - '--num_iterations 1 \'
+            - '--num_inference_steps 40 \'
+            - '--use_torch_compile \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+        - model: Wan2.2
+          model_repo: Wan-AI/Wan2.2-I2V-A14B-Diffusers
+          url: https://huggingface.co/Wan-AI/Wan2.2-I2V-A14B-Diffusers
+          github: https://github.com/Wan-Video/Wan2.2
+          mad_tag: pyt_xdit_wan_2_2
+          js_tag: wan_22_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--prompt "Summer beach vacation style, a white cat wearing sunglasses sits on a surfboard. The fluffy-furred feline gazes directly at the camera with a relaxed expression. Blurred beach scenery forms the background featuring crystal-clear waters, distant green hills, and a blue sky dotted with white clouds. The cat assumes a naturally relaxed posture, as if savoring the sea breeze and warm sunlight. A close-up shot highlights the feline''s intricate details and the refreshing atmosphere of the seaside." \'
+            - '--height 720 \'
+            - '--width 1280 \'
+            - '--input_images /app/data/wan_input.jpg \'
+            - '--num_frames 81 \'
+            - '--ulysses_degree 8 \'
+            - '--seed 42 \'
+            - '--num_iterations 1 \'
+            - '--num_inference_steps 40 \'
+            - '--use_torch_compile \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+    - group: FLUX
+      js_tag: flux
+      models:
+        - model: FLUX.1
+          model_repo: black-forest-labs/FLUX.1-dev
+          url: https://huggingface.co/black-forest-labs/FLUX.1-dev
+          github: https://github.com/black-forest-labs/flux
+          mad_tag: pyt_xdit_flux
+          js_tag: flux_1_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--seed 42 \'
+            - '--prompt "A small cat" \'
+            - '--height 1024 \'
+            - '--width 1024 \'
+            - '--num_inference_steps 25 \'
+            - '--max_sequence_length 256 \'
+            - '--warmup_calls 5 \'
+            - '--ulysses_degree 8 \'
+            - '--use_torch_compile \'
+            - '--guidance_scale 0.0 \'
+            - '--num_iterations 50 \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+        - model: FLUX.1 Kontext
+          model_repo: black-forest-labs/FLUX.1-Kontext-dev
+          url: https://huggingface.co/black-forest-labs/FLUX.1-Kontext-dev
+          github: https://github.com/black-forest-labs/flux
+          mad_tag: pyt_xdit_flux_kontext
+          js_tag: flux_1_kontext_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--seed 42 \'
+            - '--prompt "Add a cool hat to the cat" \'
+            - '--height 1024 \'
+            - '--width 1024 \'
+            - '--num_inference_steps 30 \'
+            - '--max_sequence_length 512 \'
+            - '--warmup_calls 5 \'
+            - '--ulysses_degree 8 \'
+            - '--use_torch_compile \'
+            - '--input_images /app/data/flux_cat.png \'
+            - '--guidance_scale 2.5 \'
+            - '--num_iterations 25 \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+        - model: FLUX.2
+          model_repo: black-forest-labs/FLUX.2-dev
+          url: https://huggingface.co/black-forest-labs/FLUX.2-dev
+          github: https://github.com/black-forest-labs/flux2
+          mad_tag: pyt_xdit_flux_2
+          js_tag: flux_2_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--seed 42 \'
+            - '--prompt "Add a cool hat to the cat" \'
+            - '--height 1024 \'
+            - '--width 1024 \'
+            - '--num_inference_steps 50 \'
+            - '--max_sequence_length 512 \'
+            - '--warmup_calls 5 \'
+            - '--ulysses_degree 8 \'
+            - '--use_torch_compile \'
+            - '--input_images /app/data/flux_cat.png \'
+            - '--guidance_scale 4.0 \'
+            - '--num_iterations 25 \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+        - model: FLUX.2 Klein
+          model_repo: black-forest-labs/FLUX.2-klein-9B
+          url: https://huggingface.co/black-forest-labs/FLUX.2-klein-9B
+          github: https://github.com/black-forest-labs/flux2
+          mad_tag: pyt_xdit_flux_2_klein
+          js_tag: flux_2_klein_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--seed 42 \'
+            - '--prompt "A spectacular sunset over the ocean" \'
+            - '--height 2048 \'
+            - '--width 2048 \'
+            - '--num_inference_steps 4 \'
+            - '--warmup_calls 5 \'
+            - '--ulysses_degree 8 \'
+            - '--use_torch_compile \'
+            - '--guidance_scale 1.0 \'
+            - '--num_iterations 25 \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+    - group: StableDiffusion
+      js_tag: stablediffusion
+      models:
+        - model: stable-diffusion-3.5-large
+          model_repo: stabilityai/stable-diffusion-3.5-large
+          url: https://huggingface.co/stabilityai/stable-diffusion-3.5-large
+          github: https://github.com/Stability-AI/sd3.5
+          mad_tag: pyt_xdit_sd_3_5
+          js_tag: stable_diffusion_3_5_large_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--prompt "A capybara holding a sign that reads Hello World" \'
+            - '--num_iterations 50 \'
+            - '--num_inference_steps 28 \'
+            - '--pipefusion_parallel_degree 4 \'
+            - '--use_cfg_parallel \'
+            - '--use_torch_compile \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+    - group: Z-Image
+      js_tag: z_image
+      models:
+        - model: Z-Image Turbo
+          model_repo: Tongyi-MAI/Z-Image-Turbo
+          url: https://huggingface.co/Tongyi-MAI/Z-Image-Turbo
+          github: https://github.com/Tongyi-MAI/Z-Image
+          mad_tag: pyt_xdit_z_image_turbo
+          js_tag: z_image_turbo_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--seed 42 \'
+            - '--prompt "A crowded beach" \'
+            - '--height 1088 \'
+            - '--width 1920 \'
+            - '--num_inference_steps 9 \'
+            - '--ulysses_degree 2 \'
+            - '--use_torch_compile \'
+            - '--guidance_scale 0.0 \'
+            - '--num_iterations 50 \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+    - group: LTX
+      js_tag: ltx
+      models:
+        - model: LTX-2
+          model_repo: Lightricks/LTX-2
+          url: https://huggingface.co/Lightricks/LTX-2
+          github: https://github.com/Lightricks/LTX-2
+          mad_tag: pyt_xdit_ltx2
+          js_tag: ltx2_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--seed 42 \'
+            - '--prompt "Cinematic action packed shot. The man says silently: \"We need to run.\". The camera zooms in on his mouth then immediately screams: \"NOW!\". The camera zooms back out, he turns around and bolts it." \'
+            - '--height 1088 \'
+            - '--width 1920 \'
+            - '--num_inference_steps 40 \'
+            - '--ulysses_degree 8 \'
+            - '--use_torch_compile \'
+            - '--guidance_scale 4.0 \'
+            - '--num_iterations 1 \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+    - group: Qwen-Image
+      js_tag: qwen_image
+      models:
+        - model: Qwen-Image
+          model_repo: Qwen/Qwen-Image
+          url: https://huggingface.co/Qwen/Qwen-Image
+          github: https://github.com/QwenLM/Qwen-Image
+          mad_tag: pyt_xdit_qwen_image
+          js_tag: qwen_image_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--seed 42 \'
+            - '--prompt "A cat holding a sign that says hello world" \'
+            - '--height 2048 \'
+            - '--width 2048 \'
+            - '--num_inference_steps 50 \'
+            - '--ulysses_degree 8 \'
+            - '--use_torch_compile \'
+            - '--num_iterations 1 \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'
+        - model: Qwen-Image-Edit
+          model_repo: Qwen/Qwen-Image-Edit
+          url: https://huggingface.co/Qwen/Qwen-Image-Edit
+          github: https://github.com/QwenLM/Qwen-Image
+          mad_tag: pyt_xdit_qwen_image_edit
+          js_tag: qwen_image_edit_tag
+          benchmark_command:
+            - mkdir results
+            - 'xdit \'
+            - '--model {model_repo} \'
+            - '--seed 42 \'
+            - '--prompt "Add a cool hat to the cat." \'
+            - '--negative_prompt "" \'
+            - '--input_images /app/data/flux_cat.png \'
+            - '--height 2048 \'
+            - '--width 2048 \'
+            - '--num_inference_steps 50 \'
+            - '--ulysses_degree 8 \'
+            - '--use_torch_compile \'
+            - '--num_iterations 1 \'
+            - '--attention_backend aiter \'
+            - '--output_directory results'

docs/data/how-to/rocm-for-ai/inference/xdit-inference-models.yaml

@@ -1,24 +1,24 @@
 docker:
-  pull_tag: rocm/pytorch-xdit:v26.3
-  docker_hub_url: https://hub.docker.com/layers/rocm/pytorch-xdit/v26.3/images/sha256-ac78a03d2911bf1b49c001d3be2e8bd745c1bc455cb49ae972825a7986880902
+  pull_tag: rocm/pytorch-xdit:v26.4
+  docker_hub_url: https://hub.docker.com/layers/rocm/pytorch-xdit/v26.4/images/sha256-b4296a638eb8dc7ebcafc808e180b78a3c44177580c21986082ec9539496067c
   ROCm: 7.12.0
   whats_new:
-    - "Qwen-Image support"
-    - "Qwen-Image-Edit support"
-    - "Aiter update to support Sage attention v2"
-    - "xDiT update to support MXFP4 GEMMs in Wan2.2, Wan2.1 and Flux.2"
+    - "Qwen-Image-2512 support"
+    - "Z-Image support"
+    - "Parallel VAE decode support for Wan models"
+    - "Batch inference and data parallel support"
   components:
     TheRock: 
-      version: e40a6da
+      version: 9b611c6
       url: https://github.com/ROCm/TheRock
     rocm-libraries:
-      version: 9e9e900
+      version: 7567d83
       url: https://github.com/ROCm/rocm-libraries
     rocm-systems:
-      version: ca89a1a
+      version: 93bc019
       url: https://github.com/ROCm/rocm-systems
     torch:
-      version: 91be249
+      version: ff65f5b
       url: https://github.com/ROCm/pytorch
     torchaudio:
       version: e3c6ee2
@@ -33,13 +33,16 @@ docker:
       version: 46ba481
       url: https://github.com/huggingface/accelerate
     aiter:
-      version: 82d733f
+      version: a169e14
       url: https://github.com/ROCm/aiter
     diffusers:
       version: a80b192
       url: https://github.com/huggingface/diffusers
+    distvae:
+      version: bf7531e
+      url: https://github.com/xdit-project/DistVAE
     xfuser:
-      version: 2882027
+      version: 45c44e7
       url: https://github.com/xdit-project/xDiT
     yunchang:
       version: 631bdfd
@@ -114,6 +117,7 @@ docker:
             - '--input_images /app/data/wan_input.jpg \'
             - '--num_frames 81 \'
             - '--ulysses_degree 8 \'
+            - '--use_parallel_vae \'
             - '--seed 42 \'
             - '--num_iterations 1 \'
             - '--num_inference_steps 40 \'
@@ -136,6 +140,7 @@ docker:
             - '--input_images /app/data/wan_input.jpg \'
             - '--num_frames 81 \'
             - '--ulysses_degree 8 \'
+            - '--use_parallel_vae \'
             - '--seed 42 \'
             - '--num_iterations 1 \'
             - '--num_inference_steps 40 \'
@@ -262,12 +267,12 @@ docker:
     - group: Z-Image
       js_tag: z_image
       models:
-        - model: Z-Image Turbo
-          model_repo: Tongyi-MAI/Z-Image-Turbo
-          url: https://huggingface.co/Tongyi-MAI/Z-Image-Turbo
+        - model: Z-Image
+          model_repo: Tongyi-MAI/Z-Image
+          url: https://huggingface.co/Tongyi-MAI/Z-Image
           github: https://github.com/Tongyi-MAI/Z-Image
-          mad_tag: pyt_xdit_z_image_turbo
-          js_tag: z_image_turbo_tag
+          mad_tag: pyt_xdit_z_image
+          js_tag: z_image_tag
           benchmark_command:
             - mkdir results
             - 'xdit \'
@@ -276,11 +281,13 @@ docker:
             - '--prompt "A crowded beach" \'
             - '--height 1088 \'
             - '--width 1920 \'
-            - '--num_inference_steps 9 \'
+            - '--num_inference_steps 50 \'
             - '--ulysses_degree 2 \'
+            - '--ring_degree 2 \'
+            - '--use_cfg_parallel \'
             - '--use_torch_compile \'
-            - '--guidance_scale 0.0 \'
-            - '--num_iterations 50 \'
+            - '--guidance_scale 4.0 \'
+            - '--num_iterations 25 \'
             - '--attention_backend aiter \'
             - '--output_directory results'
     - group: LTX
@@ -311,8 +318,8 @@ docker:
       js_tag: qwen_image
       models:
         - model: Qwen-Image
-          model_repo: Qwen/Qwen-Image
-          url: https://huggingface.co/Qwen/Qwen-Image
+          model_repo: Qwen/Qwen-Image-2512
+          url: https://huggingface.co/Qwen/Qwen-Image-2512
           github: https://github.com/QwenLM/Qwen-Image
           mad_tag: pyt_xdit_qwen_image
           js_tag: qwen_image_tag

docs/data/how-to/rocm-for-ai/training/megatron-lm-benchmark-models.yaml

@@ -1,14 +1,14 @@
 docker:
-  pull_tag: rocm/primus:v26.1
+  pull_tag: rocm/primus:v26.2
   docker_hub_url: https://hub.docker.com/layers/rocm/primus/v26.1/images/sha256-4fc8808bdb14117c6af7f38d79c809056e6fdbfd530c1fabbb61d097ddaf820d
   components:
-    ROCm: 7.1.0
-    PyTorch: 2.10.0.dev20251112+rocm7.1
-    Python: "3.10"
-    Transformer Engine: 2.6.0.dev0+f141f34b
+    ROCm: 7.2.0
+    PyTorch: 2.10.0+git94c6e04
+    Python: "3.12.3"
+    Transformer Engine: 2.8.0.dev0+51f74fa7
     Flash Attention: 2.8.3
     hipBLASLt: 34459f66ea
-    Triton: 3.4.0
+    Triton: 3.5.0
     RCCL: 2.27.7
 model_groups:
   - group: Meta Llama

docs/data/how-to/rocm-for-ai/training/previous-versions/primus-megatron-v26.1-benchmark-models.yaml

@@ -0,0 +1,58 @@
+docker:
+  pull_tag: rocm/primus:v26.1
+  docker_hub_url: https://hub.docker.com/layers/rocm/primus/v26.1/images/sha256-4fc8808bdb14117c6af7f38d79c809056e6fdbfd530c1fabbb61d097ddaf820d
+  components:
+    ROCm: 7.1.0
+    PyTorch: 2.10.0.dev20251112+rocm7.1
+    Python: "3.10"
+    Transformer Engine: 2.6.0.dev0+f141f34b
+    Flash Attention: 2.8.3
+    hipBLASLt: 34459f66ea
+    Triton: 3.4.0
+    RCCL: 2.27.7
+model_groups:
+  - group: Meta Llama
+    tag: llama
+    models:
+      - model: Llama 3.3 70B
+        mad_tag: primus_pyt_megatron_lm_train_llama-3.3-70b
+        config_name: llama3.3_70B-pretrain.yaml
+      - model: Llama 3.1 70B
+        mad_tag: primus_pyt_megatron_lm_train_llama-3.1-70b
+        config_name: llama3.1_70B-pretrain.yaml
+      - model: Llama 3.1 8B
+        mad_tag: primus_pyt_megatron_lm_train_llama-3.1-8b
+        config_name: llama3.1_8B-pretrain.yaml
+      - model: Llama 2 7B
+        mad_tag: primus_pyt_megatron_lm_train_llama-2-7b
+        config_name: llama2_7B-pretrain.yaml
+      - model: Llama 2 70B
+        mad_tag: primus_pyt_megatron_lm_train_llama-2-70b
+        config_name: llama2_70B-pretrain.yaml
+  - group: DeepSeek
+    tag: deepseek
+    models:
+      - model: DeepSeek-V3 (proxy)
+        mad_tag: primus_pyt_megatron_lm_train_deepseek-v3-proxy
+        config_name: deepseek_v3-pretrain.yaml
+      - model: DeepSeek-V2-Lite
+        mad_tag: primus_pyt_megatron_lm_train_deepseek-v2-lite-16b
+        config_name: deepseek_v2_lite-pretrain.yaml
+  - group: Mistral AI
+    tag: mistral
+    models:
+      - model: Mixtral 8x7B
+        mad_tag: primus_pyt_megatron_lm_train_mixtral-8x7b
+        config_name: mixtral_8x7B_v0.1-pretrain.yaml
+      - model: Mixtral 8x22B (proxy)
+        mad_tag: primus_pyt_megatron_lm_train_mixtral-8x22b-proxy
+        config_name: mixtral_8x22B_v0.1-pretrain.yaml
+  - group: Qwen
+    tag: qwen
+    models:
+      - model: Qwen 2.5 7B
+        mad_tag: primus_pyt_megatron_lm_train_qwen2.5-7b
+        config_name: primus_qwen2.5_7B-pretrain.yaml
+      - model: Qwen 2.5 72B
+        mad_tag: primus_pyt_megatron_lm_train_qwen2.5-72b
+        config_name: qwen2.5_72B-pretrain.yaml

docs/data/how-to/rocm-for-ai/training/previous-versions/primus-pytorch-v26.1-benchmark-models.yaml

@@ -0,0 +1,32 @@
+docker:
+  pull_tag: rocm/primus:v26.1
+  docker_hub_url: https://hub.docker.com/layers/rocm/primus/v26.1/images/sha256-4fc8808bdb14117c6af7f38d79c809056e6fdbfd530c1fabbb61d097ddaf820d
+  components:
+    ROCm: 7.1.0
+    PyTorch: 2.10.0.dev20251112+rocm7.1
+    Python: "3.10"
+    Transformer Engine: 2.6.0.dev0+f141f34b
+    Flash Attention: 2.8.3
+    hipBLASLt: 34459f66ea
+model_groups:
+  - group: Meta Llama
+    tag: llama
+    models:
+      - model: Llama 3.1 8B
+        mad_tag: primus_pyt_train_llama-3.1-8b
+        model_repo: Llama-3.1-8B
+        url: https://huggingface.co/meta-llama/Llama-3.1-8B
+        precision: BF16
+      - model: Llama 3.1 70B
+        mad_tag: primus_pyt_train_llama-3.1-70b
+        model_repo: Llama-3.1-70B
+        url: https://huggingface.co/meta-llama/Llama-3.1-70B
+        precision: BF16
+  - group: DeepSeek
+    tag: deepseek
+    models:
+      - model: DeepSeek V3 16B
+        mad_tag: primus_pyt_train_deepseek-v3-16b
+        model_repo: DeepSeek-V3
+        url: https://huggingface.co/deepseek-ai/DeepSeek-V3
+        precision: BF16

docs/data/how-to/rocm-for-ai/training/primus-megatron-benchmark-models.yaml

@@ -1,14 +1,14 @@
 docker:
-  pull_tag: rocm/primus:v26.1
-  docker_hub_url: https://hub.docker.com/layers/rocm/primus/v26.1/images/sha256-4fc8808bdb14117c6af7f38d79c809056e6fdbfd530c1fabbb61d097ddaf820d
+  pull_tag: rocm/primus:v26.2
+  docker_hub_url: https://hub.docker.com/layers/rocm/primus/v26.2/images/sha256-9148d1bfcd579bf92f44bd89090e0d8c958f149c134b4b34b9674ab559244585
   components:
-    ROCm: 7.1.0
-    PyTorch: 2.10.0.dev20251112+rocm7.1
-    Python: "3.10"
-    Transformer Engine: 2.6.0.dev0+f141f34b
+    ROCm: 7.2.0
+    PyTorch: 2.10.0a0+git449b176
+    Python: "3.12.3"
+    Transformer Engine: 2.8.0.dev0+51f74fa7
     Flash Attention: 2.8.3
-    hipBLASLt: 34459f66ea
-    Triton: 3.4.0
+    hipBLASLt: 1.2.0-de5c1aebb6
+    Triton: 3.6.0
     RCCL: 2.27.7
 model_groups:
   - group: Meta Llama
@@ -17,18 +17,30 @@ model_groups:
       - model: Llama 3.3 70B
         mad_tag: primus_pyt_megatron_lm_train_llama-3.3-70b
         config_name: llama3.3_70B-pretrain.yaml
-      - model: Llama 3.1 70B
-        mad_tag: primus_pyt_megatron_lm_train_llama-3.1-70b
-        config_name: llama3.1_70B-pretrain.yaml
       - model: Llama 3.1 8B
         mad_tag: primus_pyt_megatron_lm_train_llama-3.1-8b
         config_name: llama3.1_8B-pretrain.yaml
+      - model: Llama 3.1 70B
+        mad_tag: primus_pyt_megatron_lm_train_llama-3.1-70b
+        config_name: llama3.1_70B-pretrain.yaml
       - model: Llama 2 7B
         mad_tag: primus_pyt_megatron_lm_train_llama-2-7b
         config_name: llama2_7B-pretrain.yaml
       - model: Llama 2 70B
         mad_tag: primus_pyt_megatron_lm_train_llama-2-70b
         config_name: llama2_70B-pretrain.yaml
+  - group: AMD Zebra-Llama
+    tag: zebra-llama
+    models:
+      - model: Zebra-Llama 1B
+        mad_tag: primus_pyt_megatron_lm_train_zebra-llama-1b
+        config_name: zebra_llama_1b-pretrain.yaml
+      - model: Zebra-Llama 3B
+        mad_tag: primus_pyt_megatron_lm_train_zebra-llama-3b
+        config_name: zebra_llama_3b-pretrain.yaml
+      - model: Zebra-Llama 8B
+        mad_tag: primus_pyt_megatron_lm_train_zebra-llama-8b
+        config_name: zebra_llama_8b-pretrain.yaml
   - group: DeepSeek
     tag: deepseek
     models:
@@ -50,6 +62,11 @@ model_groups:
   - group: Qwen
     tag: qwen
     models:
+      - model: Qwen 3 32B SFT
+        mad_tag: primus_pyt_megatron_lm_train_qwen3-32b-sft
+      - model: Qwen 3 32B LoRA
+        mad_tag: primus_pyt_megatron_lm_train_qwen3-32b-lora
+        config_name: primus_qwen2.5_7B-pretrain.yaml
       - model: Qwen 2.5 7B
         mad_tag: primus_pyt_megatron_lm_train_qwen2.5-7b
         config_name: primus_qwen2.5_7B-pretrain.yaml

docs/data/how-to/rocm-for-ai/training/primus-pytorch-benchmark-models.yaml

@@ -1,13 +1,15 @@
 docker:
-  pull_tag: rocm/primus:v26.1
-  docker_hub_url: https://hub.docker.com/layers/rocm/primus/v26.1/images/sha256-4fc8808bdb14117c6af7f38d79c809056e6fdbfd530c1fabbb61d097ddaf820d
+  pull_tag: rocm/primus:v26.2
+  docker_hub_url: https://hub.docker.com/layers/rocm/primus/v26.2/images/sha256-9148d1bfcd579bf92f44bd89090e0d8c958f149c134b4b34b9674ab559244585
   components:
-    ROCm: 7.1.0
-    PyTorch: 2.10.0.dev20251112+rocm7.1
-    Python: "3.10"
-    Transformer Engine: 2.6.0.dev0+f141f34b
+    ROCm: 7.2.0
+    PyTorch: 2.10.0a0+git449b176
+    Python: "3.12.3"
+    Transformer Engine: 2.8.0.dev0+51f74fa7
     Flash Attention: 2.8.3
-    hipBLASLt: 34459f66ea
+    hipBLASLt: 1.2.0-de5c1aebb6
+    Triton: 3.6.0
+    RCCL: 2.27.7
 model_groups:
   - group: Meta Llama
     tag: llama

docs/data/how-to/rocm-for-ai/training/pytorch-training-benchmark-models.yaml

@@ -1,11 +1,11 @@
 docker:
-  pull_tag: rocm/primus:v26.1
+  pull_tag: rocm/primus:v26.2
   docker_hub_url: https://hub.docker.com/layers/rocm/primus/v26.1/images/sha256-4fc8808bdb14117c6af7f38d79c809056e6fdbfd530c1fabbb61d097ddaf820d
   components:
-    ROCm: 7.1.0
-    PyTorch: 2.10.0.dev20251112+rocm7.1
-    Python: "3.10"
-    Transformer Engine: 2.6.0.dev0+f141f34b
+    ROCm: 7.2.0
+    PyTorch: 2.10.0+git94c6e04
+    Python: "3.12.3"
+    Transformer Engine: 2.8.0.dev0+51f74fa7
     Flash Attention: 2.8.3
     hipBLASLt: 34459f66ea
 model_groups:

docs/how-to/deep-learning-rocm.rst

@@ -52,22 +52,6 @@ The table below summarizes information about ROCm-enabled deep learning framewor
 
           <a href="https://github.com/ROCm/jax"><i class="fab fa-github fa-lg"></i></a>
 
-    * - :doc:`verl <../compatibility/ml-compatibility/verl-compatibility>`
-      - :doc:`link <rocm-install-on-linux:install/3rd-party/verl-install>`
-      - 
-        - Docker image
-      - .. raw:: html
-
-          <a href="https://github.com/ROCm/verl"><i class="fab fa-github fa-lg"></i></a>
-
-    * - :doc:`Stanford Megatron-LM <../compatibility/ml-compatibility/stanford-megatron-lm-compatibility>`
-      - :doc:`link <rocm-install-on-linux:install/3rd-party/stanford-megatron-lm-install>`
-      - 
-        - Docker image
-      - .. raw:: html
-
-          <a href="https://github.com/ROCm/Stanford-Megatron-LM"><i class="fab fa-github fa-lg"></i></a>
-
     * - :doc:`DGL <../compatibility/ml-compatibility/dgl-compatibility>`
       - :doc:`link <rocm-install-on-linux:install/3rd-party/dgl-install>`
       - 
@@ -76,42 +60,6 @@ The table below summarizes information about ROCm-enabled deep learning framewor
 
           <a href="https://github.com/ROCm/dgl"><i class="fab fa-github fa-lg"></i></a> 
 
-    * - :doc:`Megablocks <../compatibility/ml-compatibility/megablocks-compatibility>`
-      - :doc:`link <rocm-install-on-linux:install/3rd-party/megablocks-install>`
-      - 
-        - Docker image
-      - .. raw:: html
-
-          <a href="https://github.com/ROCm/megablocks"><i class="fab fa-github fa-lg"></i></a>
-
-    * - :doc:`Ray <../compatibility/ml-compatibility/ray-compatibility>`
-      - :doc:`link <rocm-install-on-linux:install/3rd-party/ray-install>`
-      - 
-        - Docker image
-        - Wheels package
-        - ROCm Base Docker image
-      - .. raw:: html
-
-          <a href="https://github.com/ROCm/ray"><i class="fab fa-github fa-lg"></i></a>
-
-    * - :doc:`llama.cpp <../compatibility/ml-compatibility/llama-cpp-compatibility>`
-      - :doc:`link <rocm-install-on-linux:install/3rd-party/llama-cpp-install>`
-      - 
-        - Docker image
-        - ROCm Base Docker image
-      - .. raw:: html
-
-          <a href="https://github.com/ROCm/llama.cpp"><i class="fab fa-github fa-lg"></i></a>
-
-    * - :doc:`FlashInfer <../compatibility/ml-compatibility/flashinfer-compatibility>`
-      - :doc:`link <rocm-install-on-linux:install/3rd-party/flashinfer-install>`
-      - 
-        - Docker image
-        - ROCm Base Docker image
-      - .. raw:: html
-
-          <a href="https://github.com/ROCm/flashinfer"><i class="fab fa-github fa-lg"></i></a>
-
 Learn how to use your ROCm deep learning environment for training, fine-tuning, inference, and performance optimization
 through the following guides.
 

docs/how-to/rocm-for-ai/fine-tuning/single-gpu-fine-tuning-and-inference.rst

@@ -127,7 +127,7 @@ Download the base model and fine-tuning dataset
 
    .. code-block:: shell
 
-      huggingface-cli login
+      hf auth login
 
    .. note::
 

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.10.0-20250812.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.10.1-20250909.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X accelerators using AMD MAD and the ROCm vLLM Docker image.

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.10.2-20251006.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the ROCm vLLM Docker image.
@@ -479,4 +480,4 @@ Previous versions
 =================
 
 See :doc:`vllm-history` to find documentation for previous releases
-of the ``ROCm/vllm`` Docker image.
+of the ``ROCm/vllm`` Docker image.

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.11.1-20251103.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the ROCm vLLM Docker image.

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.4.3.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the unified

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.6.4.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the unified

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.6.6.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.7.3-20250325.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.8.3-20250415.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.8.5-20250513.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.8.5-20250521.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.9.0.1-20250605.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.9.1-20250702.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/vllm-0.9.1-20250715.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn how to validate LLM inference performance on MI300X GPUs using AMD MAD and the

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-25.10.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn to validate diffusion model video generation on MI300X, MI350X and MI355X accelerators using

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-25.11.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn to validate diffusion model video generation on MI300X, MI350X and MI355X accelerators using

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-25.12.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn to validate diffusion model video generation on MI300X, MI350X and MI355X accelerators using

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-25.13.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn to validate diffusion model video generation on MI300X, MI350X and MI355X accelerators using

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-26.1.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn to validate diffusion model video generation on MI300X, MI350X and MI355X accelerators using

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-26.2.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: Learn to validate diffusion model video generation on MI300X, MI350X and MI355X accelerators using

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-26.3.rst

@@ -0,0 +1,321 @@
+:orphan:
+:no-search:
+
+.. meta::
+   :description: Learn to validate diffusion model video generation on MI300X, MI350X and MI355X accelerators using
+                 prebuilt and optimized docker images.
+   :keywords: xDiT, diffusion, video, video generation, image, image generation, validate, benchmark
+
+************************
+xDiT diffusion inference
+************************
+
+.. caution::
+
+   This documentation does not reflect the latest version of the xDiT diffusion
+   inference performance documentation. See
+   :doc:`/how-to/rocm-for-ai/inference/xdit-diffusion-inference` for the latest
+   version.
+
+.. _xdit-video-diffusion-263:
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/inference/previous-versions/xdit_26.3-inference-models.yaml
+
+   {% set docker = data.docker %}
+
+   The `rocm/pytorch-xdit <{{ docker.docker_hub_url }}>`_ Docker image offers a prebuilt, optimized environment based on `xDiT <https://github.com/xdit-project/xDiT>`_ for
+   benchmarking diffusion model video and image generation on gfx942 and gfx950 series (AMD Instinct™ MI300X, MI325X, MI350X, and MI355X) GPUs.
+   The image runs ROCm **{{docker.ROCm}}** (preview) based on `TheRock <https://github.com/ROCm/TheRock>`_
+   and includes the following components:
+
+   .. dropdown:: Software components - {{ docker.pull_tag.split('-')|last }}
+
+      .. list-table::
+         :header-rows: 1
+
+         * - Software component
+           - Version
+
+         {% for component_name, component_data in docker.components.items() %}
+         * - `{{ component_name }} <{{ component_data.url }}>`_
+           - {{ component_data.version }}
+         {% endfor %}
+
+Follow this guide to pull the required image, spin up a container, download the model, and run a benchmark.
+For preview and development releases, see `amdsiloai/pytorch-xdit <https://hub.docker.com/r/amdsiloai/pytorch-xdit>`_.
+
+What's new
+==========
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/inference/previous-versions/xdit_26.3-inference-models.yaml
+
+   {% set docker = data.docker %}
+
+   {% for item in docker.whats_new %}
+   * {{ item }}
+   {% endfor %}
+
+.. _xdit-video-diffusion-supported-models-263:
+
+Supported models
+================
+
+The following models are supported for inference performance benchmarking.
+Some instructions, commands, and recommendations in this documentation might
+vary by model -- select one to get started.
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/inference/previous-versions/xdit_26.3-inference-models.yaml
+
+   {% set docker = data.docker %}
+
+   .. raw:: html
+
+      <div id="vllm-benchmark-ud-params-picker" class="container-fluid">
+          <div class="row gx-0">
+              <div class="col-2 me-1 px-2 model-param-head">Model</div>
+              <div class="row col-10 pe-0">
+        {% for model_group in docker.supported_models %}
+               <div class="col-6 px-2 model-param" data-param-k="model-group" data-param-v="{{ model_group.js_tag }}" tabindex="0">{{ model_group.group }}</div>
+        {% endfor %}
+              </div>
+          </div>
+
+          <div class="row gx-0 pt-1">
+              <div class="col-2 me-1 px-2 model-param-head">Variant</div>
+              <div class="row col-10 pe-0">
+        {% for model_group in docker.supported_models %}
+            {% set models = model_group.models %}
+            {% for model in models %}
+                {% if models|length % 3 == 0 %}
+                <div class="col-4 px-2 model-param" data-param-k="model" data-param-v="{{ model.js_tag }}" data-param-group="{{ model_group.js_tag }}" tabindex="0">{{ model.model }}</div>
+                {% else %}
+                <div class="col-6 px-2 model-param" data-param-k="model" data-param-v="{{ model.js_tag }}" data-param-group="{{ model_group.js_tag }}" tabindex="0">{{ model.model }}</div>
+                {% endif %}
+            {% endfor %}
+        {% endfor %}
+              </div>
+          </div>
+      </div>
+
+   {% for model_group in docker.supported_models %}
+       {% for model in model_group.models %}
+
+   .. container:: model-doc {{ model.js_tag }}
+
+      .. note::
+
+         To learn more about your specific model see the `{{ model.model }} model card on Hugging Face <{{ model.url }}>`_
+         or visit the `GitHub page <{{ model.github }}>`__. Note that some models require access authorization before use via an
+         external license agreement through a third party.
+
+       {% endfor %}
+   {% endfor %}
+
+System validation
+=================
+
+Before running AI workloads, it's important to validate that your AMD hardware is configured
+correctly and performing optimally.
+
+If you have already validated your system settings, including aspects like NUMA auto-balancing, you
+can skip this step. Otherwise, complete the procedures in the :ref:`System validation and
+optimization <rocm-for-ai-system-optimization>` guide to properly configure your system settings
+before starting.
+
+To test for optimal performance, consult the recommended :ref:`System health benchmarks
+<rocm-for-ai-system-health-bench>`. This suite of tests will help you verify and fine-tune your
+system's configuration.
+
+Pull the Docker image
+=====================
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/inference/previous-versions/xdit_26.3-inference-models.yaml
+
+   {% set docker = data.docker %}
+
+   For this tutorial, it's recommended to use the latest ``{{ docker.pull_tag }}`` Docker image.
+   Pull the image using the following command:
+
+   .. code-block:: shell
+
+      docker pull {{ docker.pull_tag }}
+
+Validate and benchmark
+======================
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/inference/previous-versions/xdit_26.3-inference-models.yaml
+
+   {% set docker = data.docker %}
+
+   Once the image has been downloaded you can follow these steps to
+   run benchmarks and generate outputs.
+
+   {% for model_group in docker.supported_models %}
+     {% for model in model_group.models %}
+
+   .. container:: model-doc {{model.js_tag}}
+
+      The following commands are written for {{ model.model }}.
+      See :ref:`xdit-video-diffusion-supported-models-263` to switch to another available model.
+
+     {% endfor %}
+   {% endfor %}
+
+Choose your setup method
+------------------------
+
+You can either use an existing Hugging Face cache or download the model fresh inside the container.
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/inference/previous-versions/xdit_26.3-inference-models.yaml
+
+   {% set docker = data.docker %}
+
+   {% for model_group in docker.supported_models %}
+     {% for model in model_group.models %}
+   .. container:: model-doc {{model.js_tag}}
+
+      .. tab-set::
+
+         .. tab-item:: Option 1: Use existing Hugging Face cache
+
+            If you already have models downloaded on your host system, you can mount your existing cache.
+
+            1. Set your Hugging Face cache location.
+
+               .. code-block:: shell
+
+                  export HF_HOME=/your/hf_cache/location
+
+            2. Download the model (if not already cached).
+
+               .. code-block:: shell
+
+                  huggingface-cli download {{ model.model_repo }} {% if model.revision %} --revision {{ model.revision }} {% endif %}
+
+            3. Launch the container with mounted cache.
+
+               .. code-block:: shell
+
+                  docker run \
+                      -it --rm \
+                      --cap-add=SYS_PTRACE \
+                      --security-opt seccomp=unconfined \
+                      --user root \
+                      --device=/dev/kfd \
+                      --device=/dev/dri \
+                      --group-add video \
+                      --ipc=host \
+                      --network host \
+                      --privileged \
+                      --shm-size 128G \
+                      --name pytorch-xdit \
+                      -e HSA_NO_SCRATCH_RECLAIM=1 \
+                      -e OMP_NUM_THREADS=16 \
+                      -e CUDA_VISIBLE_DEVICES=0,1,2,3,4,5,6,7 \
+                      -e HF_HOME=/app/huggingface_models \
+                      -v $HF_HOME:/app/huggingface_models \
+                      {{ docker.pull_tag }}
+
+         .. tab-item:: Option 2: Download inside container
+
+            If you prefer to keep the container self-contained or don't have an existing cache.
+
+            1. Launch the container
+
+               .. code-block:: shell
+
+                  docker run \
+                      -it --rm \
+                      --cap-add=SYS_PTRACE \
+                      --security-opt seccomp=unconfined \
+                      --user root \
+                      --device=/dev/kfd \
+                      --device=/dev/dri \
+                      --group-add video \
+                      --ipc=host \
+                      --network host \
+                      --privileged \
+                      --shm-size 128G \
+                      --name pytorch-xdit \
+                      -e HSA_NO_SCRATCH_RECLAIM=1 \
+                      -e OMP_NUM_THREADS=16 \
+                      -e CUDA_VISIBLE_DEVICES=0,1,2,3,4,5,6,7 \
+                      {{ docker.pull_tag }}
+
+            2. Inside the container, set the Hugging Face cache location and download the model.
+
+               .. code-block:: shell
+
+                  export HF_HOME=/app/huggingface_models
+                  huggingface-cli download {{ model.model_repo }} {% if model.revision %} --revision {{ model.revision }} {% endif %}
+
+               .. warning::
+
+                  Models will be downloaded to the container's filesystem and will be lost when the container is removed unless you persist the data with a volume.
+     {% endfor %}
+   {% endfor %}
+
+Run inference
+=============
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/inference/previous-versions/xdit_26.3-inference-models.yaml
+
+   {% set docker = data.docker %}
+
+   {% for model_group in docker.supported_models %}
+     {% for model in model_group.models %}
+
+   .. container:: model-doc {{ model.js_tag }}
+
+      .. tab-set::
+
+         .. tab-item:: MAD-integrated benchmarking
+
+            1. Clone the ROCm Model Automation and Dashboarding (`<https://github.com/ROCm/MAD>`__) repository to a local
+               directory and install the required packages on the host machine.
+
+               .. code-block:: shell
+
+                  git clone https://github.com/ROCm/MAD
+                  cd MAD
+                  pip install -r requirements.txt
+
+            2. On the host machine, use this command to run the performance benchmark test on
+               the `{{model.model}} <{{ model.url }}>`_ model using one node.
+
+               .. code-block:: shell
+
+                  export MAD_SECRETS_HFTOKEN="your personal Hugging Face token to access gated models"
+                  madengine run \
+                      --tags {{model.mad_tag}} \
+                      --keep-model-dir \
+                      --live-output
+
+            MAD launches a Docker container with the name
+            ``container_ci-{{model.mad_tag}}``. The throughput and serving reports of the
+            model are collected in the following paths: ``{{ model.mad_tag }}_throughput.csv``
+            and ``{{ model.mad_tag }}_serving.csv``.
+
+         .. tab-item:: Standalone benchmarking
+
+            To run the benchmarks for {{ model.model }}, use the following command:
+
+            .. code-block:: shell
+
+               {{ model.benchmark_command
+                  | map('replace', '{model_repo}', model.model_repo)
+                  | map('trim')
+                  | join('\n               ') }}
+
+            The generated content and timing information will be stored under the results directory.
+
+      {% endfor %}
+    {% endfor %}
+
+Previous versions
+=================
+
+See
+:doc:`/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-history`
+to find documentation for previous releases of xDiT diffusion inference
+performance testing.

docs/how-to/rocm-for-ai/inference/benchmark-docker/previous-versions/xdit-history.rst

@@ -15,11 +15,20 @@ benchmarking, see the version-specific documentation.
      - Components
      - Resources
 
-   * - ``rocm/pytorch-xdit:v26.3`` (latest)
+   * - ``rocm/pytorch-xdit:v26.4`` (latest)
      -
-       * TheRock e40a6da
+       * `ROCm 7.12.0 preview <https://rocm.docs.amd.com/en/7.12.0-preview/about/release-notes.html>`__
+       * TheRock 9b611c6
      -
        * :doc:`Documentation </how-to/rocm-for-ai/inference/xdit-diffusion-inference>`
+       * `Docker Hub <https://hub.docker.com/layers/rocm/pytorch-xdit/v26.4/images/sha256-b4296a638eb8dc7ebcafc808e180b78a3c44177580c21986082ec9539496067c>`__
+
+   * - ``rocm/pytorch-xdit:v26.3``
+     -
+       * `ROCm 7.12.0 preview <https://rocm.docs.amd.com/en/7.12.0-preview/about/release-notes.html>`__
+       * TheRock e40a6da
+     -
+       * :doc:`Documentation <xdit-26.3>`
        * `Docker Hub <https://hub.docker.com/layers/rocm/pytorch-xdit/v26.3/images/sha256-ac78a03d2911bf1b49c001d3be2e8bd745c1bc455cb49ae972825a7986880902>`__
 
    * - ``rocm/pytorch-xdit:v26.2``

docs/how-to/rocm-for-ai/inference/benchmark-docker/sglang-mori-distributed.md

@@ -692,7 +692,7 @@ This performance test supports the following models:
 * [DeepSeek-R1-0528](https://huggingface.co/deepseek-ai/DeepSeek-R1-0528)
 
 To set up your environment and download the models using the Hugging Face CLI,
-use the following commands. Modify the `huggingface-cli download` command
+use the following commands. Modify the `hf download` command
 to download the desired model.
 
 ```bash
@@ -704,7 +704,7 @@ pip install huggingface_hub
 
 # Download the model to the shared NFS mount point
 # Replace 'deepseek-ai/DeepSeek-R1-0528' with your desired model
-huggingface-cli download --token <your_hf_token> \
+hf download --token <your_hf_token> \
     deepseek-ai/DeepSeek-R1-0528 \
     --local-dir /mount/point/models/DeepSeek-R1
 ```

docs/how-to/rocm-for-ai/inference/benchmark-docker/vllm-mori-distributed.md

@@ -387,7 +387,7 @@ source ~/venvs/hf/bin/activate
 pip install huggingface_hub
 
 # Download the model to the shared NFS mount point
-huggingface-cli download --token <your_hf_token> \
+hf download --token <your_hf_token> \
     EmbeddedLLM/deepseek-r1-FP8-Dynamic \
     --local-dir /mount/point/models/EmbeddedLLM/deepseek-r1-FP8-Dynamic
 ```

docs/how-to/rocm-for-ai/inference/index.rst

@@ -35,3 +35,5 @@ training, fine-tuning, and inference. It leverages popular machine learning fram
 - :doc:`xDiT diffusion inference <xdit-diffusion-inference>`
 
 - :doc:`Deploying your model <deploy-your-model>`
+
+- :doc:`xDiT diffusion inference <xdit-diffusion-inference>`

docs/how-to/rocm-for-ai/inference/xdit-diffusion-inference.rst

@@ -15,7 +15,7 @@ xDiT diffusion inference
 
    The `rocm/pytorch-xdit <{{ docker.docker_hub_url }}>`_ Docker image offers a prebuilt, optimized environment based on `xDiT <https://github.com/xdit-project/xDiT>`_ for
    benchmarking diffusion model video and image generation on gfx942 and gfx950 series (AMD Instinct™ MI300X, MI325X, MI350X, and MI355X) GPUs.
-   The image runs ROCm **{{docker.ROCm}}** (preview) based on `TheRock <https://github.com/ROCm/TheRock>`_
+   The image runs `ROCm {{docker.ROCm}} (preview) <https://rocm.docs.amd.com/en/7.12.0-preview/about/release-notes.html>`__ based on `TheRock <https://github.com/ROCm/TheRock>`_
    and includes the following components:
 
    .. dropdown:: Software components - {{ docker.pull_tag.split('-')|last }}
@@ -36,6 +36,7 @@ For preview and development releases, see `amdsiloai/pytorch-xdit <https://hub.d
 
 What's new
 ==========
+
 .. datatemplate:yaml:: /data/how-to/rocm-for-ai/inference/xdit-inference-models.yaml
 
    {% set docker = data.docker %}
@@ -179,7 +180,7 @@ You can either use an existing Hugging Face cache or download the model fresh in
 
                .. code-block:: shell
 
-                  huggingface-cli download {{ model.model_repo }} {% if model.revision %} --revision {{ model.revision }} {% endif %}
+                  hf download {{ model.model_repo }} {% if model.revision %} --revision {{ model.revision }} {% endif %}
 
             3. Launch the container with mounted cache.
 
@@ -236,7 +237,7 @@ You can either use an existing Hugging Face cache or download the model fresh in
                .. code-block:: shell
 
                   export HF_HOME=/app/huggingface_models
-                  huggingface-cli download {{ model.model_repo }} {% if model.revision %} --revision {{ model.revision }} {% endif %}
+                  hf download {{ model.model_repo }} {% if model.revision %} --revision {{ model.revision }} {% endif %}
 
                .. warning::
 

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/jax-maxtext-v25.11.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using JAX MaxText for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/jax-maxtext-v25.4.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using JAX MaxText for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/jax-maxtext-v25.5.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using JAX MaxText for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/jax-maxtext-v25.7.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using JAX MaxText for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/jax-maxtext-v25.9.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using JAX MaxText for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/jax-maxtext-v26.1.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using JAX MaxText for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-history.rst

@@ -7,7 +7,7 @@ Megatron-LM training performance testing version history
 This table lists previous versions of the ROCm Megatron-LM training Docker image for
 inference performance testing. For detailed information about available models
 for benchmarking, see the version-specific documentation. You can find tagged
-previous releases of the ``ROCm/megatron-lm`` Docker image on `Docker Hub <https://hub.docker.com/r/rocm/megatron-lm/tags>`__.
+previous releases of the ``ROCm/primus`` Docker image on `Docker Hub <https://hub.docker.com/r/rocm/megatron-lm/tags>`__.
 
 .. list-table::
    :header-rows: 1
@@ -16,13 +16,20 @@ previous releases of the ``ROCm/megatron-lm`` Docker image on `Docker Hub <https
      - Components
      - Resources
 
-   * - v26.1 (latest)
+   * - v26.2 (latest)
+     -
+       * ROCm 7.2.0
+       * PyTorch 2.10.0+git94c6e04
+     -
+       * :doc:`Primus Megatron documentation <../primus-megatron>`
+       * `Docker Hub <https://hub.docker.com/layers/rocm/primus/v26.2/images/sha256-9148d1bfcd579bf92f44bd89090e0d8c958f149c134b4b34b9674ab559244585>`__
+
+   * - v26.1
      -
        * ROCm 7.1.0
        * PyTorch 2.10.0.dev20251112+rocm7.1
      -
-       * :doc:`Primus Megatron documentation <../primus-megatron>`
-       * :doc:`Megatron-LM (legacy) documentation <../megatron-lm>`
+       * :doc:`Primus Megatron documentation <primus-megatron-v26.1>`
        * `Docker Hub <https://hub.docker.com/layers/rocm/primus/v26.1/images/sha256-4fc8808bdb14117c6af7f38d79c809056e6fdbfd530c1fabbb61d097ddaf820d>`__
 
    * - v25.11
@@ -31,7 +38,7 @@ previous releases of the ``ROCm/megatron-lm`` Docker image on `Docker Hub <https
        * PyTorch 2.10.0.dev20251112+rocm7.1
      -
        * :doc:`Primus Megatron documentation <primus-megatron-v25.11>`
-       * :doc:`Megatron-LM (legacy) documentation <megatron-lm-v25.10>`
+       * :doc:`Megatron-LM (legacy) documentation <megatron-lm-v25.11>`
        * `Docker Hub <https://hub.docker.com/layers/rocm/primus/v25.11/images/sha256-71aa65a9bfc8e9dd18bce5b68c81caff864f223e9afa75dc1b719671a1f4a3c3>`__
 
    * - v25.10

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-primus-migration-guide.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 *****************************************************************
 Migrating workloads to Primus (Megatron backend) from Megatron-LM

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v24.12-dev.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using ROCm Megatron-LM

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v25.10.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v25.11.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v25.3.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v25.4.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v25.5.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v25.6.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v25.7.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v25.8.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/megatron-lm-v25.9.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-megatron-v25.10.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-megatron-v25.11.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-megatron-v25.7.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-megatron-v25.8.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-megatron-v25.9.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using Megatron-LM for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-pytorch-v25.10.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-pytorch-v25.11.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-pytorch-v25.8.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-pytorch-v25.9.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/primus-pytorch-v26.1.rst

@@ -0,0 +1,458 @@
+:orphan:
+:no-search:
+
+.. meta::
+   :description: How to train a model using PyTorch for ROCm.
+   :keywords: ROCm, AI, LLM, train, PyTorch, torch, Llama, flux, tutorial, docker
+
+****************************************
+Training a model with Primus and PyTorch
+****************************************
+
+.. caution::
+
+   This documentation does not reflect the latest version of ROCm Primus PyTorch training
+   performance benchmark documentation. See :doc:`../primus-pytorch` for the latest version.
+
+`Primus <https://github.com/AMD-AGI/Primus>`__ is a unified and flexible
+LLM training framework designed to streamline training. It streamlines LLM
+training on AMD Instinct GPUs using a modular, reproducible configuration paradigm.
+Primus now supports the PyTorch torchtitan backend.
+
+.. note::
+
+   For a unified training solution on AMD GPUs with ROCm, the `rocm/pytorch-training
+   <https://hub.docker.com/r/rocm/pytorch-training/>`__ Docker Hub registry will be
+   deprecated soon in favor of `rocm/primus <https://hub.docker.com/r/rocm/primus>`__.
+   The ``rocm/primus`` Docker containers will cover PyTorch training ecosystem frameworks,
+   including torchtitan and :doc:`Megatron-LM <primus-megatron>`.
+
+   Primus with the PyTorch torchtitan backend is designed to replace the
+   :doc:`ROCm PyTorch training <pytorch-training>` workflow. See
+   :doc:`pytorch-training` to see steps to run workloads without Primus.
+
+AMD provides a ready-to-use Docker image for MI355X, MI350X, MI325X, and
+MI300X GPUs containing essential components for Primus and PyTorch training
+with Primus Turbo optimizations.
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/training/previous-versions/primus-pytorch-v26.1-benchmark-models.yaml
+
+   .. tab-set::
+
+      .. tab-item:: {{ data.docker.pull_tag }}
+         :sync: {{ data.docker.pull_tag }}
+
+         .. list-table::
+            :header-rows: 1
+
+            * - Software component
+              - Version
+
+            {% for component_name, component_version in data.docker.components.items() %}
+            * - {{ component_name }}
+              - {{ component_version }}
+            {% endfor %}
+
+.. _amd-primus-pytorch-model-support-v26.01:
+
+Supported models
+================
+
+The following models are pre-optimized for performance on the AMD Instinct MI325X and MI300X GPUs.
+Some instructions, commands, and training recommendations in this documentation might
+vary by model -- select one to get started.
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/training/previous-versions/primus-pytorch-v26.1-benchmark-models.yaml
+
+   {% set model_groups = data.model_groups %}
+   .. raw:: html
+
+      <div id="vllm-benchmark-ud-params-picker" class="container-fluid">
+         <div class="row gx-0">
+            <div class="col-2 me-1 px-2 model-param-head">Model</div>
+            <div class="row col-10 pe-0">
+      {% for model_group in model_groups %}
+               <div class="col-6 px-2 model-param" data-param-k="model-group" data-param-v="{{ model_group.tag }}" tabindex="0">{{ model_group.group }}</div>
+      {% endfor %}
+            </div>
+         </div>
+
+         <div class="row gx-0 pt-1">
+            <div class="col-2 me-1 px-2 model-param-head">Variant</div>
+            <div class="row col-10 pe-0">
+      {% for model_group in model_groups %}
+         {% set models = model_group.models %}
+         {% for model in models %}
+            {% if models|length % 3 == 0 %}
+               <div class="col-4 px-2 model-param" data-param-k="model" data-param-v="{{ model.mad_tag }}" data-param-group="{{ model_group.tag }}" tabindex="0">{{ model.model }}</div>
+            {% else %}
+               <div class="col-6 px-2 model-param" data-param-k="model" data-param-v="{{ model.mad_tag }}" data-param-group="{{ model_group.tag }}" tabindex="0">{{ model.model }}</div>
+            {% endif %}
+         {% endfor %}
+      {% endfor %}
+            </div>
+         </div>
+      </div>
+
+.. seealso::
+
+   For additional workloads, including Llama 3.3, Llama 3.2, Llama 2, GPT OSS, Qwen, and Flux models,
+   see the documentation :doc:`pytorch-training` (without Primus)
+
+.. _amd-primus-pytorch-performance-measurements-v26.01:
+
+System validation
+=================
+
+Before running AI workloads, it's important to validate that your AMD hardware is configured
+correctly and performing optimally.
+
+If you have already validated your system settings, including aspects like NUMA auto-balancing, you
+can skip this step. Otherwise, complete the procedures in the :ref:`System validation and
+optimization <rocm-for-ai-system-optimization>` guide to properly configure your system settings
+before starting training.
+
+To test for optimal performance, consult the recommended :ref:`System health benchmarks
+<rocm-for-ai-system-health-bench>`. This suite of tests will help you verify and fine-tune your
+system's configuration.
+
+This Docker image is optimized for specific model configurations outlined
+below. Performance can vary for other training workloads, as AMD
+doesn’t test configurations and run conditions outside those described.
+
+Pull the Docker image
+=====================
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/training/previous-versions/primus-pytorch-v26.1-benchmark-models.yaml
+
+   Use the following command to pull the Docker image from Docker Hub.
+
+   .. code-block:: shell
+
+      docker pull {{ data.docker.pull_tag }}
+
+Run training
+============
+
+Once the setup is complete, choose between the following two workflows to start benchmarking training.
+For fine-tuning workloads and multi-node training examples, see :doc:`pytorch-training` (without Primus).
+For best performance on MI325X, MI350X, and MI355X GPUs, you might need to
+tweak some configurations (such as batch sizes).
+
+.. datatemplate:yaml:: /data/how-to/rocm-for-ai/training/previous-versions/primus-pytorch-v26.1-benchmark-models.yaml
+
+   {% set docker = data.docker %}
+   {% set model_groups = data.model_groups %}
+
+   .. tab-set::
+
+      .. tab-item:: Primus benchmarking
+
+   {% for model_group in model_groups %}
+      {% for model in model_group.models %}
+
+         .. container:: model-doc {{ model.mad_tag }}
+
+            The following run commands are tailored to {{ model.model }}.
+            See :ref:`amd-primus-pytorch-model-support-v26.01` to switch to another available model.
+
+            .. rubric:: Download the Docker image and required packages
+
+            1. Pull the ``{{ docker.pull_tag }}`` Docker image from Docker Hub.
+
+               .. code-block:: shell
+
+                  docker pull {{ docker.pull_tag }}
+
+            2. Run the Docker container.
+
+               .. code-block:: shell
+
+                  docker run -it \
+                      --device /dev/dri \
+                      --device /dev/kfd \
+                      --network host \
+                      --ipc host \
+                      --group-add video \
+                      --cap-add SYS_PTRACE \
+                      --security-opt seccomp=unconfined \
+                      --privileged \
+                      -v $HOME:$HOME \
+                      -v $HOME/.ssh:/root/.ssh \
+                      --shm-size 64G \
+                      --name training_env \
+                      {{ docker.pull_tag }}
+
+               Use these commands if you exit the ``training_env`` container and need to return to it.
+
+               .. code-block:: shell
+
+                  docker start training_env
+                  docker exec -it training_env bash
+
+               The Docker container hosts verified commit ``9c529cd4`` of the `Primus
+               <https://github.com/AMD-AGI/Primus/tree/9c529cd4a934a68a880ede036c3e97b792e38167/>`__ repository.
+
+            .. rubric:: Prepare training datasets and dependencies
+
+            The following benchmarking examples require downloading models and datasets
+            from Hugging Face. To ensure successful access to gated repos, set your
+            ``HF_TOKEN``.
+
+            .. code-block:: shell
+
+               export HF_TOKEN=$your_personal_hugging_face_access_token
+
+            .. rubric:: Pretraining
+
+            To get started, navigate to the ``Primus`` directory in your container.
+
+            .. code-block::
+
+               cd /workspace/Primus
+
+            Now, to start the pretraining benchmark, use the ``run_pretrain.sh`` script
+            included with Primus with the appropriate options.
+
+            .. rubric:: Benchmarking examples
+
+            .. container:: model-doc primus_pyt_train_llama-3.1-8b
+
+               Use the following command to run train Llama 3.1 8B with BF16 precision using Primus torchtitan.
+
+               .. tab-set::
+
+                  .. tab-item:: MI355X and MI350X
+                     :sync: MI355X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_8B.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI355X/llama3.1_8B-BF16-pretrain.yaml
+
+                  .. tab-item:: MI325X
+                     :sync: MI325X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_8B.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/llama3.1_8B-BF16-pretrain.yaml \
+                          --training.local_batch_size 6
+
+                  .. tab-item:: MI300X
+                     :sync: MI300X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_8B.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/llama3.1_8B-BF16-pretrain.yaml
+
+               To train Llama 3.1 8B with FP8 precision, use the following command.
+
+               .. tab-set::
+
+                  .. tab-item:: MI355X and MI350X
+                     :sync: MI355X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_8B_fp8.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI355X/llama3.1_8B-FP8-pretrain.yaml
+
+                  .. tab-item:: MI325X
+                     :sync: MI325X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_8B_fp8.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/llama3.1_8B-FP8-pretrain.yaml \
+                          --training.local_batch_size 7
+
+                  .. tab-item:: MI300X
+                     :sync: MI300X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_8B_fp8.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/llama3.1_8B-FP8-pretrain.yaml
+
+            .. container:: model-doc primus_pyt_train_llama-3.1-70b
+
+               Use the following command to run train Llama 3.1 70B with BF16 precision using Primus torchtitan.
+
+               .. tab-set::
+
+                  .. tab-item:: MI355X and MI350X
+                     :sync: MI355X and MI300X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_70B.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI355X/llama3.1_70B-BF16-pretrain.yaml
+
+                  .. tab-item:: MI325X
+                     :sync: MI325X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_70B.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/llama3.1_70B-BF16-pretrain.yaml \
+                          --training.local_batch_size 6
+
+                  .. tab-item:: MI300X
+                     :sync: MI300X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_70B.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/llama3.1_70B-BF16-pretrain.yaml
+
+               To train Llama 3.1 70B with FP8 precision, use the following command.
+
+               .. tab-set::
+
+                  .. tab-item:: MI355X and MI350X
+                     :sync: MI355X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_70B_fp8.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI355X/llama3.1_70B-FP8-pretrain.yaml
+
+                  .. tab-item:: MI325X
+                     :sync: MI325X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_70B_fp8.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/llama3.1_70B-FP8-pretrain.yaml \
+                          --training.local_batch_size 5
+
+                  .. tab-item:: MI300X
+                     :sync: MI300X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_llama3.1_70B_fp8.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/llama3.1_70B-FP8-pretrain.yaml
+
+            .. container:: model-doc primus_pyt_train_deepseek-v3-16b
+
+               Use the following command to run train DeepSeek V3 16B with BF16 precision using Primus torchtitan.
+
+               .. tab-set::
+
+                  .. tab-item:: MI355X and MI350X
+                     :sync: MI355X and MI300X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_deepseek_v3_16b.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI355X/deepseek_v3_16b-pretrain.yaml
+
+                  .. tab-item:: MI325X
+                     :sync: MI325X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_deepseek_v3_16b.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/deepseek_v3_16b-pretrain.yaml \
+                          --training.local_batch_size 10
+
+                  .. tab-item:: MI300X
+                     :sync: MI300X
+
+                     .. code-block:: shell
+
+                        bash runner/primus-cli direct \
+                          --log_file /tmp/primus_deepseek_v3_16b.log \
+                          -- train pretrain \
+                          --config examples/torchtitan/configs/MI300X/deepseek_v3_16b-pretrain.yaml
+      {% endfor %}
+   {% endfor %}
+
+      .. tab-item:: MAD-integrated benchmarking
+
+   {% for model_group in model_groups %}
+      {% for model in model_group.models %}
+
+         .. container:: model-doc {{ model.mad_tag }}
+
+            The following run command is tailored to {{ model.model }}.
+            See :ref:`amd-primus-pytorch-model-support-v26.01` to switch to another available model.
+
+            1. Clone the ROCm Model Automation and Dashboarding (`<https://github.com/ROCm/MAD>`__) repository to a local
+               directory and install the required packages on the host machine.
+
+               .. code-block:: shell
+
+                  git clone https://github.com/ROCm/MAD
+                  cd MAD
+                  pip install -r requirements.txt
+
+            2. For example, use this command to run the performance benchmark test on the {{ model.model }} model
+               using one node with the {{ model.precision }} data type on the host machine.
+
+               .. code-block:: shell
+
+                  export MAD_SECRETS_HFTOKEN="your personal Hugging Face token to access gated models"
+                  madengine run \
+                      --tags {{ model.mad_tag }} \
+                      --keep-model-dir \
+                      --live-output \
+                      --timeout 28800
+
+               MAD launches a Docker container with the name
+               ``container_ci-{{ model.mad_tag }}``. The latency and throughput reports of the
+               model are collected in ``~/MAD/perf.csv``.
+
+      {% endfor %}
+   {% endfor %}
+
+Further reading
+===============
+
+- For an introduction to Primus, see `Primus: A Lightweight, Unified Training
+  Framework for Large Models on AMD GPUs <https://rocm.blogs.amd.com/software-tools-optimization/primus/README.html>`__.
+
+- To learn more about MAD and the ``madengine`` CLI, see the `MAD usage guide <https://github.com/ROCm/MAD?tab=readme-ov-file#usage-guide>`__.
+
+- To learn more about system settings and management practices to configure your system for
+  AMD Instinct MI300X Series GPUs, see `AMD Instinct MI300X system optimization <https://instinct.docs.amd.com/projects/amdgpu-docs/en/latest/system-optimization/mi300x.html>`_.
+
+- For a list of other ready-made Docker images for AI with ROCm, see
+  `AMD Infinity Hub <https://www.amd.com/en/developer/resources/infinity-hub.html#f-amd_hub_category=AI%20%26%20ML%20Models>`_.
+
+Previous versions
+=================
+
+See :doc:`pytorch-training-history` to find documentation for previous releases
+of the ``ROCm/pytorch-training`` Docker image.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-history.rst

@@ -7,7 +7,7 @@ PyTorch training performance testing version history
 This table lists previous versions of the ROCm PyTorch training Docker image for
 inference performance testing. For detailed information about available models
 for benchmarking, see the version-specific documentation. You can find tagged
-previous releases of the ``ROCm/pytorch-training`` Docker image on `Docker Hub <https://hub.docker.com/r/rocm/pytorch-training/tags>`_.
+previous releases of the ``ROCm/primus`` Docker image on `Docker Hub <https://hub.docker.com/r/rocm/pytorch-training/tags>`_.
 
 .. list-table::
    :header-rows: 1
@@ -16,13 +16,20 @@ previous releases of the ``ROCm/pytorch-training`` Docker image on `Docker Hub <
      - Components
      - Resources
 
-   * - v26.1 (latest)
+   * - v26.2 (latest)
+     -
+       * ROCm 7.2.0
+       * PyTorch 2.10.0+git94c6e04
+     -
+       * :doc:`Primus PyTorch training documentation <../primus-pytorch>`
+       * `Docker Hub <https://hub.docker.com/layers/rocm/primus/v26.2/images/sha256-9148d1bfcd579bf92f44bd89090e0d8c958f149c134b4b34b9674ab559244585>`__
+
+   * - v26.1
      -
        * ROCm 7.1.0
        * PyTorch 2.10.0.dev20251112+rocm7.1
      -
-       * :doc:`Primus PyTorch training documentation <../primus-megatron>`
-       * :doc:`PyTorch training (legacy) documentation <../megatron-lm>`
+       * :doc:`Primus PyTorch training documentation <primus-pytorch-v26.1>`
        * `Docker Hub <https://hub.docker.com/layers/rocm/primus/v26.1/images/sha256-4fc8808bdb14117c6af7f38d79c809056e6fdbfd530c1fabbb61d097ddaf820d>`__
 
    * - v25.11

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.10.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.11.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.3.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.4.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.5.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.6.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.7.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.8.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/previous-versions/pytorch-training-v25.9.rst

@@ -1,4 +1,5 @@
 :orphan:
+:no-search:
 
 .. meta::
    :description: How to train a model using PyTorch for ROCm.

docs/how-to/rocm-for-ai/training/benchmark-docker/primus-megatron.rst

@@ -47,7 +47,7 @@ Megatron-LM.
               - {{ component_version }}
             {% endfor %}
 
-.. _amd-primus-megatron-lm-model-support-v26.01:
+.. _amd-primus-megatron-lm-model-support-v26.2:
 
 Supported models
 ================
@@ -65,9 +65,21 @@ might vary by model -- select one to get started.
          <div class="row gx-0">
             <div class="col-2 me-1 px-2 model-param-head">Model</div>
             <div class="row col-10 pe-0">
-      {% for model_group in model_groups %}
-               <div class="col-3 px-2 model-param" data-param-k="model-group" data-param-v="{{ model_group.tag }}" tabindex="0">{{ model_group.group }}</div>
-      {% endfor %}
+               {% set tag = "llama" %}
+               {% set group = "Meta Llama" %}
+               <div class="col-6 px-2 model-param" data-param-k="model-group" data-param-v="{{ tag }}" tabindex="0">{{ group }}</div>
+               {% set tag = "zebra-llama" %}
+               {% set group = "AMD Zebra-Llama" %}
+               <div class="col-6 px-2 model-param" data-param-k="model-group" data-param-v="{{ tag }}" tabindex="0">{{ group }}</div>
+               {% set tag = "deepseek" %}
+               {% set group = "DeepSeek" %}
+               <div class="col-4 px-2 model-param" data-param-k="model-group" data-param-v="{{ tag }}" tabindex="0">{{ group }}</div>
+               {% set tag = "mistral" %}
+               {% set group = "Mistral AI" %}
+               <div class="col-4 px-2 model-param" data-param-k="model-group" data-param-v="{{ tag }}" tabindex="0">{{ group }}</div>
+               {% set tag = "qwen" %}
+               {% set group = "Qwen" %}
+               <div class="col-4 px-2 model-param" data-param-k="model-group" data-param-v="{{ tag }}" tabindex="0">{{ group }}</div>
             </div>
          </div>
 
@@ -108,7 +120,7 @@ To test for optimal performance, consult the recommended :ref:`System health ben
 <rocm-for-ai-system-health-bench>`. This suite of tests will help you verify and fine-tune your
 system's configuration.
 
-.. _mi300x-amd-primus-megatron-lm-training-v26.01:
+.. _mi300x-amd-primus-megatron-lm-training-v26.2:
 
 Environment setup
 =================
@@ -118,7 +130,7 @@ Environment setup
    Use the following instructions to set up the environment, configure the script to train models, and
    reproduce the benchmark results on AMD Instinct GPUs.
 
-.. _amd-primus-megatron-lm-requirements-v26.01:
+.. _amd-primus-megatron-lm-requirements-v26.2:
 
 Pull the Docker image
 
@@ -160,7 +172,7 @@ Pull the Docker image
 The Docker container hosts verified commit ``9c529cd4`` of the `Primus
 <https://github.com/AMD-AGI/Primus/tree/9c529cd4a934a68a880ede036c3e97b792e38167>`__ repository.
 
-.. _amd-primus-megatron-lm-environment-setup-v26.01:
+.. _amd-primus-megatron-lm-environment-setup-v26.2:
 
 Configuration
 =============
@@ -207,7 +219,7 @@ You can use either mock data or real data for training.
 
   Ensure that the files are accessible inside the Docker container.
 
-.. _amd-primus-megatron-lm-tokenizer-v26.01:
+.. _amd-primus-megatron-lm-tokenizer-v26.2:
 
 Tokenizer
 ---------
@@ -220,7 +232,7 @@ right permissions to access the tokenizer for each model.
    # Export your HF_TOKEN in the workspace
    export HF_TOKEN=<your_hftoken>
 
-.. _amd-primus-megatron-lm-run-training-v26.01:
+.. _amd-primus-megatron-lm-run-training-v26.2:
 
 Run training
 ============
@@ -237,14 +249,12 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 .. code-block:: shell
 
    pip install -r requirements.txt
-   export HSA_NO_SCRATCH_RECLAIM=1
-   export NVTE_CK_USES_BWD_V3=1
 
 .. container:: model-doc primus_pyt_megatron_lm_train_llama-3.3-70b
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 3.3 70B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run pre-training for Llama 3.3 70B BF16, run:
 
@@ -279,7 +289,7 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 3.1 8B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run pre-training for Llama 3.1 8B FP8, run:
 
@@ -343,7 +353,7 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 3.1 70B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run pre-training for Llama 3.1 70B BF16, run:
 
@@ -357,7 +367,9 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
             bash runner/primus-cli direct \
               --log_file /tmp/primus_llama3.1_70B.log \
               -- train pretrain \
-              --config examples/megatron/configs/MI355X/llama3.1_70B-BF16-pretrain.yaml
+              --config examples/megatron/configs/MI355X/llama3.1_70B-BF16-pretrain.yaml \
+              --micro_batch_size 8 \
+              --global_batch_size 128
 
       .. tab-item:: MI300X
          :sync: MI325X and MI300X
@@ -417,7 +429,7 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 2 7B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run pre-training for Llama 2 7B FP8, run:
 
@@ -481,7 +493,7 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 2 70B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run pre-training for Llama 2 70B BF16, run:
 
@@ -516,7 +528,7 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to DeepSeek-V3.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run training on a single node for DeepSeek-V3 (MoE with expert parallel) BF16 with 3-layer proxy,
    use the following command:
@@ -536,7 +548,9 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
               --moe_layer_freq 1 \
               --train_iters 50 \
               --micro_batch_size 8 \
-              --global_batch_size 64
+              --global_batch_size 64 \
+              --moe_use_fused_router_with_aux_score True \
+              --moe_permute_fusion True
 
       .. tab-item:: MI300X
          :sync: MI325X and MI300X
@@ -562,7 +576,7 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to DeepSeek-V2-Lite.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run training on a single node for DeepSeek-V2-Lite (MoE with expert parallel) BF16,
    use the following command:
@@ -577,7 +591,11 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
             bash runner/primus-cli direct \
               --log_file /tmp/primus_deepseek_v2_lite.log \
               -- train pretrain \
-              --config examples/megatron/configs//MI355X/deepseek_v2_lite-BF16-pretrain.yaml
+              --config examples/megatron/configs//MI355X/deepseek_v2_lite-BF16-pretrain.yaml \
+              --use_turbo_grouped_mlp False \
+              --moe_use_legacy_grouped_gemm True \
+              --moe_use_fused_router_with_aux_score True \
+              --moe_permute_fusion True
 
       .. tab-item:: MI300X
          :sync: MI325X and MI300X
@@ -598,7 +616,7 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Mixtral 8x7B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run training on a single node for Mixtral 8x7B (MoE with expert parallel),
    use the following command:
@@ -634,7 +652,7 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Mixtral 8x22B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run training on a single node for Mixtral 8x22B BF16 (MoE with expert parallel) 4-layer proxy,
    use the following command:
@@ -671,11 +689,83 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
               --global_batch_size 16 \
               --train_iters 50
 
+.. container:: model-doc primus_pyt_megatron_lm_train_qwen3-32b-lora
+
+   Once setup is complete, run the appropriate training command.
+   The following run commands are tailored to post-training Qwen 3 32B (LoRA).
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
+
+   To run training on a single node for Qwen 3 32B BF16 (SFT), use the following
+   command:
+
+   .. tab-set::
+
+      .. tab-item:: MI355X and MI350X
+         :sync: MI355X and MI350X
+
+         .. code-block:: shell
+
+            bash runner/primus-cli direct \
+              --log_file /tmp/primus_qwen3_32b.log \
+              -- train posttrain \
+              --config examples/megatron_bridge/configs/MI355X/qwen3_32b_lora_posttrain.yaml
+
+      .. tab-item:: MI300X
+         :sync: MI325X and MI300X
+
+         .. code-block:: shell
+
+            # Set the variables for better performance
+            # only on MI325X and MI300X
+            export PRIMUS_TURBO_ATTN_V3_ATOMIC_FP32=1
+            export NVTE_CK_IS_V3_ATOMIC_FP32=1
+
+            bash runner/primus-cli direct \
+              --log_file /tmp/primus_qwen3_32b.log \
+              -- train posttrain \
+              --config examples/megatron_bridge/configs/MI300X/qwen3_32b_lora_posttrain.yaml
+
+.. container:: model-doc primus_pyt_megatron_lm_train_qwen3-32b-sft
+
+   Once setup is complete, run the appropriate training command.
+   The following run commands are tailored to post-training Qwen 3 32B (SFT).
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
+
+   To run training on a single node for Qwen 3 32B BF16 (SFT), use the following
+   command:
+
+   .. tab-set::
+
+      .. tab-item:: MI355X and MI350X
+         :sync: MI355X and MI350X
+
+         .. code-block:: shell
+
+            bash runner/primus-cli direct \
+              --log_file /tmp/primus_qwen3_32b_sft.log \
+              -- train posttrain \
+              --config examples/megatron_bridge/configs/MI355X/qwen3_32b_sft_posttrain.yaml
+
+      .. tab-item:: MI300X
+         :sync: MI325X and MI300X
+
+         .. code-block:: shell
+
+            # Set the variables for better performance
+            # only on MI325X and MI300X
+            export PRIMUS_TURBO_ATTN_V3_ATOMIC_FP32=1
+            export NVTE_CK_IS_V3_ATOMIC_FP32=1
+
+            bash runner/primus-cli direct \
+              --log_file /tmp/primus_qwen3_32b_sft.log \
+              -- train posttrain \
+              --config examples/megatron_bridge/configs/MI300X/qwen3_32b_sft_posttrain.yaml
+
 .. container:: model-doc primus_pyt_megatron_lm_train_qwen2.5-7b
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Qwen 2.5 7B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run training on a single node for Qwen 2.5 7B BF16, use the following
    command:
@@ -740,7 +830,7 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Qwen 2.5 72B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To run the training on a single node for Qwen 2.5 72B BF16, use the following command.
 
@@ -771,7 +861,112 @@ To run training on a single node, navigate to ``/workspace/Primus`` and use the
               -- train pretrain \
               --config examples/megatron/configs/MI300X/qwen2.5_72B-BF16-pretrain.yaml
 
-.. _amd-primus-megatron-multi-node-examples-v26.01:
+.. container:: model-doc primus_pyt_megatron_lm_train_zebra-llama-1b
+
+   Once setup is complete, run the appropriate training command.
+   The following run commands are tailored to Zebra-Llama 1B.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
+
+   To run the training on a single node for AMD Zebra-Llama 1B BF16, use the following command.
+
+   .. tab-set::
+
+      .. tab-item:: MI355X and MI350X
+         :sync: MI355X and MI350X
+
+         .. code-block:: shell
+
+            PRIMUS_TRAIN_RUNTIME=legacy bash runner/primus-cli direct \
+              --log_file /tmp/primus_zebra_llama_1B.log \
+              -- train pretrain \
+              --config examples/megatron/configs/MI355X/zebra_llama_1B-pretrain.yaml
+
+      .. tab-item:: MI300X
+         :sync: MI325X and MI300X
+
+         .. code-block:: shell
+
+            # Set the variables for better performance
+            # only on MI325X and MI300X
+            export PRIMUS_TURBO_ATTN_V3_ATOMIC_FP32=1
+            export NVTE_CK_IS_V3_ATOMIC_FP32=1
+
+            PRIMUS_TRAIN_RUNTIME=legacy bash runner/primus-cli direct \
+              --log_file /tmp/primus_zebra_llama_1B.log \
+              -- train pretrain \
+              --config examples/megatron/configs/MI300X/zebra_llama_1B-pretrain.yaml
+
+.. container:: model-doc primus_pyt_megatron_lm_train_zebra-llama-3b
+
+   Once setup is complete, run the appropriate training command.
+   The following run commands are tailored to Zebra-Llama 3B.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
+
+   To run the training on a single node for AMD Zebra-Llama 3B BF16, use the following command.
+
+   .. tab-set::
+
+      .. tab-item:: MI355X and MI350X
+         :sync: MI355X and MI350X
+
+         .. code-block:: shell
+
+            PRIMUS_TRAIN_RUNTIME=legacy bash runner/primus-cli direct \
+              --log_file /tmp/primus_zebra_llama_3B.log \
+              -- train pretrain \
+              --config examples/megatron/configs/MI355X/zebra_llama_3B-pretrain.yaml
+
+      .. tab-item:: MI300X
+         :sync: MI325X and MI300X
+
+         .. code-block:: shell
+
+            # Set the variables for better performance
+            # only on MI325X and MI300X
+            export PRIMUS_TURBO_ATTN_V3_ATOMIC_FP32=1
+            export NVTE_CK_IS_V3_ATOMIC_FP32=1
+
+            PRIMUS_TRAIN_RUNTIME=legacy bash runner/primus-cli direct \
+              --log_file /tmp/primus_zebra_llama_3B.log \
+              -- train pretrain \
+              --config examples/megatron/configs/MI300X/zebra_llama_3B-pretrain.yaml
+
+.. container:: model-doc primus_pyt_megatron_lm_train_zebra-llama-8b
+
+   Once setup is complete, run the appropriate training command.
+   The following run commands are tailored to Zebra Llama 8B.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
+
+   To run the training on a single node for AMD Zebra-Llama 8B BF16, use the following command.
+
+   .. tab-set::
+
+      .. tab-item:: MI355X and MI350X
+         :sync: MI355X and MI350X
+
+         .. code-block:: shell
+
+            PRIMUS_TRAIN_RUNTIME=legacy bash runner/primus-cli direct \
+              --log_file /tmp/primus_zebra_llama_8B.log \
+              -- train pretrain \
+              --config examples/megatron/configs/MI355X/zebra_llama_8B-pretrain.yaml
+
+      .. tab-item:: MI300X
+         :sync: MI325X and MI300X
+
+         .. code-block:: shell
+
+            # Set the variables for better performance
+            # only on MI325X and MI300X
+            export PRIMUS_TURBO_ATTN_V3_ATOMIC_FP32=1
+            export NVTE_CK_IS_V3_ATOMIC_FP32=1
+
+            PRIMUS_TRAIN_RUNTIME=legacy bash runner/primus-cli direct \
+              --log_file /tmp/primus_zebra_llama_8B.log \
+              -- train pretrain \
+              --config examples/megatron/configs/MI300X/zebra_llama_8B-pretrain.yaml
+
+.. _amd-primus-megatron-multi-node-examples-v26.2:
 
 Multi-node training examples
 ----------------------------
@@ -789,14 +984,11 @@ to launch the multi-node workload. Use the following steps to setup your environ
    .. code-block:: shell
 
       git clone --recurse-submodules https://github.com/AMD-AGI/Primus.git
-      cd Primus
-      git checkout c4c083de64ba3e8f19ccc9629411267108931f9e
+      cd Primus/
+      git checkout 44f780d
       git submodule update --init --recursive
-
       export DOCKER_IMAGE={{ docker.pull_tag }}
       export HF_TOKEN=<your_HF_token>
-      export HSA_NO_SCRATCH_RECLAIM=1
-      export NVTE_CK_USES_BWD_V3=1
       export NCCL_IB_HCA=<your_NCCL_IB_HCA> # specify which RDMA interfaces to use for communication
       export NCCL_SOCKET_IFNAME=<your_NCCL_SOCKET_IFNAME> # your Network Interface
       export GLOO_SOCKET_IFNAME=<your_GLOO_SOCKET_IFNAME> # your Network Interface
@@ -813,13 +1005,13 @@ to launch the multi-node workload. Use the following steps to setup your environ
    * If ``NCCL_IB_HCA`` and ``NCCL_SOCKET_IFNAME`` are not set, Primus will try to auto-detect. However, since NICs can vary accross different cluster, it is encouraged to explicitly export your NCCL parameters for the cluster.
    * To find your network interface, you can use ``ip a``.
    * To find RDMA interfaces, you can use ``ibv_devices`` to get the list of all the RDMA/IB  devices.
-   * Remember to set ``DOCKER_IMAGE`` and ``HF_TOKEN`` (see :ref:`amd-primus-megatron-lm-tokenizer-v26.01`) as appropriate.
+   * Remember to set ``DOCKER_IMAGE`` and ``HF_TOKEN`` (see :ref:`amd-primus-megatron-lm-tokenizer-v26.2`) as appropriate.
 
 .. container:: model-doc primus_pyt_megatron_lm_train_llama-3.1-8b
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 3.1 8B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To train Llama 3.1 8B FP8 on 8 nodes, run:
 
@@ -836,7 +1028,7 @@ to launch the multi-node workload. Use the following steps to setup your environ
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 2 7B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To train Llama 2 7B FP8 on 8 nodes, run:
 
@@ -853,7 +1045,7 @@ to launch the multi-node workload. Use the following steps to setup your environ
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 3.1 70B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To train Llama 3.1 70B FP8 on 8 nodes, run:
 
@@ -883,7 +1075,7 @@ to launch the multi-node workload. Use the following steps to setup your environ
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 2 70B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To train Llama 2 70B FP8 on 8 nodes, run:
 
@@ -913,7 +1105,7 @@ to launch the multi-node workload. Use the following steps to setup your environ
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 3.3 70B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To train Llama 3.3 70B FP8 on 8 nodes, run:
 
@@ -943,7 +1135,7 @@ to launch the multi-node workload. Use the following steps to setup your environ
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 2 70B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To train Mixtral 8x7B BF16 on 8 nodes, run:
 
@@ -961,7 +1153,7 @@ to launch the multi-node workload. Use the following steps to setup your environ
 
    Once setup is complete, run the appropriate training command.
    The following run commands are tailored to Llama 2 70B.
-   See :ref:`amd-primus-megatron-lm-model-support-v26.01` to switch to another available model.
+   See :ref:`amd-primus-megatron-lm-model-support-v26.2` to switch to another available model.
 
    To train Qwen2.5 72B FP8 on 8 nodes, run:
 
@@ -976,7 +1168,7 @@ to launch the multi-node workload. Use the following steps to setup your environ
           --global_batch_size 512 \
           --recompute_num_layers 80 \
 
-.. _amd-primus-megatron-lm-benchmark-test-vars-v26.01:
+.. _amd-primus-megatron-lm-benchmark-test-vars-v26.2:
 
 Key options
 -----------
@@ -1018,14 +1210,6 @@ recompute_granularity
 num_layers
   For using a reduced number of layers as with proxy models.
 
-Known issues
-============
-
-DeepSeekV3 proxy model and Mixtral 8x22B proxy model may exit with an error
-due to a memory free issue. However, this does not impacts training runs. All
-iterations, in this case 50, should have been completed before the exit and
-the results should be available in the end.
-
 Further reading
 ===============
 

docs/how-to/rocm-for-ai/training/benchmark-docker/primus-pytorch.rst

@@ -45,7 +45,7 @@ with Primus Turbo optimizations.
               - {{ component_version }}
             {% endfor %}
 
-.. _amd-primus-pytorch-model-support-v26.01:
+.. _amd-primus-pytorch-model-support-v26.2:
 
 Supported models
 ================
@@ -91,7 +91,7 @@ vary by model -- select one to get started.
    For additional workloads, including Llama 3.3, Llama 3.2, Llama 2, GPT OSS, Qwen, and Flux models,
    see the documentation :doc:`pytorch-training` (without Primus)
 
-.. _amd-primus-pytorch-performance-measurements-v26.01:
+.. _amd-primus-pytorch-performance-measurements-v26.2:
 
 System validation
 =================
@@ -146,7 +146,7 @@ tweak some configurations (such as batch sizes).
          .. container:: model-doc {{ model.mad_tag }}
 
             The following run commands are tailored to {{ model.model }}.
-            See :ref:`amd-primus-pytorch-model-support-v26.01` to switch to another available model.
+            See :ref:`amd-primus-pytorch-model-support-v26.2` to switch to another available model.
 
             .. rubric:: Download the Docker image and required packages
 
@@ -224,17 +224,6 @@ tweak some configurations (such as batch sizes).
                           -- train pretrain \
                           --config examples/torchtitan/configs/MI355X/llama3.1_8B-BF16-pretrain.yaml
 
-                  .. tab-item:: MI325X
-                     :sync: MI325X
-
-                     .. code-block:: shell
-
-                        bash runner/primus-cli direct \
-                          --log_file /tmp/primus_llama3.1_8B.log \
-                          -- train pretrain \
-                          --config examples/torchtitan/configs/MI300X/llama3.1_8B-BF16-pretrain.yaml \
-                          --training.local_batch_size 6
-
                   .. tab-item:: MI300X
                      :sync: MI300X
 
@@ -259,17 +248,6 @@ tweak some configurations (such as batch sizes).
                           -- train pretrain \
                           --config examples/torchtitan/configs/MI355X/llama3.1_8B-FP8-pretrain.yaml
 
-                  .. tab-item:: MI325X
-                     :sync: MI325X
-
-                     .. code-block:: shell
-
-                        bash runner/primus-cli direct \
-                          --log_file /tmp/primus_llama3.1_8B_fp8.log \
-                          -- train pretrain \
-                          --config examples/torchtitan/configs/MI300X/llama3.1_8B-FP8-pretrain.yaml \
-                          --training.local_batch_size 7
-
                   .. tab-item:: MI300X
                      :sync: MI300X
 
@@ -296,17 +274,6 @@ tweak some configurations (such as batch sizes).
                           -- train pretrain \
                           --config examples/torchtitan/configs/MI355X/llama3.1_70B-BF16-pretrain.yaml
 
-                  .. tab-item:: MI325X
-                     :sync: MI325X
-
-                     .. code-block:: shell
-
-                        bash runner/primus-cli direct \
-                          --log_file /tmp/primus_llama3.1_70B.log \
-                          -- train pretrain \
-                          --config examples/torchtitan/configs/MI300X/llama3.1_70B-BF16-pretrain.yaml \
-                          --training.local_batch_size 6
-
                   .. tab-item:: MI300X
                      :sync: MI300X
 
@@ -331,17 +298,6 @@ tweak some configurations (such as batch sizes).
                           -- train pretrain \
                           --config examples/torchtitan/configs/MI355X/llama3.1_70B-FP8-pretrain.yaml
 
-                  .. tab-item:: MI325X
-                     :sync: MI325X
-
-                     .. code-block:: shell
-
-                        bash runner/primus-cli direct \
-                          --log_file /tmp/primus_llama3.1_70B_fp8.log \
-                          -- train pretrain \
-                          --config examples/torchtitan/configs/MI300X/llama3.1_70B-FP8-pretrain.yaml \
-                          --training.local_batch_size 5
-
                   .. tab-item:: MI300X
                      :sync: MI300X
 
@@ -368,17 +324,6 @@ tweak some configurations (such as batch sizes).
                           -- train pretrain \
                           --config examples/torchtitan/configs/MI355X/deepseek_v3_16b-pretrain.yaml
 
-                  .. tab-item:: MI325X
-                     :sync: MI325X
-
-                     .. code-block:: shell
-
-                        bash runner/primus-cli direct \
-                          --log_file /tmp/primus_deepseek_v3_16b.log \
-                          -- train pretrain \
-                          --config examples/torchtitan/configs/MI300X/deepseek_v3_16b-pretrain.yaml \
-                          --training.local_batch_size 10
-
                   .. tab-item:: MI300X
                      :sync: MI300X
 
@@ -399,7 +344,7 @@ tweak some configurations (such as batch sizes).
          .. container:: model-doc {{ model.mad_tag }}
 
             The following run command is tailored to {{ model.model }}.
-            See :ref:`amd-primus-pytorch-model-support-v26.01` to switch to another available model.
+            See :ref:`amd-primus-pytorch-model-support-v26.2` to switch to another available model.
 
             1. Clone the ROCm Model Automation and Dashboarding (`<https://github.com/ROCm/MAD>`__) repository to a local
                directory and install the required packages on the host machine.

docs/how-to/rocm-for-ai/training/benchmark-docker/pytorch-training.rst

@@ -631,8 +631,8 @@ To launch the training job on a SLURM cluster for Llama 3.3 70B, run the followi
 
 .. code-block:: shell
 
-   huggingface-cli login # Get access to HF Llama model space
-   huggingface-cli download meta-llama/Llama-3.3-70B-Instruct --local-dir ./models/Llama-3.3-70B-Instruct # Download the Llama 3.3 model locally
+   hf auth login # Get access to HF Llama model space
+   hf download meta-llama/Llama-3.3-70B-Instruct --local-dir ./models/Llama-3.3-70B-Instruct # Download the Llama 3.3 model locally
    # In the MAD repository
    cd scripts/pytorch_train
    sbatch Torchtune_Multinode.sh

docs/how-to/system-optimization/index.rst

@@ -14,7 +14,7 @@ optimize performance for specific types of workloads or use-cases. The contents
 
   .. grid-item-card:: AMD RDNA
 
-    * :doc:`AMD RDNA3.5 system optimization <strixhalo>`
+    * :doc:`AMD RDNA3.5 system optimization <rdna3-5>`
     * :doc:`AMD RDNA2 system optimization <w6000-v620>`
 
   .. grid-item-card:: AMD Instinct

docs/how-to/system-optimization/rdna3-5.rst

@@ -0,0 +1,273 @@
+.. meta::
+   :description: System optimization of AMD RDNA3.5 Ryzen APUs (gfx1150/gfx1151/gfx1152) systems. Learn about VRAM, GTT, TTM tuning, shared memory configuration, and required Linux kernel support.
+   :keywords: AMD RDNA3.5, Ryzen APU, gfx1150, gfx1151, gfx1152, ROCm, VRAM, GTT, GART, TTM, GPUVM, system optimization
+
+:orphan:
+
+.. _strix-halo-optimization:
+
+==========================================
+AMD RDNA3.5 system optimization
+==========================================
+
+This topic describes how to optimize systems powered by AMD Ryzen APUs with
+RDNA3.5 architecture. These APUs combine high-performance CPU cores with
+integrated RDNA3.5 graphics, and support LPDDR5X-8000 or DDR5 memory, making
+them particularly well-suited for:
+
+* LLM development and inference systems
+* High-performance workstations
+* Virtualization hosts running multiple VMs
+* GPU compute and parallel processing
+* Gaming systems
+* Home servers and AI development platforms
+
+.. _memory-settings:
+
+Memory settings
+===============
+
+AMD Ryzen APUs with RDNA3.5 architecture (gfx1150, gfx1151, and gfx1152 LLVM
+targets) memory access is handled through GPU Virtual Memory (GPUVM), which
+provides per-process GPU virtual address spaces (VMIDs) rather than a separate,
+discrete VRAM pool.
+
+As a result, memory on RDNA3.5 APUs is mapped rather than physically
+partitioned. The terms Graphics Address Remapping Table (GART) and Graphics
+Translation Table (GTT) describe limits on how much system memory can be mapped
+into GPU address spaces and who can use it, rather than distinct types of
+physical memory.
+
+* **GART**
+
+  Defines the amount of platform address space (system RAM or Memory-Mapped I/O)
+  that can be mapped into the GPU virtual address space used by the kernel driver.
+  On systems with physically shared CPU and GPU memory, such as RDNA3.5-based
+  systems, this mapped system memory effectively serves as VRAM for the GPU.
+  GART is typically kept relatively small to limit GPU page-table size and is
+  primarily used for driver-internal operations.
+
+* **GTT**
+
+  Defines the amount of system RAM that can be mapped into GPU virtual address
+  spaces for user processes. This is the memory pool used by applications such
+  as PyTorch and other AI/compute workloads. GTT allocations are dynamic and
+  not permanently reserved, allowing the operating system to reclaim memory when
+  the GPU isn't actively using it. By default, the GTT limit is set to
+  approximately 50 percent of total system RAM.
+
+.. note::
+
+  On systems with physically shared CPU and GPU memory, such as RDNA3.5-based
+  systems, several terms are often used interchangeably in firmware menus,
+  documentation, and community discussions:
+
+  * VRAM
+  * Carve-out
+  * GART
+  * Dedicated GPU memory
+  * Firmware-reserved GPU memory
+
+  In this topic, VRAM will be used going forward.
+
+You can adjust the amount of memory available to the GPU by:
+
+* Increasing the VRAM in BIOS, or
+
+* Reducing the configured GTT size to be smaller than the reserved amount.
+
+If the GTT size is larger than the VRAM, the AMD GPU driver performs VRAM
+allocations using GTT (GTT-backed allocations), as described in the
+`torvalds/linux@759e764 <https://github.com/torvalds/linux/commit/759e764f7d587283b4e0b01ff930faca64370e59>`_
+GitHub commit.
+
+Because memory is physically shared, there's no performance distinction
+like that of discrete GPUs where dedicated VRAM is significantly faster than
+system memory. Firmware may optionally reserve some memory exclusively for GPU
+use, but this provides little benefit for most workloads while permanently
+reducing available system memory.
+
+For this reason, AI frameworks work more efficiently with GTT-backed allocations. GTT
+allows large, flexible mappings without permanently reserving memory, resulting
+in better overall system utilization on unified memory systems.
+
+Configuring shared memory limits on Linux
+-----------------------------------------
+
+The maximum amount of shared GPU-accessible memory can be increased by changing
+the kernel **Translation Table Manager (TTM)** page limit. This setting controls
+how many system memory pages can be mapped for GPU use and is exposed at:
+
+::
+
+   /sys/module/ttm/parameters/pages_limit
+
+The value is expressed in **pages**, and not bytes or gigabytes (GB).
+
+.. note::
+
+   It's recommended to keep the dedicated VRAM reservation in BIOS small
+   (for example, 0.5 GB) and increasing the shared (TTM/GTT) limit instead.
+
+A helper utility is available to simplify configuration.
+
+1. Install ``pipx``:
+
+   ::
+
+      sudo apt install pipx
+      pipx ensurepath
+
+2. Install the AMD debug tools:
+
+   ::
+
+      pipx install amd-debug-tools
+
+3. Query the current shared memory configuration:
+
+   ::
+
+      amd-ttm
+
+4. Set the usable shared memory (in GB):
+
+   ::
+
+      amd-ttm --set <NUM>
+
+5. Reboot for changes to take effect.
+
+.. note::
+
+  The amd-ttm convert the pages to GB to help the users.
+
+Example with output
+^^^^^^^^^^^^^^^^^^^
+
+Check the current settings:
+
+::
+
+   amd-ttm
+   💻 Current TTM pages limit: 16469033 pages (62.82 GB)
+   💻 Total system memory: 125.65 GB
+
+Change the usable shared memory:
+
+::
+
+   ❯ amd-ttm --set 100
+   🐧 Successfully set TTM pages limit to 26214400 pages (100.00 GB)
+   🐧 Configuration written to /etc/modprobe.d/ttm.conf
+   ○ NOTE: You need to reboot for changes to take effect.
+   Would you like to reboot the system now? (y/n): y
+
+Revert to kernel defaults:
+
+::
+
+   ❯ amd-ttm --clear
+  🐧 Configuration /etc/modprobe.d/ttm.conf removed
+   Would you like to reboot the system now? (y/n): y
+
+.. _operating-system-support:
+
+Operating system support
+========================
+
+The ROCm compatibility tables can be found at the following links:
+
+- `System requirements (Linux) <https://rocm.docs.amd.com/projects/install-on-linux/en/latest/reference/system-requirements.html>`_
+- `System requirements (Microsoft Windows) <https://rocm.docs.amd.com/projects/install-on-windows/en/latest/reference/system-requirements.html>`_
+
+AMD Ryzen AI Max series APUs (gfx1151) have additional kernel version
+requirements, as described in the  following section.
+
+Required kernel version
+-----------------------
+
+Support for AMD Ryzen AI Max series APUs requires specific Linux kernel fixes
+that update internal limits in the AMD KFD driver to ensure correct queue
+creation and memory availability checks. Without these updates, GPU compute
+workloads might fail to initialize or exhibit unpredictable behavior.
+
+The following commits are required for AMD Ryzen AI Max series support:
+
+- `gregkh/linux@7f26af7 <https://github.com/gregkh/linux/commit/7f26af7bf9b76c2c2a1a761aab5803e52be21eea>`_
+- `gregkh/linux@7445db6 <https://github.com/gregkh/linux/commit/7445db6a7d5a0242d8214582b480600b266cba9e>`_
+
+These patches are available in the following minimum kernel versions:
+
+- Ubuntu 24.04 Hardware Enablement (HWE): ``6.17.0-19.19~24.04.2`` or later
+- Ubuntu 24.04 Original Equipment Manufacturer (OEM): ``6.14.0-1018`` or later
+- All other distributions: Linux kernel ``6.18.4`` or later
+
+The table below reflects compatibility for AMD-released pre-built ROCm
+binaries only. Distributions that ship native ROCm packaging might
+provide different support levels.
+
+.. list-table::
+   :header-rows: 0
+   :widths: 10 90
+
+   * - ❌
+     - Unsupported combination
+   * - ⚠️
+     - Unstable/experimental combination
+   * - ✅
+     - Stable and supported combination
+
+.. list-table::
+   :header-rows: 1
+   :widths: 20 50 15 15
+
+   * - ROCm Release
+     - | Ubuntu 24.04 HWE (>= 6.17.0-19.19~24.04.2),
+       | Ubuntu 24.04 OEM (>= 6.14.0-1018) or
+       | Ubuntu 26.04 Generic
+     - Other distributions >= 6.18.4
+     - Other distributions < 6.18.4
+
+   * - 7.11.0 or 7.12.0
+     - ✅
+     - ✅
+     - ⚠️
+
+   * - 7.10.0 or 7.9.0
+     - ❌
+     - ❌
+     - ⚠️
+
+   * - 7.2.1
+     - ✅
+     - ✅
+     - ⚠️
+
+   * - 7.2.0
+     - ✅
+     - ✅
+     - ❌
+
+   * - 7.1.x
+     - ❌
+     - ❌
+     - ⚠️
+
+   * - 6.4.x
+     - ❌
+     - ❌
+     - ⚠️
+
+.. note::
+
+  Ubuntu 24.04 HWE kernels earlier than ``6.17.0-19.19~24.04.2`` and Ubuntu
+  24.04 OEM kernels earlier than ``6.14.0-1018`` are not supported for
+  RDNA3.5 APUs.
+  
+  The following distributions include the required fixes in their native
+  packaging, independent of AMD pre-built binaries: 
+
+  - Fedora 43
+  - Ubuntu 26.04
+  - Arch Linux 2026.02.01

docs/how-to/system-optimization/strixhalo.rst

@@ -1,289 +0,0 @@
-.. meta::
-   :description: Learn about system settings and performance tuning for AMD Strix Halo (Ryzen AI MAX/MAX+) APUs.
-   :keywords: Strix Halo, Ryzen AI MAX, workstation, BIOS, installation, APU, optimization, ROCm
-
-.. _strix-halo-optimization:
-
-==========================================
-AMD Strix Halo system optimization
-==========================================
-
-This document provides guidance for optimizing systems powered by AMD Ryzen AI
-MAX and MAX+ processors (codenamed Strix Halo). These APUs combine
-high-performance CPU cores with integrated RDNA 3.5 graphics and support up to
-128GB of unified LPDDR5X-8000 memory, making them particularly well-suited for:
-
-* LLM development and inference systems
-* High-performance workstations
-* Virtualization hosts running multiple VMs
-* GPU compute and parallel processing
-* Gaming systems
-* Home servers and AI development platforms
-
-The main purpose of this document is to help users utilize Strix Halo APUs to
-their full potential through proper system configuration.
-
-.. _memory-settings:
-
-Memory settings
-===============
-
-On Strix Halo GPUs (gfx1151) memory access is handled through GPU Virtual Memory
-(GPUVM), which provides per-process GPU virtual address spaces (VMIDs) rather
-than a separate, discrete VRAM pool.
-
-As a result, memory on Strix Halo is **mapped**, not physically partitioned.
-The terms Graphics Address Remapping Table (GART) and GTT (Graphics Translation
-Table) describe limits on how much system memory can be mapped into GPU address
-spaces and who can use it, rather than distinct types of physical memory.
-
-* **GART**
-
-  Defines the amount of platform address space (system RAM or Memory-Mapped I/O)
-  that can be mapped into the GPU virtual address space used by the kernel driver.
-  On systems with physically shared CPU and GPU memory, such as Strix Halo, this
-  mapped system memory effectively serves as VRAM for the GPU. GART is typically
-  kept relatively small to limit GPU page-table size and is mainly used for
-  driver-internal operations.
-
-* **GTT**
-
-  Defines the amount of system RAM that can be mapped into GPU virtual address
-  spaces for user processes. This is the memory pool used by applications such
-  as PyTorch and other AI/compute workloads. GTT allocations are dynamic and are
-  not permanently reserved, allowing the operating system to reclaim memory when
-  it is not actively used by the GPU. By default, the GTT limit is set to
-  approximately 50% of total system RAM.
-
-.. note::
-
-  On systems with physically shared CPU and GPU memory such as Strix Halo,
-  several terms are often used interchangeably in firmware menus, documentations
-  and community discussions:
-
-  * VRAM
-  * Carve-out
-  * GART
-  * Dedicated GPU memory
-  * Firmware-reserved GPU memory
-
-  In this document, we will use VRAM from this point onward.
-
-If desired, you can adjust how much memory is preferentially available to the
-GPU by:
-
-* Increasing the VRAM in BIOS, or
-
-* Reducing the configured GTT size so it is smaller than the reserved amount.
-
-If the GTT size bigger than VRAM at that case the amdgpu driver for VRAM allocation
-using GTT (GTT-backed allocations) as you can see in
-`torvalds/linux@759e764 <https://github.com/torvalds/linux/commit/759e764f7d587283b4e0b01ff930faca64370e59>`_
-commit.
-
-Because memory is physically shared, there is no performance distinction
-similar to discrete GPUs where dedicated VRAM is significantly faster than
-system memory. Firmware may optionally reserve some memory exclusively for GPU
-use, but this provides little benefit for most workloads while permanently
-reducing available system memory.
-
-For this reason, AI frameworks typically prefer GTT-backed allocations. GTT
-allows large, flexible mappings without permanently reserving memory, resulting
-in better overall system utilization on unified memory systems.
-
-Configuring shared memory limits on linux
------------------------------------------
-
-The maximum amount of shared GPU-accessible memory can be increased by changing
-the kernel **Translation Table Manager (TTM)** page limit. This setting controls
-how many system memory pages may be mapped for GPU use and is exposed at:
-
-::
-
-   /sys/module/ttm/parameters/pages_limit
-
-The value is expressed in **pages**, not bytes or gigabytes (GB).
-
-.. note::
-
-   AMD recommends keeping the dedicated VRAM reservation in BIOS small
-   (for example 0.5 GB) and increasing the shared (TTM/GTT) limit instead.
-
-A helper utility is available to simplify configuration.
-
-1. Install ``pipx``:
-
-   ::
-
-      sudo apt install pipx
-      pipx ensurepath
-
-2. Install the AMD debug tools:
-
-   ::
-
-      pipx install amd-debug-tools
-
-3. Query the current shared memory configuration:
-
-   ::
-
-      amd-ttm
-
-4. Set the usable shared memory (in GB):
-
-   ::
-
-      amd-ttm --set <NUM>
-
-5. Reboot for changes to take effect.
-
-.. note::
-
-  The amd-ttm convert the pages to GB to help the users.
-
-**Example with output**
-
-Check the current settings:
-
-::
-
-   amd-ttm
-   💻 Current TTM pages limit: 16469033 pages (62.82 GB)
-   💻 Total system memory: 125.65 GB
-
-Change the usable shared memory:
-
-::
-
-   ❯ amd-ttm --set 100
-   🐧 Successfully set TTM pages limit to 26214400 pages (100.00 GB)
-   🐧 Configuration written to /etc/modprobe.d/ttm.conf
-   ○ NOTE: You need to reboot for changes to take effect.
-   Would you like to reboot the system now? (y/n): y
-
-Revert to kernel defaults:
-
-::
-
-   ❯ amd-ttm --clear
-  🐧 Configuration /etc/modprobe.d/ttm.conf removed
-   Would you like to reboot the system now? (y/n): y
-
-.. _operating-system-support:
-
-Operating system support
-========================
-
-The ROCm compatibility tables can be found at the following links:
-
-- `System requirements (Linux) <https://rocm.docs.amd.com/projects/install-on-linux/en/latest/reference/system-requirements.html>`_
-- `System requirements (Windows) <https://rocm.docs.amd.com/projects/install-on-windows/en/latest/reference/system-requirements.html>`_
-
-However, for Strix Halo there are additional kernel version requirements,
-which are described in the following section.
-
-Required kernel version
------------------------
-
-Support for Strix Halo requires specific fixes in the Linux kernel that
-update internal limits in the AMD KFD driver to ensure correct queue
-creation and memory availability checks. Without these updates, GPU
-compute workloads may fail to initialize or behave unpredictably. The
-necessary Linux kernel patches have been merged upstream and are
-included in Linux kernel 6.18.4 and newer releases.
-
-The following commits are required for Strix Halo support:
-
-- `gregkh/linux@7f26af7 <https://github.com/gregkh/linux/commit/7f26af7bf9b76c2c2a1a761aab5803e52be21eea>`_
-- `gregkh/linux@7445db6 <https://github.com/gregkh/linux/commit/7445db6a7d5a0242d8214582b480600b266cba9e>`_
-
-The table below reflects compatibility for **AMD-released pre-built ROCm
-binaries only**. Distributions that ship **native ROCm packaging** may
-provide different support levels.
-
-.. list-table::
-   :header-rows: 0
-   :widths: 10 90
-
-   * - ❌
-     - Unsupported combination
-   * - ⚠️
-     - Unstable / experimental combination
-   * - ✅
-     - Stable and supported combination
-
-.. list-table::
-   :header-rows: 1
-   :widths: 12 14 14 16 14 16 16
-
-   * - ROCm Release
-     - Ubuntu 24.04 HWE
-     - Ubuntu 24.04 OEM (<= 6.14.0-1017)
-     - Ubuntu 24.04 OEM (>= 6.14.0-1018)
-     - Ubuntu 26.04 Generic
-     - Generic Distro < 6.18.4
-     - Generic Distro >= 6.18.4
-
-   * - 7.11.0
-     - ⚠️
-     - ⚠️
-     - ✅
-     - ✅
-     - ⚠️
-     - ✅
-
-   * - 7.10.0
-     - ⚠️
-     - ⚠️
-     - ❌
-     - ❌
-     - ⚠️
-     - ❌
-
-   * - 7.9.0
-     - ⚠️
-     - ⚠️
-     - ❌
-     - ❌
-     - ⚠️
-     - ❌
-
-   * - 7.2.1
-     - ⚠️
-     - ⚠️
-     - ✅
-     - ✅
-     - ⚠️
-     - ✅
-
-   * - 7.2.0
-     - ❌
-     - ✅
-     - ✅
-     - ✅
-     - ❌
-     - ✅
-
-   * - 7.1.x
-     - ⚠️
-     - ⚠️
-     - ❌
-     - ❌
-     - ⚠️
-     - ❌
-
-   * - 6.4.x
-     - ⚠️
-     - ⚠️
-     - ❌
-     - ❌
-     - ⚠️
-     - ❌
-
-The following distributions include the required fixes in their
-native packaging, independent of AMD pre-built binaries:
-
-- Fedora 43
-- Ubuntu 26.04
-- Arch Linux

docs/index.md

@@ -13,10 +13,15 @@ compatibility with industry software frameworks. For more information, see
 [What is ROCm?](./what-is-rocm.rst)
 
 ROCm supports multiple programming languages and programming interfaces such as
-{doc}`HIP (Heterogeneous-Compute Interface for Portability)<hip:index>`, OpenCL,
-and OpenMP, as explained in the [Programming guide](./how-to/programming_guide.rst).
+{doc}`HIP <hip:index>`, OpenCL, and OpenMP, as explained in the [Programming guide](./how-to/programming_guide.rst).
 
-If you're using AMD Radeon GPUs or Ryzen APUs in a workstation setting with a display connected, review {doc}`ROCm on Radeon and Ryzen documentation<radeon:index>`.
+If you're using AMD Radeon™ GPUs or Ryzen™ APUs for graphics workloads, see the {doc}`ROCm on Radeon and Ryzen <radeon:index>` documentation.
+
+```{note}
+The [AMD ROCm Programming Guide](https://rocm-handbook.amd.com/projects/amd-rocm-programming-guide/en/latest/)
+presents key ROCm concepts in a structured, book-style format, a helpful
+starting point for those new to GPU programming.
+```
 
 ROCm documentation is organized into the following categories:
 

docs/reference/env-variables.rst

@@ -120,8 +120,11 @@ documentation.
       - Performance tuning, kernel selection, logging, and debugging for BLAS
         operations.
 
-    * - :doc:`rocSolver <rocsolver:reference/env_variables>`
-      - Control logging of rocSolver.
+    * - :doc:`rocSHMEM <rocshmem:api/env_variables>`
+      - Control the behavior of rocSHMEM.
+
+    * - :doc:`rocSOLVER <rocsolver:reference/env_variables>`
+      - Control logging of rocSOLVER.
 
     * - :doc:`rocSPARSE <rocsparse:reference/env_variables>`
       - Control logging of rocSPARSE.

docs/release/versions.md

@@ -10,6 +10,7 @@
 
 | Version | Release date |
 | ------- | ------------ |
+| [7.2.2](https://rocm.docs.amd.com/en/docs-7.2.2/) | April 14, 2026 |
 | [7.2.1](https://rocm.docs.amd.com/en/docs-7.2.1/) | March 25, 2026 |
 | [7.2.0](https://rocm.docs.amd.com/en/docs-7.2.0/) | January 21, 2026 |
 | [7.1.1](https://rocm.docs.amd.com/en/docs-7.1.1/) | November 26, 2025 |

docs/sphinx/_toc.yml.in

@@ -35,20 +35,8 @@ subtrees:
         title: TensorFlow compatibility
       - file: compatibility/ml-compatibility/jax-compatibility.rst
         title: JAX compatibility
-      - file: compatibility/ml-compatibility/verl-compatibility.rst
-        title: verl compatibility
-      - file: compatibility/ml-compatibility/stanford-megatron-lm-compatibility.rst
-        title: Stanford Megatron-LM compatibility
       - file: compatibility/ml-compatibility/dgl-compatibility.rst
         title: DGL compatibility
-      - file: compatibility/ml-compatibility/megablocks-compatibility.rst
-        title: Megablocks compatibility
-      - file: compatibility/ml-compatibility/ray-compatibility.rst
-        title: Ray compatibility
-      - file: compatibility/ml-compatibility/llama-cpp-compatibility.rst
-        title: llama.cpp compatibility
-      - file: compatibility/ml-compatibility/flashinfer-compatibility.rst
-        title: FlashInfer compatibility
   - file: how-to/build-rocm.rst
     title: Build ROCm from source
 
@@ -77,12 +65,12 @@ subtrees:
             title: Train a model with Primus and Megatron-LM
             entries:
             - file: how-to/rocm-for-ai/training/benchmark-docker/megatron-lm.rst
-              title: Train a model with Megatron-LM
+              title: Train a model with Megatron-LM (legacy)
           - file: how-to/rocm-for-ai/training/benchmark-docker/primus-pytorch.rst
             title: Train a model with Primus and PyTorch
             entries:
             - file: how-to/rocm-for-ai/training/benchmark-docker/pytorch-training.rst
-              title: Train a model with PyTorch
+              title: Train a model with PyTorch (legacy)
           - file: how-to/rocm-for-ai/training/benchmark-docker/jax-maxtext.rst
             title: Train a model with Primus and JAX MaxText
           - file: how-to/rocm-for-ai/training/benchmark-docker/mpt-llm-foundry

docs/sphinx/requirements.txt

@@ -37,7 +37,7 @@ click==8.3.1
     #   sphinx-external-toc
 comm==0.2.3
     # via ipykernel
-cryptography==46.0.5
+cryptography==46.0.7
     # via pyjwt
 debugpy==1.8.19
     # via ipykernel
@@ -156,13 +156,13 @@ pydata-sphinx-theme==0.15.4
     #   sphinx-book-theme
 pygithub==2.8.1
     # via rocm-docs-core
-pygments==2.19.2
+pygments==2.20.0
     # via
     #   accessible-pygments
     #   ipython
     #   pydata-sphinx-theme
     #   sphinx
-pyjwt[crypto]==2.10.1
+pyjwt[crypto]==2.12.0
     # via pygithub
 pynacl==1.6.2
     # via pygithub
@@ -184,7 +184,7 @@ referencing==0.37.0
     # via
     #   jsonschema
     #   jsonschema-specifications
-requests==2.32.5
+requests==2.33.0
     # via
     #   pygithub
     #   sphinx
@@ -261,7 +261,7 @@ tabulate==0.9.0
     # via jupyter-cache
 tomli==2.4.0
     # via sphinx
-tornado==6.5.4
+tornado==6.5.5
     # via
     #   ipykernel
     #   jupyter-client