Fix llvm and lld 2.3 tags for opencl and hcc (#770) (#771)

.github/CODEOWNERS

@@ -1 +0,0 @@
-* @saadrahim @Rmalavally @amd-aakash @zhang2amd @jlgreathouse @samjwu @MathiasMagnus

.github/dependabot.yml

@@ -1,12 +0,0 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
-# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-
-version: 2
-updates:
-  - package-ecosystem: "pip" # See documentation for possible values
-    directory: "/docs/sphinx" # Location of package manifests
-    open-pull-requests-limit: 10
-    schedule:
-      interval: "daily"

.github/workflows/linting.yml

@@ -1,56 +0,0 @@
-name: Linting
-
-on:
-  push:
-    branches: 
-    - develop
-    - main
-  pull_request:
-    branches: 
-    - develop
-    - main
-
-concurrency:
-  group: ${{ github.ref }}-${{ github.workflow }}
-  cancel-in-progress: true
-
-jobs:
-  lint-rest:
-    name: "RestructuredText"
-    runs-on: ubuntu-latest
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v3
-    - name: Install rst-lint
-      run: pip install restructuredtext-lint
-    - name: Lint ResT files
-      run: rst-lint ${{ join(github.workspace, '/docs') }}
-
-  lint-md:
-    name: "Markdown"
-    runs-on: ubuntu-latest
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v3
-    - name: Use markdownlint-cli2
-      uses: DavidAnson/markdownlint-cli2-action@v10.0.1
-      with:
-        globs: '**/*.md'
-
-  spelling:
-    name: "Spelling"
-    runs-on: ubuntu-latest
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v3
-    - name: Fetch config
-      shell: sh
-      run: |
-        curl --silent --show-error --fail --location https://raw.github.com/RadeonOpenCompute/rocm-docs-core/develop/.spellcheck.yaml -O
-        curl --silent --show-error --fail --location https://raw.github.com/RadeonOpenCompute/rocm-docs-core/develop/.wordlist.txt >> .wordlist.txt
-    - name: Run spellcheck
-      uses: rojopolis/spellcheck-github-actions@0.30.0
-    - name: On fail
-      if: failure()
-      run: |
-        echo "Please check for spelling mistakes or add them to '.wordlist.txt' in either the root of this project or in rocm-docs-core."

.gitignore

@@ -1,18 +0,0 @@
-.venv
-.vscode
-build
-
-# documentation artifacts
-_build/
-_images/
-_static/
-_templates/
-_toc.yml
-docBin/
-_doxygen/
-_readthedocs/
-
-# avoid duplicating contributing.md due to conf.py
-docs/contributing.md
-docs/release.md
-docs/CHANGELOG.md

.markdownlint-cli2.yaml

@@ -1,14 +0,0 @@
-config:
-  default: true
-  MD013: false
-  MD026:
-    punctuation: '.,;:!'
-  MD029:
-    style: ordered
-  MD033: false
-  MD034: false
-  MD041: false
-ignores:
-  - CHANGELOG.md
-  - "{,docs/}{RELEASE,release}.md"
-  - tools/autotag/templates/**/*.md

.readthedocs.yaml

@@ -1,21 +0,0 @@
-# Read the Docs configuration file
-# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
-
-version: 2
-
-build:
-   os: ubuntu-22.04
-   tools:
-      python: "3.10"
-   apt_packages:
-     - "doxygen"
-     - "graphviz" # For dot graphs in doxygen
-
-python:
-   install:
-   - requirements: docs/sphinx/requirements.txt
-
-sphinx:
-   configuration: docs/conf.py
-
-formats: []

.wordlist.txt

@@ -1,29 +0,0 @@
-# isv_deployment_win
-ABI
-# gpu_aware_mpi
-DMA
-GDR
-HCA
-MPI
-MVAPICH
-Mellanox's
-NIC
-OFED
-OSU
-OpenFabrics
-PeerDirect
-RDMA
-UCX
-ib_core
-# linear algebra
-LAPACK
-MMA
-backends
-cuSOLVER
-cuSPARSE
-# tuning_guides
-BMC
-DGEMM
-HPCG
-HPL
-IOPM

CONTRIBUTING.md

@@ -1,246 +0,0 @@
-# Contributing to ROCm Docs
-
-AMD values and encourages the ROCm community to contribute to our code and
-documentation. This repository is focused on ROCm documentation and this
-contribution guide describes the recommend method for creating and modifying our
-documentation.
-
-While interacting with ROCm Documentation, we encourage you to be polite and
-respectful in your contributions, content or otherwise. Authors, maintainers of
-these docs act on good intentions and to the best of their knowledge.
-Keep that in mind while you engage. Should you have issues with contributing
-itself, refer to
-[discussions](https://github.com/RadeonOpenCompute/ROCm/discussions) on the
-GitHub repository.
-
-## Supported Formats
-
-Our documentation includes both markdown and rst files. Markdown is encouraged
-over rst due to the lower barrier to participation. GitHub flavored markdown is preferred
-for all submissions as it will render accurately on our GitHub repositories. For existing documentation,
-[MyST](https://myst-parser.readthedocs.io/en/latest/intro.html) markdown
-is used to implement certain features unsupported in GitHub markdown. This is
-not encouraged for new documentation. AMD will transition
-to stricter use of GitHub flavored markdown with a few caveats. ROCm documentation
-also uses [sphinx-design](https://sphinx-design.readthedocs.io/en/latest/index.html)
-in our markdown and rst files. We also will use breathe syntax for doxygen documentation
-in our markdown files. Other design elements for effective HTML rendering of the documents
-may be added to our markdown files. Please see
-[GitHub](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github)'s
-guide on writing and formatting on GitHub as a starting point.
-
-ROCm documentation adds additional requirements to markdown and rst based files
-as follows:
-
-- Level one headers are only used for page titles. There must be only one level
-  1 header per file for both Markdown and Restructured Text.
-- Pass [markdownlint](https://github.com/markdownlint/markdownlint) check via
-  our automated github action on a Pull Request (PR).
-
-## Filenames and folder structure
-
-Please use snake case for file names. Our documentation follows pitchfork for
-folder structure. All documentation is in /docs except for special files like
-the contributing guide in the / folder. All images used in the documentation are
-place in the /docs/data folder.
-
-## How to provide feedback for for ROCm documentation
-
-There are three standard ways to provide feedback for this repository.
-
-### Pull Request
-
-All contributions to ROCm documentation should arrive via the
-[GitHub Flow](https://docs.github.com/en/get-started/quickstart/github-flow)
-targetting the develop branch of the repository. If you are unable to contribute
-via the GitHub Flow, feel free to email us. TODO, confirm email address.
-
-### GitHub Issue
-
-Issues on existing or absent docs can be filed as [GitHub issues
-](https://github.com/RadeonOpenCompute/ROCm/issues).
-
-### Email Feedback
-
-## Language and Style
-
-Adopting Microsoft CPP-Docs guidelines for [Voice and Tone
-](https://github.com/MicrosoftDocs/cpp-docs/blob/main/styleguide/voice-tone.md).
-
-ROCm documentation templates to be made public shortly. ROCm templates dictate
-the recommended structure and flow of the documentation. Guidelines on how to
-integrate figures, equations, and tables are all based off
-[MyST](https://myst-parser.readthedocs.io/en/latest/intro.html).
-
-Font size and selection, page layout, white space control, and other formatting
-details are controlled via rocm-docs-core, sphinx extention. Please raise issues
-in rocm-docs-core for any formatting concerns and changes requested.
-
-## Building Documentation
-
-While contributing, one may build the documentation locally on the command-line
-or rely on Continuous Integration for previewing the resulting HTML pages in a
-browser.
-
-### Command line documentation builds
-
-Python versions known to build documentation:
-
-- 3.8
-
-To build the docs locally using Python Virtual Environment (`venv`), execute the
-following commands from the project root:
-
-```sh
-python3 -mvenv .venv
-# Windows
-.venv/Scripts/python -m pip install -r docs/sphinx/requirements.txt
-.venv/Scripts/python -m sphinx -T -E -b html -d _build/doctrees -D language=en docs _build/html
-# Linux
-.venv/bin/python     -m pip install -r docs/sphinx/requirements.txt
-.venv/bin/python     -m sphinx -T -E -b html -d _build/doctrees -D language=en docs _build/html
-```
-
-Then open up `_build/html/index.html` in your favorite browser.
-
-### Pull Requests documentation builds
-
-When opening a PR to the `develop` branch on GitHub, the page corresponding to
-the PR (`https://github.com/RadeonOpenCompute/ROCm/pull/<pr_number>`) will have
-a summary at the bottom. This requires the user be logged in to GitHub.
-
-- There, click `Show all checks` and `Details` of the Read the Docs pipeline. It
-  will take you to `https://readthedocs.com/projects/advanced-micro-devices-rocm/
-  builds/<some_build_num>/`
-  - The list of commands shown are the exact ones used by CI to produce a render
-    of the documentation.
-- There, click on the small blue link `View docs` (which is not the same as the
-  bigger button with the same text). It will take you to the built HTML site with
-  a URL of the form `https://
-  advanced-micro-devices-demo--<pr_number>.com.readthedocs.build/projects/alpha/en
-  /<pr_number>/`.
-
-### Build the docs using VS Code
-
-One can put together a productive environment to author documentation and also
-test it locally using VS Code with only a handful of extensions. Even though the
-extension landscape of VS Code is ever changing, here is one example setup that
-proved useful at the time of writing. In it, one can change/add content, build a
-new version of the docs using a single VS Code Task (or hotkey), see all errors/
-warnings emitted by Sphinx in the Problems pane and immediately see the
-resulting website show up on a locally serving web server.
-
-#### Configuring VS Code
-
-1. Install the following extensions:
-
-    - Python (ms-python.python)
-    - Live Server (ritwickdey.LiveServer)
-
-2. Add the following entries in `.vscode/settings.json`
-
-    ```json
-    {
-      "liveServer.settings.root": "/.vscode/build/html",
-      "liveServer.settings.wait": 1000,
-      "python.terminal.activateEnvInCurrentTerminal": true
-    }
-    ```
-
-    The settings in order are set for the following reasons:
-    - Sets the root of the output website for live previews. Must be changed
-      alongside the `tasks.json` command.
-    - Tells live server to wait with the update to give time for Sphinx to
-      regenerate site contents and not refresh before all is don. (Empirical value)
-    - Automatic virtual env activation is a nice touch, should you want to build
-      the site from the integrated terminal.
-
-3. Add the following tasks in `.vscode/tasks.json`
-
-    ```json
-    {
-      "version": "2.0.0",
-      "tasks": [
-        {
-          "label": "Build Docs",
-          "type": "process",
-          "windows": {
-            "command": "${workspaceFolder}/.venv/Scripts/python.exe"
-          },
-          "command": "${workspaceFolder}/.venv/bin/python3",
-          "args": [
-            "-m",
-            "sphinx",
-            "-j",
-            "auto",
-            "-T",
-            "-b",
-            "html",
-            "-d",
-            "${workspaceFolder}/.vscode/build/doctrees",
-            "-D",
-            "language=en",
-            "${workspaceFolder}/docs",
-            "${workspaceFolder}/.vscode/build/html"
-          ],
-          "problemMatcher": [
-            {
-              "owner": "sphinx",
-              "fileLocation": "absolute",
-              "pattern": {
-                "regexp": "^(?:.*\\.{3}\\s+)?(\\/[^:]*|[a-zA-Z]:\\\\[^:]*):(\\d+):\\s+(WARNING|ERROR):\\s+(.*)$",
-                "file": 1,
-                "line": 2,
-                "severity": 3,
-                "message": 4
-              },
-            },
-            {
-              "owner": "sphinx",
-              "fileLocation": "absolute",
-              "pattern": {
-                "regexp": "^(?:.*\\.{3}\\s+)?(\\/[^:]*|[a-zA-Z]:\\\\[^:]*):{1,2}\\s+(WARNING|ERROR):\\s+(.*)$",
-                "file": 1,
-                "severity": 2,
-                "message": 3
-              }
-            }
-          ],
-          "group": {
-            "kind": "build",
-            "isDefault": true
-          }
-        },
-      ],
-    }
-    ```
-
-    > (Implementation detail: two problem matchers were needed to be defined,
-    > because VS Code doesn't tolerate some problem information being potentially
-    > absent. While a single regex could match all types of errors, if a capture
-    > group remains empty (the line number doesn't show up in all warning/error
-    > messages) but the `pattern` references said empty capture group, VS Code
-    > discards the message completely.)
-
-4. Configure Python virtual environment (venv)
-
-    - From the Command Palette, run `Python: Create Environment`
-      - Select `venv` environment and the `docs/sphinx/requirements.txt` file.
-      _(Simply pressing enter while hovering over the file from the dropdown is
-      insufficient, one has to select the radio button with the 'Space' key if
-      using the keyboard.)_
-
-5. Build the docs
-
-    - Launch the default build Task using either:
-      - a hotkey _(default is 'Ctrl+Shift+B')_ or
-      - by issuing the `Tasks: Run Build Task` from the Command Palette.
-
-6. Open the live preview
-
-    - Navigate to the output of the site within VS Code, right-click on
-    `.vscode/build/html/index.html` and select `Open with Live Server`. The
-    contents should update on every rebuild without having to refresh the
-    browser.
-
-<!-- markdownlint-restore -->

LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2023 Advanced Micro Devices, Inc. All rights reserved.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

README.md

@@ -1,54 +1,727 @@
-# AMD ROCm™ Platform
+## Are You Ready to ROCK?
+The ROCm Platform brings a rich foundation to advanced computing by seamlessly integrating the CPU and GPU with the goal of solving real-world problems.
+This software enables the high-performance operation of AMD GPUs for computationally oriented tasks in the Linux operating system.
 
-ROCm™ is an open-source stack for GPU computation. ROCm is primarily Open-Source
-Software (OSS) that allows developers the freedom to customize and tailor their
-GPU software for their own needs while collaborating with a community of other
-developers, and helping each other find solutions in an agile, flexible, rapid
-and secure manner.
+### Current ROCm Version: 2.3
 
-ROCm is a collection of drivers, development tools and APIs enabling GPU
-programming from the low-level kernel to end-user applications. ROCm is powered
-by AMD’s Heterogeneous-computing Interface for Portability (HIP), an OSS 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 supports programming models such as OpenMP and OpenCL, and
-includes all the necessary OSS compilers, debuggers and libraries. ROCm is fully
-integrated into ML frameworks such as PyTorch and TensorFlow. ROCm can be
-deployed in many ways, including through the use of containers such as Docker,
-Spack, and your own build from source.
+- [Hardware Support](#hardware-support)
+  * [Supported GPUs](#supported-gpus)
+  * [Supported CPUs](#supported-cpus)
+  * [Not supported or limited support under ROCm](#not-supported-or-limited-support-under-rocm)
+- [New features and enhancements in ROCm 2.3](#new-features-and-enhancements-in-rocm-23)
+- [The latest ROCm platform - ROCm 2.3](#the-latest-rocm-platform---rocm-230)
+  * [Supported Operating Systems](#supported-operating-systems---new-operating-systems-available)
+  * [ROCm support in upstream Linux kernels](#rocm-support-in-upstream-linux-kernels)
+- [Installing from AMD ROCm repositories](#installing-from-amd-rocm-repositories)
+  * [ROCm Binary Package Structure](#rocm-binary-package-structure)
+  * [Ubuntu Support - installing from a Debian repository](#ubuntu-support---installing-from-a-debian-repository)
+  * [CentOS/RHEL 7 (7.4, 7.5, 7.6) Support](#centosrhel-7-74-75-76-support)
+- [Known issues / workarounds](#known-issues--workarounds)
+- [Closed source components](#closed-source-components)
+- [Getting ROCm source code](#getting-rocm-source-code)
+  * [Installing repo](#installing-repo)
+  * [Downloading the ROCm source code](#downloading-the-rocm-source-code)
+  * [Building the ROCm source code](#building-the-rocm-source-code)
+- [Deprecation Notice](#deprecation-notice)
+- [Final notes](#final-notes)
 
-ROCm’s goal is to allow our users to maximize their GPU hardware investment.
-ROCm is designed to help develop, test and deploy GPU accelerated HPC, AI,
-scientific computing, CAD, and other applications in a free, open-source,
-integrated and secure software ecosystem.
+### Hardware Support
+ROCm is focused on using AMD GPUs to accelerate computational tasks such as machine learning, engineering workloads, and scientific computing.
+In order to focus our development efforts on these domains of interest, ROCm supports a targeted set of hardware configurations which are detailed further in this section.
 
-This repository contains the manifest file for ROCm™ releases, changelogs, and
-release information. The file default.xml contains information for all
-repositories and the associated commit used to build the current ROCm release.
+#### Supported GPUs
+Because the ROCm Platform has a focus on particular computational domains, we offer official support for a selection of AMD GPUs that are designed to offer good performance and price in these domains.
 
-The default.xml file uses the repo Manifest format.
+ROCm officially supports AMD GPUs that use following chips:
 
-The develop branch of this repository contains content for the next
-ROCm release.
+  * GFX8 GPUs
+    * "Fiji" chips, such as on the AMD Radeon R9 Fury X and Radeon Instinct MI8
+    * "Polaris 10" chips, such as on the AMD Radeon RX 580 and Radeon Instinct MI6
+    * "Polaris 11" chips, such as on the AMD Radeon RX 570 and Radeon Pro WX 4100
+    * "Polaris 12" chips, such as on the AMD Radeon RX 550 and Radeon RX 540
+  * GFX9 GPUs
+    * "Vega 10" chips, such as on the AMD Radeon RX Vega 64 and Radeon Instinct MI25
+    * "Vega 7nm" chips, such as the AMD Radeon VII
 
-## ROCm Documentation
+ROCm is a collection of software ranging from drivers and runtimes to libraries and developer tools.
+Some of this software may work with more GPUs than the "officially supported" list above, though AMD does not make any official claims of support for these devices on the ROCm software platform.
+The following list of GPUs are enabled in the ROCm software, though full support is not guaranteed:
 
-ROCm Documentation is available online at
-[rocm.docs.amd.com](https://rocm.docs.amd.com). Source code for the documenation
-is located in the docs folder of most repositories that are part of ROCm.
+  * GFX7 GPUs
+    * "Hawaii" chips, such as the AMD Radeon R9 390X and FirePro W9100
 
-### How to build documentation via Sphinx
+As described in the next section, GFX8 GPUs require PCI Express 3.0 (PCIe 3.0) with support for PCIe atomics. This requires both CPU and motherboard support. GFX9 GPUs, by default, also require PCIe 3.0 with support for PCIe atomics, but they can operate in most cases without this capability.
 
-```bash
-cd docs
+At this time, the integrated GPUs in AMD APUs are not officially supported targets for ROCm.
+As descried [below](#limited-support), "Carrizo", "Bristol Ridge", and "Raven Ridge" APUs are enabled in our upstream drivers and the ROCm OpenCL runtime.
+However, they are not enabled in our HCC or HIP runtimes, and may not work due to motherboard or OEM hardware limitations.
+As such, they are not yet officially supported targets for ROCm.
 
-pip3 install -r sphinx/requirements.txt
+For a more detailed list of hardware support, please see [the following documentation](https://rocm.github.io/hardware.html).
 
-python3 -m sphinx -T -E -b html -d _build/doctrees -D language=en . _build/html
+#### Supported CPUs
+As described above, GFX8 GPUs require PCIe 3.0 with PCIe atomics in order to run ROCm.
+In particular, the CPU and every active PCIe point between the CPU and GPU require support for PCIe 3.0 and PCIe atomics.
+The CPU root must indicate PCIe AtomicOp Completion capabilities and any intermediate switch must indicate PCIe AtomicOp Routing capabilities.
+
+Current CPUs which support PCIe Gen3 + PCIe Atomics are:
+
+  * AMD Ryzen CPUs;
+  * The CPUs in AMD Ryzen APUs;
+  * AMD Ryzen Threadripper CPUs
+  * AMD EPYC CPUs;  
+  * Intel Xeon E7 v3 or newer CPUs;
+  * Intel Xeon E5 v3 or newer CPUs; 
+  * Intel Xeon E3 v3 or newer CPUs;
+  * Intel Core i7 v4, Core i5 v4, Core i3 v4 or newer CPUs (i.e. Haswell family or newer).
+  * Some Ivy Bridge-E systems
+
+Beginning with ROCm 1.8, GFX9 GPUs (such as Vega 10) no longer require PCIe atomics.
+We have similarly opened up more options for number of PCIe lanes.
+GFX9 GPUs can now be run on CPUs without PCIe atomics and on older PCIe generations, such as PCIe 2.0.
+This is not supported on GPUs below GFX9, e.g. GFX8 cards in the Fiji and Polaris families.
+
+If you are using any PCIe switches in your system, please note that PCIe Atomics are only supported on some switches, such as Broadcom PLX.
+When you install your GPUs, make sure you install them in a PCIe 3.0 x16, x8, x4, or x1 slot attached either directly to the CPU's Root I/O controller or via a PCIe switch directly attached to the CPU's Root I/O controller.
+
+In our experience, many issues stem from trying to use consumer motherboards which provide physical x16 connectors that are electrically connected as e.g. PCIe 2.0 x4, PCIe slots connected via the Southbridge PCIe I/O controller, or PCIe slots connected through a PCIe switch that does
+not support PCIe atomics.
+
+If you attempt to run ROCm on a system without proper PCIe atomic support, you may see an error in the kernel log (`dmesg`):
+```
+kfd: skipped device 1002:7300, PCI rejects atomics
 ```
 
-## Older ROCm™ Releases
+Experimental support for our Hawaii (GFX7) GPUs (Radeon R9 290, R9 390, FirePro W9100, S9150, S9170)
+does not require or take advantage of PCIe Atomics. However, we still recommend that you use a CPU
+from the list provided above for compatibility purposes.
 
-For release information for older ROCm™ releases, refer to
-[CHANGELOG](./CHANGELOG.md).
+#### Not supported or limited support under ROCm 
+##### Limited support 
+
+* ROCm 2.3.x should support PCIe 2.0 enabled CPUs such as the AMD Opteron, Phenom, Phenom II, Athlon, Athlon X2, Athlon II and older Intel Xeon and Intel Core Architecture and Pentium CPUs. However, we have done very limited testing on these configurations, since our test farm has been catering to CPUs listed above. This is where we need community support. _If you find problems on such setups, please report these issues_.
+* Thunderbolt 1, 2, and 3 enabled breakout boxes should now be able to work with ROCm. Thunderbolt 1 and 2 are PCIe 2.0 based, and thus are only supported with GPUs that do not require PCIe 3.0 atomics (e.g. Vega 10). However, we have done no testing on this configuration and would need community support due to limited access to this type of equipment.
+* AMD "Carrizo" and "Bristol Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes.
+  * As of ROCm 2.1, "Carrizo" and "Bristol Ridge" require the use of upstream kernel drivers.
+  * In addition, various "Carrizo" and "Bristol Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
+  * Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.
+* AMD "Raven Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes.
+  * As of ROCm 2.1, "Raven Ridge" requires the use of upstream kernel drivers.
+  * In addition, various "Raven Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
+  * Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.
+  
+##### Not supported 
+
+* "Tonga", "Iceland", "Vega M", and "Vega 12" GPUs are not supported in ROCm 2.3.x
+* We do not support GFX8-class GPUs (Fiji, Polaris, etc.) on CPUs that do not have PCIe 3.0 with PCIe atomics.
+  * As such, we do not support AMD Carrizo and Kaveri APUs as hosts for such GPUs.
+  * Thunderbolt 1 and 2 enabled GPUs are not supported by GFX8 GPUs on ROCm. Thunderbolt 1 & 2 are based on PCIe 2.0.
+
+### New features and enhancements in ROCm 2.3
+
+#### Mem usage per GPU
+Per GPU memory usage is added to rocm-smi.
+Display information regarding used/total bytes for VRAM, visible VRAM and GTT, via the --showmeminfo flag
+
+#### MIVisionX, v1.1 - ONNX	
+ONNX parser changes to adjust to new file formats
+
+#### MIGraphX, v0.2
+MIGraphX 0.2 supports the following new features:
+* New Python API
+* Support for additional ONNX operators and fixes that now enable a large set of Imagenet models
+* Support for RNN Operators
+* Support for multi-stream Execution
+* [Experimental] Support for Tensorflow frozen protobuf files
+
+See: [Getting-started:-using-the-new-features-of-MIGraphX-0.2](https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/wiki/Getting-started:-using-the-new-features-of-MIGraphX-0.2) for more details
+
+#### MIOpen, v1.8 - 3d convolutions and int8
+* This release contains full 3-D convolution support and int8 support for inference.
+* Additionally, there are major updates in the performance database for major models including those found in Torchvision.
+
+See: [MIOpen releases](https://github.com/ROCmSoftwarePlatform/MIOpen/releases)
+
+#### Caffe2 -  mGPU support	
+Multi-gpu support is enabled for Caffe2.
+
+#### rocTracer library, ROCm tracing API for collecting runtimes API and asynchronous GPU activity traces
+HIP/HCC domains support is introduced in rocTracer library.
+
+#### BLAS -  Int8 GEMM performance, Int8 functional and performance	
+Introduces support and performance optimizations for Int8 GEMM, implements TRSV support, and includes improvements and optimizations with Tensile.
+
+#### Prioritized L1/L2/L3 BLAS (functional)	
+Functional implementation of BLAS L1/L2/L3 functions
+
+#### BLAS - tensile optimization
+Improvements and optimizations with tensile
+
+#### MIOpen Int8 support
+Support for int8
+
+Features and enhancements introduced in previous versions of ROCm can be found in [version_history.md](version_history.md)
+
+### The latest ROCm platform - ROCm 2.3
+
+The latest supported version of the drivers, tools, libraries and source code for the ROCm platform have been released and are available from the following GitHub repositories:
+
+* ROCm Core Components
+  - [ROCk Kernel Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-2.3.0)
+  - [ROCr Runtime](https://github.com/RadeonOpenCompute/ROCR-Runtime/tree/84443a1)
+  - [ROCt Thunk Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-2.3.0)
+* ROCm Support Software
+  - [ROCm SMI](https://github.com/RadeonOpenCompute/ROC-smi/tree/roc-2.3.0)
+  - [ROCm cmake](https://github.com/RadeonOpenCompute/rocm-cmake/tree/ac45c6e2)
+  - [rocminfo](https://github.com/RadeonOpenCompute/rocminfo/tree/1bb0ccc7)
+  - [ROCm Bandwidth Test](https://github.com/RadeonOpenCompute/rocm_bandwidth_test/tree/roc-2.3.0)
+* ROCm Development Tools
+  - [HCC compiler](https://github.com/RadeonOpenCompute/hcc/tree/roc-2.3.0)
+  - [HIP](https://github.com/ROCm-Developer-Tools/HIP/tree/roc-2.3.0)
+  - [ROCm Device Libraries](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-2.3.0)
+  - ROCm OpenCL, which is created from the following components:
+    - [ROCm OpenCL Runtime](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/tree/roc-2.3.0)
+    - [ROCm OpenCL Driver](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Driver/tree/roc-2.3.0)
+    - The ROCm OpenCL compiler, which is created from the following components:
+      - [ROCm LLVM OCL](http://github.com/RadeonOpenCompute/llvm/tree/roc-ocl-2.3.0)
+      - [ROCm LLVM HCC](http://github.com/RadeonOpenCompute/llvm/tree/roc-hcc-2.3.0)
+      - [ROCm Clang](http://github.com/RadeonOpenCompute/clang/tree/roc-2.3.0)
+      - [ROCm lld OCL](http://github.com/RadeonOpenCompute/lld/tree/roc-ocl-2.3.0)
+      - [ROCm lld HCC](http://github.com/RadeonOpenCompute/lld/tree/roc-hcc-2.3.0)
+      - [ROCm Device Libraries](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-2.3.0)
+  - [ROCM Clang-OCL Kernel Compiler](https://github.com/RadeonOpenCompute/clang-ocl/tree/roc-2.3.0)
+  - [Asynchronous Task and Memory Interface (ATMI)](https://github.com/RadeonOpenCompute/atmi/tree/4dd14ad8)
+  - [ROCr Debug Agent](https://github.com/ROCm-Developer-Tools/rocr_debug_agent/tree/roc-2.3.0)
+  - [ROCm Code Object Manager](https://github.com/RadeonOpenCompute/ROCm-CompilerSupport/tree/roc-2.3.0)
+  - [ROC Profiler](https://github.com/ROCm-Developer-Tools/rocprofiler/tree/roc-2.3.x)
+  - [ROC Tracer](https://github.com/ROCm-Developer-Tools/roctracer/tree/roc-2.3.x)
+  - [Radeon Compute Profiler](https://github.com/GPUOpen-Tools/RCP/tree/a31fe682)
+  - Example Applications:
+    - [HCC Examples](https://github.com/ROCm-Developer-Tools/HCC-Example-Application/tree/ffd65333)
+    - [HIP Examples](https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/roc-2.3.0)
+* ROCm Libraries
+  - [rocBLAS](https://github.com/ROCmSoftwarePlatform/rocBLAS/tree/master-rocm-2.3)
+  - [hipBLAS](https://github.com/ROCmSoftwarePlatform/hipBLAS/tree/master-rocm-2.3)
+  - [rocFFT](https://github.com/ROCmSoftwarePlatform/rocFFT/tree/master-rocm-2.3)
+  - [rocRAND](https://github.com/ROCmSoftwarePlatform/rocRAND/tree/master-rocm-2.3)
+  - [rocSPARSE](https://github.com/ROCmSoftwarePlatform/rocSPARSE/tree/master-rocm-2.3)
+  - [hipSPARSE](https://github.com/ROCmSoftwarePlatform/hipSPARSE/tree/master-rocm-2.3)
+  - [rocALUTION](https://github.com/ROCmSoftwarePlatform/rocALUTION/tree/master-rocm-2.3)
+  - [MIOpenGEMM](https://github.com/ROCmSoftwarePlatform/MIOpenGEMM/tree/9547fb9e)
+  - [MIOpen](https://github.com/ROCmSoftwarePlatform/MIOpen/tree/roc-2.3.0)
+  - [HIP Thrust](https://github.com/ROCmSoftwarePlatform/Thrust/tree/master-rocm-2.3)
+  - [ROCm SMI Lib](https://github.com/RadeonOpenCompute/rocm_smi_lib/tree/roc-2.3.0)
+  - [RCCL](https://github.com/ROCmSoftwarePlatform/rccl/tree/master-rocm-2.3)
+  - [MIVisionX](https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/tree/8ec8732)
+  - [CUB HIP](https://github.com/ROCmSoftwarePlatform/cub-hip/tree/hip_port_1.7.4)
+
+#### Supported Operating Systems - New operating systems available
+
+The ROCm 2.2.x platform supports the following operating systems:
+
+ * Ubuntu 16.04.x, 18.04.1 and 18.04.2 (Version 16.04.3 and newer or kernels 4.13-4.15)
+ * CentOS 7.4, 7.5, and 7.6 (Using devtoolset-7 runtime support)
+ * RHEL 7.4, 7.5, and 7.6 (Using devtoolset-7 runtime support)
+
+#### ROCm support in upstream Linux kernels
+
+As of ROCm 1.9.0, the ROCm user-level software is compatible with the AMD drivers in certain upstream Linux kernels.
+As such, users have the option of either using the ROCK kernel driver that are part of AMD's ROCm repositories or using the upstream driver and only installing ROCm user-level utilities from AMD's ROCm repositories.
+
+These releases of the upstream Linux kernel support the following GPUs in ROCm:
+ * 4.17: Fiji, Polaris 10, Polaris 11
+ * 4.18: Fiji, Polaris 10, Polaris 11, Vega10
+ * 4.20: Fiji, Polaris 10, Polaris 11, Vega10, Vega 7nm
+
+The upstream driver may be useful for running ROCm software on systems that are not compatible with the kernel driver available in AMD's repositories.
+For users that have the option of using either AMD's or the upstreamed driver, there are various tradeoffs to take into consideration:
+
+|   | Using AMD's `rock-dkms` package | Using the upstream kernel driver |
+| ---- | ------------------------------------------------------------| ----- |
+| Pros | More GPU features, and they are enabled earlier | Includes the latest Linux kernel features |
+|      | Tested by AMD on supported distributions | May work on other distributions and with custom kernels |
+|      | Supported GPUs enabled regardless of kernel version | |
+|      | Includes the latest GPU firmware | |
+| Cons | May not work on all Linux distributions or versions | Features and hardware support varies depending on kernel version |
+|      | Not currently supported on kernels newer than 4.18 | Limits GPU's usage of system memory to 3/8 of system memory |
+|      |   | IPC and RDMA capabilities are not yet enabled |
+|      |   | Not tested by AMD to the same level as `rock-dkms` package |
+|      |   | Does not include most up-to-date firmware |
+
+
+### Installing from AMD ROCm repositories
+
+AMD hosts both [Debian](http://repo.radeon.com/rocm/apt/debian/) and [RPM](http://repo.radeon.com/rocm/yum/rpm/) repositories for the ROCm 2.3.x packages at this time.
+
+The packages in the Debian repository have been signed to ensure package integrity.
+
+#### ROCm Binary Package Structure
+
+ROCm is a collection of software ranging from drivers and runtimes to libraries and developer tools.
+In AMD's package distributions, these software projects are provided as a separate packages.
+This allows users to install only the packages they need, if they do not wish to install all of ROCm.
+These packages will install most of the ROCm software into `/opt/rocm/` by default.
+
+The packages for each of the major ROCm components are:
+
+* ROCm Core Components
+  - ROCk Kernel Driver: `rock-dkms`
+  - ROCr Runtime: `hsa-rocr-dev`, `hsa-ext-rocr-dev`
+  - ROCt Thunk Interface: `hsakmt-roct`, `hsakmt-roct-dev`
+* ROCm Support Software
+  - ROCm SMI: `rocm-smi`
+  - ROCm cmake: `rocm-cmake`
+  - rocminfo: `rocminfo`
+  - ROCm Bandwidth Test: `rocm_bandwidth_test`
+* ROCm Development Tools
+  - HCC compiler: `hcc`
+  - HIP: `hip_base`, `hip_doc`, `hip_hcc`, `hip_samples`
+  - ROCm Device Libraries: `rocm-device-libs`
+  - ROCm OpenCL: `rocm-opencl`, `rocm-opencl-devel` (on RHEL/CentOS), `rocm-opencl-dev` (on Ubuntu)
+  - ROCM Clang-OCL Kernel Compiler: `rocm-clang-ocl`
+  - Asynchronous Task and Memory Interface (ATMI): `atmi`
+  - ROCr Debug Agent: `rocr_debug_agent`
+  - ROCm Code Object Manager: `comgr`
+  - ROC Profiler: `rocprofiler-dev`
+  - ROC Tracer: `roctracer-dev`
+  - Radeon Compute Profiler: `rocm-profiler`
+* ROCm Libraries
+  - rocBLAS: `rocblas`
+  - hipBLAS: `hipblas`
+  - rocFFT: `rocfft`
+  - rocRAND: `rocrand`
+  - rocSPARSE: `rocsparse`
+  - hipSPARSE: `hipsparse`
+  - rocALUTION: `rocalution:`
+  - MIOpenGEMM: `miopengemm`
+  - MIOpen: `MIOpen-HIP` (for the HIP version), `MIOpen-OpenCL` (for the OpenCL version)
+  - HIP Thrust: `thrust` (on RHEL/CentOS), `hip-thrust` (on Ubuntu)
+  - ROCm SMI Lib: `rocm_smi_lib64`
+  - RCCL: `rccl`
+  - MIVisionX: `mivisionx`
+  - CUB HIP: `cub-hip`
+
+To make it easier to install ROCm, the AMD binary repos provide a number of meta-packages that will automatically install multiple other packages.
+For example, `rocm-dkms` is the primary meta-package that is used to install most of the base technology needed for ROCm to operate.
+It will install the `rock-dkms` kernel driver, and another meta-package (`rocm-dev`) which installs most of the user-land ROCm core components, support software, and development tools.
+
+The `rocm-utils` meta-package will install useful utilities that, while not required for ROCm to operate, may still be beneficial to have.
+Finally, the `rocm-libs` meta-package will install some (but not all) of the libraries that are part of ROCm.
+
+The chain of software installed by these meta-packages is illustrated below
+
+```
+rocm-dkms
+ |-- rock-dkms
+ \-- rocm-dev
+      |--hsa-rocr-dev
+      |--hsa-ext-rocr-dev
+      |--rocm-device-libs
+      |--rocm-utils
+          |-- rocminfo
+          |-- rocm-cmake
+          \-- rocm-clang-ocl # This will cause OpenCL to be installed
+      |--hcc
+      |--hip_base
+      |--hip_doc
+      |--hip_hcc
+      |--hip_samples
+      |--rocm-smi
+      |--hsakmt-roct
+      |--hsakmt-roct-dev
+      |--hsa-amd-aqlprofile
+      |--comgr
+      \--rocr_debug_agent
+
+rocm-libs
+ |-- rocblas
+ |-- rocfft
+ |-- rocrand
+ \-- hipblas
+```
+
+These meta-packages are not required but may be useful to make it easier to install ROCm on most systems.
+Some users may want to skip certain packages. For instance, a user that wants to use the upstream kernel drivers (rather than those supplied by AMD) may want to skip the `rocm-dkms` and `rock-dkms` packages, and instead directly install `rocm-dev`.
+
+Similarly, a user that only wants to install OpenCL support instead of HCC and HIP may want to skip the `rocm-dkms` and `rocm-dev` packages.
+Instead, they could directly install `rock-dkms`, `rocm-opencl`, and `rocm-opencl-dev` and their dependencies.
+
+#### Ubuntu Support - installing from a Debian repository
+
+The following directions show how to install ROCm on supported Debian-based systems such as Ubuntu 18.04.
+These directions may not work as written on unsupported Debian-based distributions.
+For example, newer versions of Ubuntu may not be compatible with the `rock-dkms` kernel driver.
+As such, users may want to skip the `rocm-dkms` and `rock-dkms` packages, as described [above](#rocm-binary-package-structure), and instead [use the upstream kernel driver](#using-debian-based-rocm-with-upstream-kernel-drivers).
+
+##### First make sure your system is up to date 
+
+```shell
+sudo apt update
+sudo apt dist-upgrade
+sudo apt install libnuma-dev
+sudo reboot
+```
+
+##### Add the ROCm apt repository
+
+For Debian-based systems like Ubuntu, configure the Debian ROCm repository as
+follows:
+
+```shell
+wget -qO - http://repo.radeon.com/rocm/apt/debian/rocm.gpg.key | sudo apt-key add -
+echo 'deb [arch=amd64] http://repo.radeon.com/rocm/apt/debian/ xenial main' | sudo tee /etc/apt/sources.list.d/rocm.list
+```
+The gpg key might change, so it may need to be updated when installing a new release. 
+If the key signature verification is failed while update, please re-add the key from 
+ROCm apt repository. The current rocm.gpg.key is not available in a standard key ring 
+distribution, but has the following sha1sum hash:
+
+`f7f8147431c75e505c58a6f3a3548510869357a6  rocm.gpg.key`
+
+##### Install
+
+Next, update the apt repository list and install the `rocm-dkms` meta-package:
+
+```shell
+sudo apt update
+sudo apt install rocm-dkms
+```
+
+##### Next set your permissions 
+
+Users will need to be in the `video` group in order to have access to the GPU.
+As such, you should ensure that your user account is a member of the `video` group prior to using ROCm.
+You can find which groups you are a member of with the following command:
+
+```shell
+groups
+```
+
+To add yourself to the video group you will need the sudo password and can use the following command:
+
+```shell
+sudo usermod -a -G video $LOGNAME 
+```
+
+You may want to ensure that any future users you add to your system are put into the "video" group by default. To do that, you can run the following commands:
+
+```shell
+echo 'ADD_EXTRA_GROUPS=1' | sudo tee -a /etc/adduser.conf
+echo 'EXTRA_GROUPS=video' | sudo tee -a /etc/adduser.conf
+```
+
+Once complete, reboot your system.
+
+##### Test basic ROCm installation
+
+After rebooting the system run the following commands to verify that the ROCm installation was successful. If you see your GPUs listed by both of these commands, you should be ready to go!
+
+```shell
+/opt/rocm/bin/rocminfo 
+/opt/rocm/opencl/bin/x86_64/clinfo 
+```
+
+Note that, to make running ROCm programs easier, you may wish to put the ROCm binaries in your PATH.
+
+```shell
+echo 'export PATH=$PATH:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin/x86_64' | sudo tee -a /etc/profile.d/rocm.sh
+```
+
+If you have an [install issue](https://rocm.github.io/install_issues.html) please read this FAQ.
+
+##### Performing an OpenCL-only Installation of ROCm
+
+Some users may want to install a subset of the full ROCm installation.
+In particular, if you are trying to install on a system with a limited amount of storage space, or which will only run a small collection of known applications, you may want to install only the packages that are required to run OpenCL applications.
+To do that, you can run the following installation command **instead** of the command to install `rocm-dkms`.
+
+```shell
+sudo apt-get install dkms rock-dkms rocm-opencl-dev
+```
+
+##### How to uninstall from Ubuntu 16.04 or Ubuntu 18.04
+
+To uninstall the ROCm packages installed in the above directions, you can execute;
+
+```shell
+sudo apt autoremove rocm-dkms rocm-dev rocm-utils
+```
+
+##### Installing development packages for cross compilation
+
+It is often useful to develop and test on different systems.
+For example, some development or build systems may not have an AMD GPU installed.
+In this scenario, you may prefer to avoid installing the ROCK kernel driver to your development system.
+
+In this case, install the development subset of packages:
+
+```shell
+sudo apt update
+sudo apt install rocm-dev
+```
+>**Note:** To execute ROCm enabled apps you will require a system with the full
+>ROCm driver stack installed
+
+##### Using Debian-based ROCm with upstream kernel drivers
+
+As described in [the above section about upstream Linux kernel support](#rocm-support-in-upstream-linux-kernels), users may want to try installing ROCm user-level software without installing AMD's custom ROCK kernel driver.
+Users who do want to use upstream kernels can run the following commands instead of installing `rocm-dkms`
+
+```shell
+sudo apt update
+sudo apt install rocm-dev
+echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"' | sudo tee /etc/udev/rules.d/70-kfd.rules
+```
+
+#### CentOS/RHEL 7 (7.4, 7.5, 7.6) Support
+
+The following directions show how to install ROCm on supported RPM-based systems such as CentOS 7.6.
+These directions may not work as written on unsupported RPM-based distributions.
+For example, Fedora may work but may not be compatible with the `rock-dkms` kernel driver.
+As such, users may want to skip the `rocm-dkms` and `rock-dkms` packages, as described [above](#rocm-binary-package-structure), and instead [use the upstream kernel driver](#using-rpm-based-rocm-with-upstream-kernel-drivers).
+
+Support for CentOS/RHEL 7 was added in ROCm 1.8, but ROCm requires a special 
+runtime environment provided by the RHEL Software Collections and additional
+dkms support packages to properly install and run.
+
+##### Preparing RHEL 7 (7.4, 7.5, 7.6) for installation
+
+RHEL is a subscription-based operating system, and you must enable several external
+repositories to enable installation of the devtoolset-7 environment and the DKMS
+support files. These steps are not required for CentOS.
+
+First, the subscription for RHEL must be enabled and attached to a pool id. Please
+see Obtaining an RHEL image and license page for instructions on registering your
+system with the RHEL subscription server and attaching to a pool id.
+
+
+Second, enable the following repositories:
+
+```shell
+sudo subscription-manager repos --enable rhel-server-rhscl-7-rpms
+sudo subscription-manager repos --enable rhel-7-server-optional-rpms
+sudo subscription-manager repos --enable rhel-7-server-extras-rpms
+```
+
+Third, enable additional repositories by downloading and installing the epel-release-latest-7 repository RPM:
+
+```shell
+sudo rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
+```
+
+##### Install and setup Devtoolset-7
+
+To setup the Devtoolset-7 environment, follow the instructions on this page:
+
+https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
+
+Note that devtoolset-7 is a Software Collections package, and it is not supported by AMD.
+
+##### Prepare CentOS/RHEL (7.4, 7.5, 7.6) for DKMS Install
+
+Installing kernel drivers on CentOS/RHEL 7.4/7.5/7.6 requires dkms tool being installed:
+
+```shell
+sudo yum install -y epel-release
+sudo yum install -y dkms kernel-headers-`uname -r` kernel-devel-`uname -r`
+```
+
+##### Installing ROCm on the system
+
+It is recommended to [remove previous ROCm installations](https://github.com/RadeonOpenCompute/ROCm#how-to-uninstall-rocm-from-centosrhel-74-75-and-76) before installing the latest version to ensure a smooth installation.
+
+At this point ROCm can be installed on the target system. Create a /etc/yum.repos.d/rocm.repo file with the following contents:
+
+```shell
+[ROCm]
+name=ROCm
+baseurl=http://repo.radeon.com/rocm/yum/rpm
+enabled=1
+gpgcheck=0
+```
+
+The repo's URL should point to the location of the repositories repodata database. Install ROCm components using these commands:
+
+```shell
+sudo yum install rocm-dkms
+```
+
+The rock-dkms component should be installed and the `/dev/kfd` device should be available on reboot.
+
+##### Set up permissions
+
+Ensure that your user account is a member of the "video" or "wheel" group prior to using the ROCm driver.
+You can find which groups you are a member of with the following command:
+
+```shell
+groups
+```
+
+To add yourself to the video (or wheel) group you will need the sudo password and can use the
+following command:
+
+```shell
+sudo usermod -a -G video $LOGNAME 
+```
+
+You may want to ensure that any future users you add to your system are put into the "video" group by default. To do that, you can run the following commands:
+
+```shell
+echo 'ADD_EXTRA_GROUPS=1' | sudo tee -a /etc/adduser.conf
+echo 'EXTRA_GROUPS=video' | sudo tee -a /etc/adduser.conf
+```
+
+Current release supports CentOS/RHEL 7.4, 7.5, 7.6. If users want to update the OS version, they should completely remove ROCm packages before updating to the latest version of the OS, to avoid DKMS related issues.
+
+Once complete, reboot your system.
+
+###### Test basic ROCm installation
+
+After rebooting the system run the following commands to verify that the ROCm installation was successful. If you see your GPUs listed by both of these commands, you should be ready to go!
+
+```shell
+/opt/rocm/bin/rocminfo
+/opt/rocm/opencl/bin/x86_64/clinfo
+```
+
+Note that, to make running ROCm programs easier, you may wish to put the ROCm binaries in your PATH.
+
+```shell
+echo 'export PATH=$PATH:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin/x86_64' | sudo tee -a /etc/profile.d/rocm.sh
+```
+
+If you have an [install issue](https://rocm.github.io/install_issues.html) please read this FAQ.
+
+###### Performing an OpenCL-only Installation of ROCm
+
+Some users may want to install a subset of the full ROCm installation.
+In particular, if you are trying to install on a system with a limited amount of storage space, or which will only run a small collection of known applications, you may want to install only the packages that are required to run OpenCL applications.
+To do that, you can run the following installation command **instead** of the command to install `rocm-dkms`.
+
+```shell
+sudo yum install rock-dkms rocm-opencl-devel
+```
+
+##### Compiling applications using HCC, HIP, and other ROCm software
+
+To compile applications or samples, please use gcc-7.2 provided by the devtoolset-7 environment.
+To do this, compile all applications after running this command: 
+
+```shell
+scl enable devtoolset-7 bash
+```
+##### How to uninstall ROCm from CentOS/RHEL 7.4, 7.5 and 7.6
+
+To uninstall the ROCm packages installed by the above directions, you can execute:
+
+```shell
+sudo yum autoremove rocm-dkms rock-dkms
+```
+
+##### Installing development packages for cross compilation
+
+It is often useful to develop and test on different systems.
+For example, some development or build systems may not have an AMD GPU installed.
+In this scenario, you may prefer to avoid installing the ROCK kernel driver to your development system.
+
+In this case, install the development subset of packages:
+
+```shell
+sudo yum install rocm-dev
+```
+>**Note:** To execute ROCm enabled apps you will require a system with the full
+>ROCm driver stack installed
+
+##### Using ROCm with upstream kernel drivers
+
+As described in [the above section about upstream Linux kernel support](#rocm-support-in-upstream-linux-kernels), use
+rs may want to try installing ROCm user-level software without installing AMD's custom ROCK kernel driver.
+Users who do want to use upstream kernels can run the following commands instead of installing `rocm-dkms`
+
+```shell
+sudo yum install rocm-dev
+echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"' | sudo tee /etc/udev/rules.d/70-kfd.rules
+```
+
+### Known issues / workarounds
+
+#### Rocprim
+"Memory access fault" observed with rocprim.hip.device.scan
+#### HPL
+HPL fails to run in higher problem size (85000 Ns)
+#### Resnet50
+Multi-GPU resnet50 training using the caffe2 framework will cause a hardhang with a console message:
+kfd2kgd: amdgpu_amdkfd_restore_userptr_worker: Failed to resume KFD
+#### Caffe2
+Caffe2 images/sec drops 40% when 4 processes simultaneously run it, each using one GPU 
+#### Thrust
+functions zip_iterator.out and copy.out are not working as expected
+thrust exclusive_scan produces incorrect results when running on thrust device
+#### Tensor flow
+observed memory access fault while running SAGAN tensor flow model in Polaris based ASIC
+
+### Closed source components
+
+The ROCm platform relies on a few closed source components to provide functionality
+such as HSA image support. These components are only available through the ROCm
+repositories, and they will either be deprecated or become open source components in the
+future. These components are made available in the following packages:
+
+*  hsa-ext-rocr-dev
+
+### Getting ROCm source code
+
+ROCm is built from open source software.
+As such, it is possible to make modifications to the various components of ROCm by downloading the source code, making modifications to it, and rebuilding the components.
+The source code for ROCm components can be cloned from each of the GitHub repositories using git.
+In order to make it easier to download the correct versions of each of these tools, this ROCm repository contains a [repo](https://gerrit.googlesource.com/git-repo/) manifest file, [default.xml](default.xml).
+Interested users can thus use this manifest file to download the source code for all of the ROCm software.
+
+#### Installing repo
+
+Google's repo tool allows you to manage multiple git repositories simultaneously.
+You can install it by executing the following example commands:
+
+```shell
+mkdir -p ~/bin/
+curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
+chmod a+x ~/bin/repo
+```
+Note that you can choose a different folder to install repo into if you desire. `~/bin/` is simply used as an example.
+
+#### Downloading the ROCm source code
+
+The following example shows how to use the `repo` binary downloaded above to download all of the ROCm source code.
+If you chose a directory other than `~/bin/` to install `repo`, you should use that directory below.
+
+```shell
+mkdir -p ~/ROCm/
+cd ~/ROCm/
+~/bin/repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-2.3.0
+repo sync
+```
+
+This will cause repo to download all of the open source code associated with this ROCm release.
+You may want to ensure that you have ssh-keys configured on your machine for your GitHub ID.
+
+#### Building the ROCm source code
+
+Each ROCm component repository contains directions for building that component.
+As such, you should go to the repository you are interested in building to find how to build it.
+
+That said, AMD also offers [a project](https://github.com/RadeonOpenCompute/Experimental_ROC) that demonstrates how to download, build, package, and install ROCm software on various distributions.
+The scripts here may be useful for anyone looking to build ROCm components.
+
+### Deprecation Notice - HCC 
+AMD is deprecating HCC to put more focus on HIP development and on
+other languages supporting heterogeneous compute.  We will no longer
+develop any new feature in HCC and we will stop maintaining HCC after
+its final release, which is planned for June 2019.  If your
+application was developed with the hc C++ API, we would encourage you
+to transition it to other languages supported by AMD, such as HIP or
+OpenCL.  HIP and hc language share the same compiler technology, so
+many hc kernel language features (including inline assembly) are also
+available through the HIP compilation path.
+
+### Final notes
+* OpenCL Runtime and Compiler will be submitted to the Khronos Group for conformance testing prior to its final release.

RELEASE.md

@@ -1,39 +0,0 @@
-# Release Notes
-<!-- Do not edit this file! This file is autogenerated with -->
-<!--   tools/autotag/tag_script.py                          -->
-
-<!-- Disable lints since this is an auto-generated file.    -->
-<!-- markdownlint-disable blanks-around-headers             -->
-<!-- markdownlint-disable no-duplicate-header               -->
-<!-- markdownlint-disable no-blanks-blockquote              -->
-<!-- markdownlint-disable ul-indent                         -->
-<!-- markdownlint-disable no-trailing-spaces                -->
-
-<!-- spellcheck-disable -->
-
-The release notes for the ROCm platform.
-
--------------------
-
-## ROCm 5.1.1
-
-
-### Library Changes in ROCM 5.1.1
-
-| Library | Version |
-|---------|---------|
-| hipBLAS | [0.50.0](https://github.com/ROCmSoftwarePlatform/hipBLAS/releases/tag/rocm-5.1.1) |
-| hipCUB | [2.11.0](https://github.com/ROCmSoftwarePlatform/hipCUB/releases/tag/rocm-5.1.1) |
-| hipFFT | [1.0.7](https://github.com/ROCmSoftwarePlatform/hipFFT/releases/tag/rocm-5.1.1) |
-| hipSOLVER | [1.3.0](https://github.com/ROCmSoftwarePlatform/hipSOLVER/releases/tag/rocm-5.1.1) |
-| hipSPARSE | [2.1.0](https://github.com/ROCmSoftwarePlatform/hipSPARSE/releases/tag/rocm-5.1.1) |
-| rccl | [2.11.4](https://github.com/ROCmSoftwarePlatform/rccl/releases/tag/rocm-5.1.1) |
-| rocALUTION | [2.0.2](https://github.com/ROCmSoftwarePlatform/rocALUTION/releases/tag/rocm-5.1.1) |
-| rocBLAS | [2.43.0](https://github.com/ROCmSoftwarePlatform/rocBLAS/releases/tag/rocm-5.1.1) |
-| rocFFT | [1.0.16](https://github.com/ROCmSoftwarePlatform/rocFFT/releases/tag/rocm-5.1.1) |
-| rocPRIM | [2.10.13](https://github.com/ROCmSoftwarePlatform/rocPRIM/releases/tag/rocm-5.1.1) |
-| rocRAND | [2.10.13](https://github.com/ROCmSoftwarePlatform/rocRAND/releases/tag/rocm-5.1.1) |
-| rocSOLVER | [3.17.0](https://github.com/ROCmSoftwarePlatform/rocSOLVER/releases/tag/rocm-5.1.1) |
-| rocSPARSE | [2.1.0](https://github.com/ROCmSoftwarePlatform/rocSPARSE/releases/tag/rocm-5.1.1) |
-| rocThrust | [2.14.0](https://github.com/ROCmSoftwarePlatform/rocThrust/releases/tag/rocm-5.1.1) |
-| Tensile | [4.32.0](https://github.com/ROCmSoftwarePlatform/Tensile/releases/tag/rocm-5.1.1) |

default.xml

@@ -1,79 +1,73 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <manifest>
+
     <remote name="roc-github"
-fetch="https://github.com/RadeonOpenCompute/" />
+            fetch="http://github.com/RadeonOpenCompute/" />
     <remote name="rocm-devtools"
-fetch="https://github.com/ROCm-Developer-Tools/" />
+            fetch="https://github.com/ROCm-Developer-Tools/" />
     <remote name="rocm-swplat"
-fetch="https://github.com/ROCmSoftwarePlatform/" />
+            fetch="https://github.com/ROCmSoftwarePlatform/" />
     <remote name="gpuopen-libs"
-fetch="https://github.com/GPUOpen-ProfessionalCompute-Libraries/" />
+            fetch="https://github.com/GPUOpen-ProfessionalCompute-Libraries/" />
     <remote name="gpuopen-tools"
-fetch="https://github.com/GPUOpen-Tools/" />
-    <remote name="KhronosGroup"
-fetch="https://github.com/KhronosGroup/" />
-    <default revision="refs/tags/rocm-5.5.1"
-     remote="roc-github"
-     sync-c="true"
-     sync-j="4" />
-<!--list of projects for ROCM-->
+            fetch="https://github.com/GPUOpen-Tools/" />
+
+    <default revision="refs/tags/roc-2.3.0"
+             remote="roc-github"
+             sync-c="true"
+             sync-j="4" />
+
     <project name="ROCK-Kernel-Driver" />
     <project name="ROCT-Thunk-Interface" />
     <project name="ROCR-Runtime" />
-    <project name="rocm_smi_lib" />
-    <project name="rocm-core" />
-    <project name="rocm-cmake" />
-    <project name="rocminfo" />
+    <project name="ROC-smi" />
+    <project name="rocm-cmake" revision="ac45c6e269d1fd1dbd5dfc81cfe47a7452c96daf" />
+    <project name="rocminfo" revision="1bb0ccc731f772bb1a553e37b41d06eb0a684926" />
     <project name="rocprofiler" remote="rocm-devtools" />
     <project name="roctracer" remote="rocm-devtools" />
+    <!-- If you want to get the full OpenCL runtime, there is a separate repo
+         manifest that is more authoritative than the copy in this file. It can
+         be found at the following URL:
+         https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/blob/roc-2.0.0/opencl.xml -->
+    <remote name="KhronosGroup" fetch="https://github.com/KhronosGroup/" />
     <project name="ROCm-OpenCL-Runtime" />
-    <project path="ROCm-OpenCL-Runtime/api/opencl/khronos/icd" name="OpenCL-ICD-Loader" remote="KhronosGroup" revision="6c03f8b58fafd9dd693eaac826749a5cfad515f8" />
+    <project path="ROCm-OpenCL-Runtime/compiler/driver" name="ROCm-OpenCL-Driver"/>
+    <project path="ROCm-OpenCL-Runtime/compiler/llvm" name="llvm" revision="refs/tags/roc-ocl-2.3.0" />
+    <project path="ROCm-OpenCL-Runtime/compiler/llvm/tools/clang" name="clang" />
+    <project path="ROCm-OpenCL-Runtime/compiler/llvm/tools/lld" name="lld" revision="refs/tags/roc-ocl-2.3.0" />
+    <project path="ROCm-OpenCL-Runtime/library/amdgcn" name="ROCm-Device-Libs"/>
+    <project path="ROCm-OpenCL-Runtime/api/opencl/khronos/icd" name="OpenCL-ICD-Loader" remote="KhronosGroup" revision="261c1288aadd9dcc4637aca08332f603e6c13715" />
+
     <project name="clang-ocl" />
-<!--HIP Projects-->
+    <!-- HCC needs to be recursively synced to get it submodules -->
+    <project name="hcc" sync-s="true" />
+    <project name="HCC-Example-Application" remote="rocm-devtools" revision="ffd6533305e79eed667badd3c4cdb7879a1281b8" />
     <project name="HIP" remote="rocm-devtools" />
-    <project name="hipamd" remote="rocm-devtools" />
     <project name="HIP-Examples" remote="rocm-devtools" />
-    <project name="ROCclr" remote="rocm-devtools" />
-    <project name="HIPIFY" remote="rocm-devtools" />
-    <project name="HIPCC" remote="rocm-devtools" />
-<!-- The following projects are all associated with the AMDGPU LLVM compiler -->
-    <project name="llvm-project" />
+    <!-- The following projects are all associated with the AMDGPU LLVM compiler -->
+    <project name="llvm" path="llvm_amd-common" revision="refs/tags/roc-hcc-2.3.0" />
+    <project name="lld" path="llvm_amd-common/lld" revision="refs/tags/roc-hcc-2.3.0" />
+    <project name="clang" path="llvm_amd-common/clang" />
     <project name="ROCm-Device-Libs" />
-    <project name="atmi" />
+    <project name="atmi" revision="4dd14ad8fafc64dc8f35b0646cfe84e3e36a3c64" />
     <project name="ROCm-CompilerSupport" />
     <project name="rocr_debug_agent" remote="rocm-devtools" />
     <project name="rocm_bandwidth_test" />
-    <project name="half" remote="rocm-swplat" revision="37742ce15b76b44e4b271c1e66d13d2fa7bd003e" />
-    <project name="RCP" remote="gpuopen-tools" revision="3a49405a1500067c49d181844ec90aea606055bb" />
-<!-- gdb projects -->
-    <project name="ROCgdb" remote="rocm-devtools" />
-    <project name="ROCdbgapi" remote="rocm-devtools" />
-<!-- ROCm Libraries -->
-    <project name="rdc" />
-    <project groups="mathlibs" name="rocBLAS" remote="rocm-swplat" />
-    <project groups="mathlibs" name="Tensile" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipBLAS" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocFFT" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipFFT" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocRAND" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocSPARSE" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocSOLVER" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipSOLVER" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipSPARSE" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocALUTION" remote="rocm-swplat" />
-    <project name="MIOpenGEMM" remote="rocm-swplat" />
-    <project name="MIOpen" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rccl" remote="rocm-swplat" />
-    <project name="MIVisionX" remote="gpuopen-libs" />
-    <project groups="mathlibs" name="rocThrust" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipCUB" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocPRIM" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocWMMA" remote="rocm-swplat" />
-    <project name="hipfort" remote="rocm-swplat" />
-    <project name="AMDMIGraphX" remote="rocm-swplat" />
-    <project name="ROCmValidationSuite" remote="rocm-devtools" />
-<!-- Projects for OpenMP-Extras -->
-    <project name="aomp" path="openmp-extras/aomp" remote="rocm-devtools" />
-    <project name="aomp-extras" path="openmp-extras/aomp-extras" remote="rocm-devtools" />
-    <project name="flang" path="openmp-extras/flang" remote="rocm-devtools" />
+    <project name="RCP" remote="gpuopen-tools" revision="refs/tags/v5.6" />
+
+    <!-- ROCm Libraries -->
+    <project name="rocBLAS" remote="rocm-swplat" revision="00da0857152eeda58a9bfda611572ab30dbdc4de" />
+    <project name="hipBLAS" remote="rocm-swplat" revision="4accc37a9cb29eccbc17a036dc6d4ae0144bed4e" />
+    <project name="rocFFT" remote="rocm-swplat" revision="673805db60597698e23a409a1efe75d236b9f9d3" />
+    <project name="rocRAND" remote="rocm-swplat" revision="687d659a294f416c69dd6e860a8ded939e55c22a" />
+    <project name="rocSPARSE" remote="rocm-swplat" revision="0676d85f2f37e59f5696c02bcdc5dead6db6e5e9" />
+    <project name="hipSPARSE" remote="rocm-swplat" revision="refs/tags/v1.0.4" />
+    <project name="rocALUTION" remote="rocm-swplat" revision="be8d0c577bc3db217a8c10caaf9d2627119a3444" />
+    <project name="MIOpenGEMM" remote="rocm-swplat" revision="9547fb9e8499a5a9f16da83b1e6b749de82dd9fb" />
+    <project name="MIOpen" remote="rocm-swplat" revision="refs/tags/roc-2.3.0" />
+    <project name="Thrust" remote="rocm-swplat" revision="2f23ffb3932f303d910cad824b327c11893f0d68" sync-s="true" />
+    <project name="rocm_smi_lib" />
+    <project name="rccl" remote="rocm-swplat" revision="refs/tags/0.7.5" />
+    <project name="MIVisionX" remote="gpuopen-libs" revision="8ec87326b74d60a6f03a39298b83f192d440a939" />
+    <project name="cub-hip" remote="rocm-swplat" revision="hip_port_1.7.4" />
 </manifest>

docs/404.md

@@ -1,6 +0,0 @@
-# 404 Page Not Found
-
-Page could not be found.
-
-Return to [home](./index) or please use the links from the sidebar to find what
-you are looking for.

docs/about.md

@@ -1,74 +0,0 @@
-# About ROCm Documentation
-
-ROCm documentation is made available under open source [licenses](licensing.md).
-Documentation is built using open source toolchains. Contributions to our
-documentation is encouraged and welcome. As a contributor, please familiarize
-yourself with our documentation toolchain.
-
-## ReadTheDocs
-
-[ReadTheDocs](https://docs.readthedocs.io/en/stable/) is our front end for the
-our documentation. By front end, this is the tool that serves our HTML based
-documentation to our end users.
-
-## Doxygen
-
-[Doxygen](https://www.doxygen.nl/) is the most common inline code documentation
-standard. ROCm projects are use Doxygen for public API documentation (unless the
-upstream project is using a different tool).
-
-## Sphinx
-
-[Sphinx](https://www.sphinx-doc.org/en/master/) is a documentation generator
-originally used for python. It is now widely used in the Open Source community.
-Originally, sphinx supported RST based documentation. Markdown support is now
-available. ROCm documentation plans to default to markdown for new projects.
-Existing projects using RST are under no obligation to convert to markdown. New
-projects that believe markdown is not suitable should contact the documentation
-team prior to selecting RST.
-
-### MyST
-
-[Markedly Structured Text (MyST)](https://myst-tools.org/docs/spec) is an extended
-flavor of Markdown ([CommonMark](https://commonmark.org/)) influenced by reStructuredText (RST) and Sphinx.
-It is integrated via [`myst-parser`](https://myst-parser.readthedocs.io/en/latest/).
-A cheat sheet that showcases how to use the MyST syntax is available over at [the Jupyter
-reference](https://jupyterbook.org/en/stable/reference/cheatsheet.html).
-
-### Sphinx Theme
-
-ROCm is using the
-[Sphinx Book Theme](https://sphinx-book-theme.readthedocs.io/en/latest/). This
-theme is used by Jupyter books. ROCm documentation applies some customization
-include a header and footer on top of the Sphinx Book Theme. A future custom
-ROCm theme will be part of our documentation goals.
-
-### Sphinx Design
-
-Sphinx Design is an extension for sphinx based websites that add design
-functionality. Please see the documentation
-[here](https://sphinx-design.readthedocs.io/en/latest/index.html). ROCm
-documentation uses sphinx design for grids, cards, and synchronized tabs.
-Other features may be used in the future.
-
-### Sphinx External TOC
-
-ROCm uses the
-[sphinx-external-toc](https://sphinx-external-toc.readthedocs.io/en/latest/intro.html)
-for our navigation. This tool allows a YAML file based left navigation menu. This
-tool was selected due to its flexibility that allows scripts to operate on the
-YAML file. Please transition to this file for the project's navigation. You can
-see the `_toc.yml.in` file in this repository in the docs/sphinx folder for an
-example.
-
-### Breathe
-
-Sphinx uses [Breathe](https://www.breathe-doc.org/) to integrate Doxygen
-content.
-
-## `rocm-docs-core` pip package
-
-[rocm-docs-core](https://github.com/RadeonOpenCompute/rocm-docs-core) is an AMD
-maintained project that applies customization for our documentation. This
-project is the tool most ROCm repositories will use as part of the documentation
-build.

docs/conf.py

@@ -1,76 +0,0 @@
-# Configuration file for the Sphinx documentation builder.
-#
-# This file only contains a selection of the most common options. For a full
-# list see the documentation:
-# https://www.sphinx-doc.org/en/master/usage/configuration.html
-
-import shutil
-
-from rocm_docs import ROCmDocs
-
-
-shutil.copy2('../CONTRIBUTING.md','./contributing.md')
-shutil.copy2('../RELEASE.md','./release.md')
-# Keep capitalization due to similar linking on GitHub's markdown preview.
-shutil.copy2('../CHANGELOG.md','./CHANGELOG.md')
-
-# configurations for PDF output by Read the Docs
-project = "ROCm Documentation"
-author = "Advanced Micro Devices, Inc."
-copyright = "Copyright (c) 2023 Advanced Micro Devices, Inc. All rights reserved."
-version = "5.1.1"
-release = "5.1.1"
-
-setting_all_article_info = True
-all_article_info_os = ["linux"]
-all_article_info_author = ""
-
-# pages with specific settings
-article_pages = [
-    {"file":"deploy/linux/index", "os":["linux"]},
-    {"file":"deploy/linux/install_overview", "os":["linux"]},
-    {"file":"deploy/linux/prerequisites", "os":["linux"]},
-    {"file":"deploy/linux/quick_start", "os":["linux"]},
-    {"file":"deploy/linux/install", "os":["linux"]},
-    {"file":"deploy/linux/upgrade", "os":["linux"]},
-    {"file":"deploy/linux/uninstall", "os":["linux"]},
-    {"file":"deploy/linux/package_manager_integration", "os":["linux"]},
-    {"file":"deploy/docker", "os":["linux"]},
-    
-    {"file":"release/gpu_os_support", "os":["linux"]},
-    {"file":"release/docker_support_matrix", "os":["linux"]},
-    
-    {"file":"reference/gpu_libraries/communication", "os":["linux"]},
-    {"file":"reference/ai_tools", "os":["linux"]},
-    {"file":"reference/management_tools", "os":["linux"]},
-    {"file":"reference/validation_tools", "os":["linux"]},
-    {"file":"reference/framework_compatibility/framework_compatibility", "os":["linux"]},
-    {"file":"reference/computer_vision", "os":["linux"]},
-    
-    {"file":"how_to/deep_learning_rocm", "os":["linux"]},
-    {"file":"how_to/gpu_aware_mpi", "os":["linux"]},
-    {"file":"how_to/magma_install/magma_install", "os":["linux"]},
-    {"file":"how_to/pytorch_install/pytorch_install", "os":["linux"]},
-    {"file":"how_to/system_debugging", "os":["linux"]},
-    {"file":"how_to/tensorflow_install/tensorflow_install", "os":["linux"]},
-
-    {"file":"examples/machine_learning", "os":["linux"]},
-    {"file":"examples/inception_casestudy/inception_casestudy", "os":["linux"]},
-    
-    {"file":"understand/file_reorg", "os":["linux"]},
-
-    {"file":"understand/isv_deployment_win", "os":["windows"]},
-]
-
-external_toc_path = "./sphinx/_toc.yml"
-
-docs_core = ROCmDocs("ROCm 5.1.1 Documentation Home")
-docs_core.setup()
-
-external_projects_current_project = "rocm"
-
-for sphinx_var in ROCmDocs.SPHINX_VARS:
-    globals()[sphinx_var] = getattr(docs_core, sphinx_var)
-html_theme_options = {
-    "link_main_doc": False
-}

docs/data/deploy/quick_start_windows/image planning

@@ -1 +0,0 @@
-

docs/deploy/docker.md

@@ -1,90 +0,0 @@
-# Deploy ROCm Docker containers
-
-## Prerequisites
-
-Docker containers share the kernel with the host operating system, therefore the
-ROCm kernel-mode driver must be installed on the host. Please refer to
-{ref}`using-the-package-manager` on installing `amdgpu-dkms`. The other
-user-space parts (like the HIP-runtime or math libraries) of the ROCm stack will
-be loaded from the container image and don't need to be installed to the host.
-
-(docker-access-gpus-in-container)=
-
-## Accessing GPUs in containers
-
-In order to access GPUs in a container (to run applications using HIP, OpenCL or
-OpenMP offloading) explicit access to the GPUs must be granted.
-
-The ROCm runtimes make use of multiple device files:
-
-- `/dev/kfd`: the main compute interface shared by all GPUs
-- `/dev/dri/renderD<node>`: direct rendering interface (DRI) devices for each
-  GPU. **`<node>`** is a number for each card in the system starting from 128.
-
-Exposing these devices to a container is done by using the
-[`--device`](https://docs.docker.com/engine/reference/commandline/run/#device)
-option, i.e. to allow access to all GPUs expose `/dev/kfd` and all
-`/dev/dri/renderD` devices:
-
-```shell
-docker run --device /dev/kfd --device /dev/renderD128 --device /dev/renderD129 ...
-```
-
-More conveniently, instead of listing all devices, the entire `/dev/dri` folder
-can be exposed to the new container:
-
-```shell
-docker run --device /dev/kfd --device /dev/dri
-```
-
-Note that this gives more access than strictly required, as it also exposes the
-other device files found in that folder to the container.
-
-(docker-restrict-gpus)=
-
-### Restricting a container to a subset of the GPUs
-
-If a `/dev/dri/renderD` device is not exposed to a container then it cannot use
-the GPU associated with it; this allows to restrict a container to any subset of
-devices.
-
-For example to allow the container to access the first and third GPU start it
-like:
-
-```shell
-docker run --device /dev/kfd --device /dev/dri/renderD128 --device /dev/dri/renderD130 <image>
-```
-
-### Additional Options
-
-The performance of an application can vary depending on the assignment of GPUs
-and CPUs to the task. Typically, `numactl` is installed as part of many HPC
-applications to provide GPU/CPU mappings. This Docker runtime option supports
-memory mapping and can improve performance.
-
-```shell
---security-opt seccomp=unconfined
-```
-
-This option is recommended for Docker Containers running HPC applications.
-
-```shell
-docker run --device /dev/kfd --device /dev/dri --security-opt seccomp=unconfined ...
-```
-
-## Docker images in the ROCm ecosystem
-
-### Base images
-
-<https://github.com/RadeonOpenCompute/ROCm-docker> hosts images useful for users
-wishing to build their own containers leveraging ROCm. The built images are
-available from [Docker Hub](https://hub.docker.com/u/rocm). In particular
-`rocm/rocm-terminal` is a small image with the prerequisites to build HIP
-applications, but does not include any libraries.
-
-### Applications
-
-AMD provides pre-built images for various GPU-ready applications through its
-Infinity Hub at <https://www.amd.com/en/technologies/infinity-hub>.
-Examples for invoking each application and suggested parameters used for
-benchmarking are also provided there.

docs/deploy/linux/index.md

@@ -1,53 +0,0 @@
-# Deploy ROCm on Linux
-
-Start with {doc}`/deploy/linux/quick_start` or follow the detailed
-instructions below.
-
-## Prepare to Install
-
-::::{grid} 1 1 2 2
-:gutter: 1
-
-:::{grid-item-card} Prerequisites
-:link: prerequisites
-:link-type: doc
-
-The prerequisites page lists the required steps *before* installation.
-:::
-
-:::{grid-item-card} Install Choices
-:link: install_overview
-:link-type: doc
-
-Package manager vs AMDGPU Installer
-
-Standard Packages vs Multi-Version Packages
-:::
-
-::::
-
-## Choose your install method
-
-::::{grid} 1 1 2 2
-:gutter: 1
-
-:::{grid-item-card} Package Manager
-:link: os-native/index
-:link-type: doc
-
-Directly use your distribution's package manager to install ROCm.
-:::
-
-:::{grid-item-card} AMDGPU Installer
-:link: installer/index
-:link-type: doc
-
-Use an installer tool that orchestrates changes via the package
-manager.
-:::
-
-::::
-
-## See Also
-
-- {doc}`/release/gpu_os_support`

docs/deploy/linux/install_overview.md

@@ -1,71 +0,0 @@
-# ROCm Installation Options (Linux)
-
-Users installing ROCm must choose between various installation options. A new
-user should follow the [Quick Start guide](./quick_start).
-
-## Package Manager versus AMDGPU Installer?
-
-ROCm supports two methods for installation:
-
-- Directly using the Linux distribution's package manager
-- The `amdgpu-install` script
-
-There is no difference in the final installation state when choosing either
-option.
-
-Using the distribution's package manager lets the user install,
-upgrade and uninstall using familiar commands and workflows. Third party
-ecosystem support is the same as your OS package manager.
-
-The `amdgpu-install` script is a wrapper around the package manager. The same
-packages are installed by this script as the package manager system.
-
-The installer automates the installation process for the AMDGPU
-and ROCm stack. It handles the complete installation process
-for ROCm, including setting up the repository, cleaning the system, updating,
-and installing the desired drivers and meta-packages. Users who are
-less familiar with the package manager can choose this method for ROCm
-installation.
-
-(installation-types)=
-
-## Single Version ROCm install versus Multi-Version
-
-ROCm packages are versioned with both semantic versioning that is package
-specific and a ROCm release version.
-
-### Single-version Installation
-
-The single-version ROCm installation refers to the following:
-
-- Installation of a single instance of the ROCm release on a system
-- Use of non-versioned ROCm meta-packages
-
-### Multi-version Installation
-
-The multi-version installation refers to the following:
-
-- Installation of multiple instances of the ROCm stack on a system. Extending
-  the package name and its dependencies with the release version adds the
-  ability to support multiple versions of packages simultaneously.
-- Use of versioned ROCm meta-packages.
-
-```{attention}
-ROCm packages that were previously installed from a single-version installation
-must be removed before proceeding with the multi-version installation to avoid
-conflicts.
-```
-
-```{note}
-Multiversion install is not available for the kernel driver module, also referred to as AMDGPU.
-```
-
-The following image demonstrates the difference between single-version and
-multi-version ROCm installation types:
-
-```{figure-md} install-types
-
-<img src="/data/deploy/linux/image.001.png" alt="">
-
-ROCm Installation Types
-```

docs/deploy/linux/installer/index.md

@@ -1,31 +0,0 @@
-# AMDGPU Install Script
-
-::::{grid} 2 3 3 3
-:gutter: 1
-
-:::{grid-item-card} Install
-:link: install
-:link-type: doc
-
-How to install ROCm?
-:::
-
-:::{grid-item-card} Upgrade
-:link: upgrade
-:link-type: doc
-
-Instructions for upgrading an existing ROCm installation.
-:::
-
-:::{grid-item-card} Uninstall
-:link: uninstall
-:link-type: doc
-
-Steps for removing ROCm packages libraries and tools.
-:::
-
-::::
-
-## See Also
-
-- {doc}`/release/gpu_os_support`

docs/deploy/linux/installer/install.md

@@ -1,299 +0,0 @@
-# Installation with install script
-
-Prior to beginning, please ensure you have the [prerequisites](../prerequisites)
-installed.
-
-## Download the Installer Script
-
-To download and install the `amdgpu-install` script on the system, use the
-following commands based on your distribution.
-
-::::::{tab-set}
-:::::{tab-item} Ubuntu
-:sync: ubuntu
-
-::::{tab-set}
-:::{tab-item} Ubuntu 18.04
-:sync: ubuntu-18.04
-
-```shell
-sudo apt update
-wget https://repo.radeon.com/amdgpu-install/22.10.1/ubuntu/bionic/amdgpu-install_22.10.1.50101-1_all.deb
-sudo apt install ./amdgpu-install_22.10.1.50101-1_all.deb
-```
-
-:::
-:::{tab-item} Ubuntu 20.04
-:sync: ubuntu-20.04
-
-```shell
-sudo apt update
-wget https://repo.radeon.com/amdgpu-install/22.10.1/ubuntu/focal/amdgpu-install_22.10.1.50101-1_all.deb
-sudo apt install ./amdgpu-install_22.10.1.50101-1_all.deb
-```
-
-:::
-::::
-:::::
-:::::{tab-item} Red Hat Enterprise Linux
-:sync: RHEL
-
-::::{tab-set}
-:::{tab-item} RHEL 7.9
-:sync: RHEL-7.9
-:sync: RHEL-7
-
-```shell
-sudo yum install https://repo.radeon.com/amdgpu-install/22.10.1/rhel/7.9/amdgpu-install-22.10.1.50101-1.el7.noarch.rpm
-```
-
-:::
-:::{tab-item} RHEL 8.4
-:sync: RHEL-8.4
-:sync: RHEL-8
-
-```shell
-sudo yum install https://repo.radeon.com/amdgpu-install/22.10.1/rhel/8.4/amdgpu-install-22.10.1.50101-1.el8.noarch.rpm
-```
-
-:::
-:::{tab-item} RHEL 8.5
-:sync: RHEL-8.5
-:sync: RHEL-8
-
-```shell
-sudo yum install https://repo.radeon.com/amdgpu-install/22.10.1/rhel/8.5/amdgpu-install-22.10.1.50101-1.el8.noarch.rpm
-```
-
-:::
-::::
-:::::
-:::::{tab-item} SUSE Linux Enterprise Server 15
-:sync: SLES15
-
-::::{tab-set}
-:::{tab-item} Service Pack 4
-:sync: SLES15-SP4
-
-```shell
-sudo zypper --no-gpg-checks install https://repo.radeon.com/amdgpu-install/22.10.1/sle/15/amdgpu-install-22.10.1.50101-1.noarch.rpm
-```
-
-:::
-::::
-:::::
-::::::
-
-## Use cases
-
-Instead of installing individual applications or libraries the installer script
-groups packages into specific use cases, matching typical workflows and runtimes.
-
-To display a list of available use cases execute the command:
-
-```shell
-sudo amdgpu-install --list-usecase
-```
-
-The available use-cases will be printed in a format similar to the example
-output below.
-
-```none
-If --usecase option is not present, the default selection is "graphics,opencl,hip"
-
-Available use cases:
-rocm(for users and developers requiring full ROCm stack)
-- OpenCL (ROCr/KFD based) runtime
-- HIP runtimes
-- Machine learning framework
-- All ROCm libraries and applications
-- ROCm Compiler and device libraries
-- ROCr runtime and thunk
-lrt(for users of applications requiring ROCm runtime)
-- ROCm Compiler and device libraries
-- ROCr runtime and thunk
-opencl(for users of applications requiring OpenCL on Vega or
-later products)
-- ROCr based OpenCL
-- ROCm Language runtime
-
-openclsdk (for application developers requiring ROCr based OpenCL)
-- ROCr based OpenCL
-- ROCm Language runtime
-- development and SDK files for ROCr based OpenCL
-
-hip(for users of HIP runtime on AMD products)
-- HIP runtimes
-hiplibsdk (for application developers requiring HIP on AMD products)
-- HIP runtimes
-- ROCm math libraries
-- HIP development libraries
-```
-
-To install use cases specific to your requirements, use the installer
-`amdgpu-install` as follows:
-
-- To install a single use case add it with the `--usecase` option:
-
-  ```shell
-  sudo amdgpu-install --usecase=rocm
-  ```
-
-- For multiple use cases separate them with commas:
-
-  ```shell
-  sudo amdgpu-install --usecase=hiplibsdk,rocm
-  ```
-
-## Single-version ROCm Installation
-
-By default (without the `--rocmrelease` option)
-the installer script will install packages in the single-version layout.
-
-## Multi-version ROCm Installation
-
-For the multi-version ROCm installation you must use the installer script from
-the latest release of ROCm that you wish to install.
-
-**Example:** If you want to install ROCm releases 5.0.2 and 5.1.1
-simultaneously, you are required to download the installer from the latest ROCm
-release v5.1.1.
-
-### Add Required Repositories
-
-You must add the ROCm repositories manually for all ROCm releases
-you want to install except the latest one. The `amdgpu-install` script
-automatically adds the required repositories for the latest release.
-
-Run the following commands based on your distribution to add the repositories:
-
-::::::{tab-set}
-:::::{tab-item} Ubuntu
-:sync: ubuntu
-
-::::{tab-set}
-:::{tab-item} Ubuntu 18.04
-:sync: ubuntu-18.04
-
-```shell
-for ver in 5.0.2 5.1.1; do
-echo "deb [arch=amd64 signed-by=/etc/apt/trusted.gpg.d/rocm-keyring.gpg] https://repo.radeon.com/rocm/apt/$ver bionic main" | sudo tee /etc/apt/sources.list.d/rocm.list
-done
-echo -e 'Package: *\nPin: release o=repo.radeon.com\nPin-Priority: 600' | sudo tee /etc/apt/preferences.d/rocm-pin-600
-sudo apt update
-```
-
-:::
-:::{tab-item} Ubuntu 20.04
-:sync: ubuntu-20.04
-
-```shell
-for ver in 5.0.2 5.1.1; do
-echo "deb [arch=amd64 signed-by=/etc/apt/trusted.gpg.d/rocm-keyring.gpg] https://repo.radeon.com/rocm/apt/$ver focal main" | sudo tee /etc/apt/sources.list.d/rocm.list
-done
-echo -e 'Package: *\nPin: release o=repo.radeon.com\nPin-Priority: 600' | sudo tee /etc/apt/preferences.d/rocm-pin-600
-sudo apt update
-```
-
-:::
-::::
-:::::
-:::::{tab-item} Red Hat Enterprise Linux
-:sync: RHEL
-
-::::{tab-set}
-:::{tab-item} RHEL 7
-:sync: RHEL-7
-
-```shell
-for ver in 5.0.2 5.1.1; do
-sudo tee --append /etc/yum.repos.d/rocm.repo <<EOF
-[ROCm-$ver]
-name=ROCm$ver
-baseurl=https://repo.radeon.com/rocm/yum/$ver/main
-enabled=1
-priority=50
-gpgcheck=1
-gpgkey=https://repo.radeon.com/rocm/rocm.gpg.key
-EOF
-done
-sudo yum clean all
-```
-
-:::
-:::{tab-item} RHEL 8
-:sync: RHEL-8
-
-```shell
-for ver in 5.0.2 5.1.1; do
-sudo tee --append /etc/yum.repos.d/rocm.repo <<EOF
-[ROCm-$ver]
-name=ROCm$ver
-baseurl=https://repo.radeon.com/rocm/yum/$ver/main
-enabled=1
-priority=50
-gpgcheck=1
-gpgkey=https://repo.radeon.com/rocm/rocm.gpg.key
-EOF
-done
-sudo yum clean all
-```
-
-:::
-::::
-:::::
-:::::{tab-item} SUSE Linux Enterprise Server 15
-:sync: SLES15
-
-```shell
-for ver in 5.0.2 5.1.1; do
-sudo tee --append /etc/zypp/repos.d/rocm.repo <<EOF
-name=rocm
-baseurl=https://repo.radeon.com/rocm/zyp/$ver/main
-enabled=1
-gpgcheck=1
-gpgkey=https://repo.radeon.com/rocm/rocm.gpg.key
-EOF
-done
-sudo zypper ref
-```
-
-:::::
-::::::
-
-### Install packages
-
-Use the installer script as given below:
-
-```none
-sudo amdgpu-install --usecase=rocm --rocmrelease=<release-number-1>
-sudo amdgpu-install --usecase=rocm --rocmrelease=<release-number-2>
-sudo amdgpu-install --usecase=rocm --rocmrelease=<release-number-3>
-```
-
-Following are examples of ROCm multi-version installation. The kernel-mode
-driver, associated with the ROCm release v5.1.1, will be installed as its latest
-release in the list.
-
-```none
-sudo amdgpu-install --usecase=rocm --rocmrelease=5.0.2
-sudo amdgpu-install --usecase=rocm --rocmrelease=5.1.1
-```
-
-## Additional options
-
-### Unattended installation
-
-Adding `-y` as a parameter to `amdgpu-install` skips user prompts (for
-automation). Example: `amdgpu-install -y --usecase=rocm`
-
-### Skipping kernel mode driver installation
-
-The installer script tries to install the kernel mode driver along with the
-requested use cases. This might be unnecessary as in the case of docker
-containers or you may wish to keep a specific version when using multi-version
-installation, and not have the last installed version overwrite the kernel mode
-driver.
-
-To skip the installation of the kernel-mode driver add the `--no-dkms` option
-when calling the installer script.

docs/deploy/linux/installer/uninstall.md

@@ -1,25 +0,0 @@
-# Installer Script Uninstallation (Linux)
-
-To uninstall all ROCm packages and the kernel-mode driver the following commands
-can be used.
-
-::::{rubric} Uninstalling Single-Version Install
-::::
-
-```console shell
-sudo amdgpu-install --uninstall
-```
-
-::::{rubric} Uninstalling a Specific ROCm Release
-::::
-
-```console shell
-sudo amdgpu-install --uninstall --rocmrelease=<release-number>
-```
-
-::::{rubric} Uninstalling all ROCm Releases
-::::
-
-```console shell
-sudo amdgpu-install --uninstall --rocmrelease=all
-```

docs/deploy/linux/installer/upgrade.md

@@ -1,5 +0,0 @@
-# Upgrading with the Installer Script (Linux)
-
-The upgrade procedure with the installer script is exactly the same as
-installing for 1st time use. Refer to the {doc}`install`
-section on the exact procedure to follow.

docs/deploy/linux/os-native/index.md

@@ -1,38 +0,0 @@
-# Installation via Package manager
-
-::::{grid} 2 3 3 3
-:gutter: 1
-
-:::{grid-item-card} Install
-:link: install
-:link-type: doc
-
-How to install ROCm?
-:::
-
-:::{grid-item-card} Upgrade
-:link: upgrade
-:link-type: doc
-
-Instructions for upgrading an existing ROCm installation.
-:::
-
-:::{grid-item-card} Uninstall
-:link: uninstall
-:link-type: doc
-
-Steps for removing ROCm packages libraries and tools.
-:::
-
-:::{grid-item-card} Package Manager Integration
-:link: package_manager_integration
-:link-type: doc
-
-Information about packages.
-:::
-
-::::
-
-## See Also
-
-- {doc}`/release/gpu_os_support`