mirror of
https://github.com/ROCm/ROCm.git
synced 2026-01-10 15:18:11 -05:00
Compare commits
37 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
d85d330f17 | ||
|
|
c3efbe0263 | ||
|
|
e72d9d16f2 | ||
|
|
d6ebde1c2b | ||
|
|
c270440e1d | ||
|
|
87212e992e | ||
|
|
b9f3ba6cda | ||
|
|
befa37295e | ||
|
|
6e957870bd | ||
|
|
6906210c51 | ||
|
|
88a2c6a311 | ||
|
|
10366c7bae | ||
|
|
613020c029 | ||
|
|
bbf233a8a0 | ||
|
|
6dfc3154dc | ||
|
|
f38ab28a19 | ||
|
|
5aa6de9001 | ||
|
|
45bc0b6e8f | ||
|
|
46fe870c8d | ||
|
|
2d3d61969f | ||
|
|
6d9651756c | ||
|
|
435eee1860 | ||
|
|
ca7d03f4a6 | ||
|
|
aa48cad227 | ||
|
|
2f3d09e898 | ||
|
|
82ecac74bb | ||
|
|
d693175b09 | ||
|
|
293b24d915 | ||
|
|
950874f674 | ||
|
|
34586f3bd4 | ||
|
|
39790b6ea4 | ||
|
|
b6bf0086d0 | ||
|
|
c81f5e59cf | ||
|
|
353f901378 | ||
|
|
21e76e3fa5 | ||
|
|
488b62219f | ||
|
|
1a5a5efbd3 |
Binary file not shown.
Binary file not shown.
BIN
AMD_ROCm_Release_Notes_v3.3.pdf
Normal file
BIN
AMD_ROCm_Release_Notes_v3.3.pdf
Normal file
Binary file not shown.
BIN
MultiIns.png
Normal file
BIN
MultiIns.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 54 KiB |
619
README.md
619
README.md
@@ -1,6 +1,6 @@
|
||||
# AMD ROCm Release Notes v3.1.0
|
||||
# AMD ROCm Release Notes v3.3.0
|
||||
This page describes the features, fixed issues, and information about downloading and installing the ROCm software.
|
||||
It also covers known issues and deprecated features in the ROCm v3.1 release.
|
||||
It also covers known issues and deprecated features in the ROCm v3.3 release.
|
||||
|
||||
- [What Is ROCm?](#What-Is-ROCm)
|
||||
* [ROCm Components](#ROCm-Components)
|
||||
@@ -8,26 +8,18 @@ It also covers known issues and deprecated features in the ROCm v3.1 release.
|
||||
* [Important ROCm Links](#Important-ROCm-Links)
|
||||
|
||||
- [What\'s New in This Release](#Whats-New-in-This-Release)
|
||||
* [Change in ROCm Installation Directory Structure](#Change-in-ROCm-Installation-Directory-Structure)
|
||||
* [Reliability, Accessibility, and Serviceability Support for Vega7nm](#Reliability-Accessibility-and-Serviceability-Support-for-Vega7nm)
|
||||
* [SLURM Support for AMD GPU](#SLURM-Support-for-AMD-GPU)
|
||||
* [Multi Version Installation](#Multi-Version-Installation)
|
||||
* [GPU Process Information](#GPU-Process-Information)
|
||||
* [Support for 3D Pooling Layers](#Support-for-3D-Pooling-Layers)
|
||||
* [ONNX Enhancements](#ONNX-Enhancements)
|
||||
|
||||
|
||||
- [Known Issues](#Known-Issues)
|
||||
* [MIVision MIGraphX Installation](#MIVision-MIGraphX-Installation)
|
||||
* [Using TensorFlow](#Using-TensorFlow)
|
||||
* [HIP Compiler Dependency Issue](#HIP-Compiler-Dependency-Issue)
|
||||
* [Error Running ROC Profiler](#Error-Running-ROC-Profiler)
|
||||
|
||||
|
||||
|
||||
- [Deploying ROCm](#Deploying-ROCm)
|
||||
* [Ubuntu](#Ubuntu)
|
||||
* [CentOS RHEL v7](#CentOS-RHEL-v7)
|
||||
* [SLES 15 Service Pack 1](#SLES-15-Service-Pack-1)
|
||||
|
||||
- [Deprecations in This Release](#Deprecations-in-This-Release)
|
||||
* [Code Object Manager (Comgr) Functions](#Code-Object-Manager-(Comgr)-Functions)
|
||||
|
||||
|
||||
- [Getting the ROCm Source Code](#Getting-the-ROCm-Source-Code)
|
||||
- [Hardware and Software Support](#Hardware-and-Software-Support)
|
||||
- [Machine Learning and High Performance Computing Software Stack for AMD GPU](#Machine-Learning-and-High-Performance-Computing-Software-Stack-for-AMD-GPU)
|
||||
* [ROCm Binary Package Structure](#ROCm-Binary-Package-Structure)
|
||||
@@ -41,7 +33,7 @@ Note: You can also clone the source code for individual ROCm components from the
|
||||
|
||||
|
||||
### ROCm Components
|
||||
The following components for the ROCm platform are released and available for the v3.1
|
||||
The following components for the ROCm platform are released and available for the v3.3
|
||||
release:
|
||||
|
||||
• Drivers
|
||||
@@ -56,10 +48,10 @@ You can access the latest supported version of drivers, tools, libraries, and so
|
||||
https://github.com/RadeonOpenCompute/ROCm
|
||||
|
||||
### Supported Operating Systems
|
||||
The ROCm v3.1.x platform is designed to support the following operating systems:
|
||||
The ROCm v3.3.x platform is designed to support the following operating systems:
|
||||
|
||||
|
||||
* Ubuntu 16.04.6(Kernel 4.15) and 18.04.3(Kernel 5.3)
|
||||
* Ubuntu 16.04.6 (Kernel 4.15) and 18.04.4 (Kernel 5.3)
|
||||
|
||||
* CentOS v7.7 (Using devtoolset-7 runtime support)
|
||||
|
||||
@@ -68,7 +60,6 @@ The ROCm v3.1.x platform is designed to support the following operating systems:
|
||||
* SLES 15 SP1
|
||||
|
||||
|
||||
For details about deploying the ROCm v3.1.0.x on these operating systems, see the Deploying ROCm section later in the document.
|
||||
|
||||
### Important ROCm Links
|
||||
|
||||
@@ -77,11 +68,15 @@ Access the following links for more information on:
|
||||
* ROCm documentation, see
|
||||
https://rocm-documentation.readthedocs.io/en/latest/index.html
|
||||
|
||||
* ROCm binary structure, see
|
||||
https://github.com/RadeonOpenCompute/ROCm/blob/master/README.md#rocm-binary-package-structure
|
||||
* ROCm Release Notes
|
||||
https://rocm-documentation.readthedocs.io/en/latest/Current_Release_Notes/Current-Release-Notes.html
|
||||
|
||||
* ROCm QuickStart Installation Guide, see
|
||||
https://rocm-documentation.readthedocs.io/en/latest/Installation_Guide/Installation-Guide.html
|
||||
|
||||
* ROCm binary structure, see
|
||||
https://rocm-documentation.readthedocs.io/en/latest/Installation_Guide/Installation-Guide.html#rocm-platform-packages
|
||||
|
||||
* Common ROCm installation issues, see
|
||||
https://rocm.github.io/install_issues.html
|
||||
|
||||
* Instructions to install PyTorch after ROCm is installed – https://rocm-documentation.readthedocs.io/en/latest/Deep_learning/Deep-learning.html#pytorch
|
||||
|
||||
@@ -90,393 +85,144 @@ Note: These instructions reference the rocm/pytorch:rocm3.0_ubuntu16.04_py2.7_py
|
||||
|
||||
## What\'s New in This Release
|
||||
|
||||
### Change in ROCm Installation Directory Structure
|
||||
A fresh installation of the ROCm toolkit installs the packages in the */opt/rocm-\<version>* folder.
|
||||
### Multi Version Installation
|
||||
|
||||
Users can install and access multiple versions of the ROCm toolkit simultaneously.
|
||||
|
||||
Previously, users could install only a single version of the ROCm toolkit.
|
||||
|
||||
Now, users have the option to install multiple versions simultaneously and toggle to the desired version of the ROCm toolkit. From the v3.3 release, multiple versions of ROCm packages can be installed in the */opt/rocm-<version>* folder.
|
||||
|
||||
|
||||
**Prerequisites**
|
||||
|
||||
Ensure the existing installations of ROCm, including/opt/rocm, are completely removed before the v3.3 ROCm toolkit installation. The ROCm v3.3 package requires a clean installation.
|
||||
|
||||
* To install a single instance of ROCm, use the rocm-dkms or rocm-dev packages to install all the required components. This creates a symbolic link /opt/rocm pointing to the corresponding version of ROCm installed on the system.
|
||||
|
||||
* To install individual ROCm components, create the /opt/rocm symbolic link pointing to the version of ROCm installed on the system.
|
||||
For example, # ln -s /opt/rocm-3.3.0 /opt/rocm
|
||||
|
||||
* To install multiple instance ROCm packages, create /opt/rocm symbolic link pointing to the version of ROCm installed/used on the system.
|
||||
For example, # ln -s /opt/rocm-3.3.0 /opt/rocm
|
||||
|
||||
**NOTE**: The Kernel Fusion Driver (KFD) must be compatible with all versions of the ROCm software installed on the system.
|
||||
|
||||
**Before You Begin**
|
||||
|
||||
Review the following important notes:
|
||||
|
||||
Single Version Installation
|
||||
|
||||
To install a single instance of the ROCm package, access the non-versioned packages. You must not install any components from the multi-instance set.
|
||||
|
||||
For example,
|
||||
|
||||
* rocm-dkms
|
||||
* rocm-dev
|
||||
* hip
|
||||
|
||||
A fresh installation or an upgrade of the single-version installation will remove the existing version completely and install the new version in the */opt/rocm-<version>* folder.
|
||||
|
||||
|
||||
|
||||
|
||||
**Multi-version Installation**
|
||||
|
||||
* To install a multi-instance of the ROCm package, access the versioned packages and components.
|
||||
|
||||
For example,
|
||||
|
||||
* rocm-dkms3.3.0
|
||||
* rocm-dev3.3.0
|
||||
* hip3.3.0
|
||||
|
||||
Previously, ROCm toolkit packages were installed in the */opt/rocm* folder.
|
||||
* The new multi-instance package enables you to install two versions of the ROCm toolkit simultaneously and provides the ability to toggle between the two versioned packages.
|
||||
|
||||
|
||||
* The ROCm-DEV package does not create symlinks
|
||||
|
||||
## Reliability, Accessibility, and Serviceability Support for Vega7nm
|
||||
The Reliability, Accessibility, and Serviceability (RAS) support for Vega7nm is now available. The support includes:
|
||||
* Users must create symlinks if required
|
||||
|
||||
* UMC RAS – HBM ECC (uncorrectable error injection), page retirement, RAS recovery via GPU (BACO) reset
|
||||
* GFX RAS – GFX, MMHUB ECC (uncorrectable error injection), RAS recovery via GPU (BACO) reset
|
||||
* PCIE RAS – PCIE_BIF ECC (uncorrectable error injection), RAS recovery via GPU (BACO) reset
|
||||
* Multi-version installation with previous ROCm versions is not supported
|
||||
|
||||
## SLURM Support for AMD GPU
|
||||
SLURM (Simple Linux Utility for Resource Management) is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters. The latest version 20.02.0 of SLURM includes AMD plugins that enable SLURM to detect and configure AMD GPUs automatically. It also collects and reports the energy consumption of AMD GPUs.
|
||||
* Kernel Fusion Driver (KFD) must be compatible with all versions of ROCm installations
|
||||
|
||||
|
||||
|
||||
**IMPORTANT**: A single instance ROCm package cannot co-exist with the multi-instance package.
|
||||
|
||||
**NOTE**: The multi-instance installation applies only to ROCm v3.3 and above. This package requires a fresh installation after the complete removal of existing ROCm packages. **The multi-version installation is not backward compatible.**
|
||||
|
||||
|
||||
## GPU Process Information
|
||||
|
||||
## Known Issues
|
||||
A new functionality to display process information for GPUs is available in this release. For example, you can view the process details to determine if the GPU(s) must be reset.
|
||||
|
||||
### MIVision MIGraphX Installation
|
||||
To display the GPU process details, you can:
|
||||
|
||||
* Install and use the latest version of the MIVision/MIGraphX code.
|
||||
* Ensure the /opt/rocm symbolic link for the new version of ROCm is present and points to the right version of the ROCm toolkit.
|
||||
* Invoke the API
|
||||
|
||||
### Using TensorFlow
|
||||
The TensorFlow build system requires the following additional changes to support the new installation path:
|
||||
or
|
||||
|
||||
* Ensure the /opt/rocm symbolic link is preset and points to the right version of the ROCm toolkit.
|
||||
* Modify the build configure file to include the header files from the respective ROCm version-specific folder
|
||||
* Use the Command Line Interface (CLI)
|
||||
|
||||
### HIP Compiler Dependency Issue
|
||||
If the HIP compiler has a dependency on /opt/rocm, use the following workaround:
|
||||
For more details about the API and the command instructions, see
|
||||
|
||||
* Ensure the /opt/rocm symbolic link points to the right version of the ROCm software
|
||||
* Use the ROCM_PATH environment variable that points to the version of the ROCm software installed on the system.
|
||||
* Use the rocm-dkms package to install required ROCm components.
|
||||
https://github.com/RadeonOpenCompute/rocm_smi_lib/blob/master/docs/ROCm_SMI_Manual.pdf
|
||||
|
||||
### Error Running ROC Profiler
|
||||
**Issue:** Running ROC profiler results in the following error -
|
||||
“: hip / hsa trace due to "ImportError: No module named sqlite3" error”
|
||||
|
||||
**Workaround:** Export the Python version before running ROC profiler:
|
||||
## Support for 3D Pooling Layers
|
||||
|
||||
AMD ROCm is enhanced to include support for 3D pooling layers. The implementation of 3D pooling layers now allows users to run 3D convolutional networks, such as ResNext3D, on AMD Radeon Instinct GPUs.
|
||||
|
||||
|
||||
## ONNX Enhancements
|
||||
|
||||
Open Neural Network eXchange (ONNX) is a widely-used neural net exchange format. The AMD model compiler & optimizer support the pre-trained models in ONNX, NNEF, & Caffe formats. Currently, ONNX versions 1.3 and below are supported.
|
||||
|
||||
The AMD Neural Net Intermediate Representation (NNIR) is enhanced to handle the rapidly changing ONNX versions and its layers.
|
||||
|
||||
|
||||
|
||||
For more details about AMD support for ONNX and ISV samples, see
|
||||
|
||||
https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/tree/master/model_compiler
|
||||
|
||||
*export ROCP_PYTHON_VERSION=<python version>*
|
||||
*ex: export ROCP_PYTHON_VERSION=python3*
|
||||
|
||||
|
||||
## Deploying ROCm
|
||||
AMD hosts both Debian and RPM repositories for the ROCm v3.1.0x packages.
|
||||
AMD hosts both Debian and RPM repositories for the ROCm v3.3.0x packages.
|
||||
|
||||
The following directions show how to install ROCm on supported Debian-based systems such as Ubuntu 18.04.x.
|
||||
|
||||
Note: 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. In this case, you can exclude the rocm-dkms and rock-dkms packages.
|
||||
|
||||
For more information on the ROCm binary structure, see
|
||||
https://github.com/RadeonOpenCompute/ROCm/blob/master/README.md#rocm-binary-package-structure
|
||||
For more information on ROCM installation on all platforms, see
|
||||
|
||||
For information about upstream kernel drivers, see the Using Debian-based ROCm with Upstream Kernel Drivers section.
|
||||
https://rocm-documentation.readthedocs.io/en/latest/Installation_Guide/Installation-Guide.html
|
||||
|
||||
## Ubuntu
|
||||
### Installing a ROCm Package from a Debian Repository
|
||||
To install from a Debian Repository:
|
||||
1. Run the following code to ensure that your system is up to date:
|
||||
|
||||
sudo apt update
|
||||
|
||||
sudo apt dist-upgrade
|
||||
|
||||
sudo apt install libnuma-dev
|
||||
|
||||
sudo reboot
|
||||
|
||||
|
||||
2. Add the ROCm apt repository.
|
||||
|
||||
For Debian-based systems like Ubuntu, configure the Debian ROCm repository as follows:
|
||||
|
||||
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
|
||||
## Deprecations in This Release
|
||||
|
||||
|
||||
The gpg key may change; ensure it is updated when installing a new release. If the key signature verification fails while updating, re-add the key from the ROCm apt repository.
|
||||
### Code Object Manager (Comgr) Functions
|
||||
|
||||
The current rocm.gpg.key is not available in a standard key ring distribution, but has the following sha1sum hash:
|
||||
The following Code Object Manager (Comgr) functions are deprecated.
|
||||
|
||||
e85a40d1a43453fe37d63aa6899bc96e08f2817a rocm.gpg.key
|
||||
|
||||
* `amd_comgr_action_info_set_options`
|
||||
|
||||
3. Install the ROCm meta-package.
|
||||
Update the appropriate repository list and install the rocm-dkms meta-package:
|
||||
* `amd_comgr_action_info_get_options`
|
||||
|
||||
sudo apt update
|
||||
|
||||
sudo apt install rocm-dkms
|
||||
These functions were originally deprecated in version 1.3 of the Comgr library as they no longer support options with embedded spaces.
|
||||
The deprecated functions are now replaced with the array-oriented options API, which includes
|
||||
|
||||
* `amd_comgr_action_info_set_option_list`
|
||||
|
||||
4. Set permissions.
|
||||
To access the GPU, you must be a user in the video group. Ensure your user account is a member of the video group prior to using ROCm. To identify the groups you are a member of, use the following command:
|
||||
|
||||
groups
|
||||
|
||||
|
||||
5. To add your user to the video group, use the following command for the sudo password:
|
||||
|
||||
sudo usermod -a -G video $LOGNAME
|
||||
* `amd_comgr_action_info_get_option_list_count`
|
||||
|
||||
6. By default, add any future users to the video group. Run the following command to add users to the video group:
|
||||
* `amd_comgr_action_info_get_option_list_item`
|
||||
|
||||
echo 'ADD_EXTRA_GROUPS=1'
|
||||
sudo tee -a /etc/adduser.conf
|
||||
echo 'EXTRA_GROUPS=video'
|
||||
sudo tee -a /etc/adduser.conf
|
||||
|
||||
7. Restart the system.
|
||||
|
||||
8. Test the basic ROCm installation.
|
||||
|
||||
9. After restarting the system, run the following commands to verify that the ROCm installation is successful. If you see your GPUs listed by both commands, the installation is considered successful.
|
||||
|
||||
/opt/rocm/bin/rocminfo
|
||||
/opt/rocm/opencl/bin/x86_64/clinfo
|
||||
|
||||
Note: To run the ROCm programs more efficiently, add the ROCm binaries in your PATH.
|
||||
|
||||
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 installation issue, refer the FAQ at:
|
||||
https://rocm.github.io/install_issues.html
|
||||
|
||||
|
||||
|
||||
### Uninstalling ROCm Packages from Ubuntu
|
||||
To uninstall the ROCm packages from Ubuntu v16.04 or Ubuntu v18.04.x, run the following command:
|
||||
|
||||
sudo apt autoremove rocm-dkms
|
||||
|
||||
|
||||
### Installing Development Packages for Cross Compilation
|
||||
It is recommended that you develop and test applications on different systems. For example, some development or build systems may not have an AMD GPU installed. In this scenario, you must avoid installing the ROCk kernel driver on the development system.
|
||||
|
||||
Instead, install the following development subset of applications:
|
||||
|
||||
sudo apt update
|
||||
sudo apt install rocm-dev
|
||||
|
||||
Note: To execute ROCm enabled applications, you must install the full ROCm driver stack on your system.
|
||||
|
||||
|
||||
### Using Debian-based ROCm with Upstream Kernel Drivers
|
||||
You can install the ROCm user-level software without installing the AMD's custom ROCk kernel driver. To use the upstream kernels, run the following commands instead of installing rocm-dkms:
|
||||
|
||||
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 v7
|
||||
|
||||
This section describes how to install ROCm on supported RPM-based systems such as CentOS v7.7.
|
||||
|
||||
For more details, refer:
|
||||
https://github.com/RadeonOpenCompute/ROCm/blob/master/README.md#rocm-binary-package-structure
|
||||
|
||||
### Preparing RHEL v7 (7.7) for Installation
|
||||
RHEL is a subscription-based operating system. You must enable the external repositories to install on the devtoolset-7 environment and the dkms support files.
|
||||
|
||||
Note: The following steps do not apply to the CentOS installation.
|
||||
|
||||
1. The subscription for RHEL must be enabled and attached to a pool ID. See the Obtaining an RHEL image and license page for instructions on registering your system with the RHEL subscription server and attaching to a pool id.
|
||||
|
||||
2. Enable the following repositories:
|
||||
|
||||
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
|
||||
|
||||
3. Enable additional repositories by downloading and installing the epel-release-latest-7 repository RPM:
|
||||
|
||||
sudo rpm -ivh <repo>
|
||||
|
||||
For more details, see
|
||||
https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
|
||||
|
||||
4. Install and set up Devtoolset-7.
|
||||
|
||||
To setup the Devtoolset-7 environment, follow the instructions on this page:
|
||||
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
|
||||
|
||||
Note: devtoolset-7 is a software collections package and is not supported by AMD.
|
||||
|
||||
### Installing CentOS/RHEL (v7.7) for DKMS
|
||||
|
||||
Use the dkms tool to install the kernel drivers on CentOS/RHEL v7.7:
|
||||
|
||||
sudo yum install -y epel-release
|
||||
sudo yum install -y dkms kernel-headers-`uname -r` kernel-devel-`uname -r`
|
||||
|
||||
### Installing ROCm
|
||||
|
||||
To install ROCm on your system, follow the instructions below:
|
||||
|
||||
1. Delete the previous versions of ROCm before installing the latest version.
|
||||
2. Create a /etc/yum.repos.d/rocm.repo file with the following contents:
|
||||
|
||||
[ROCm]
|
||||
name=ROCm
|
||||
baseurl=http://repo.radeon.com/rocm/yum/rpm
|
||||
enabled=1
|
||||
gpgcheck=0
|
||||
|
||||
Note: The URL of the repository must point to the location of the repositories’ repodata database.
|
||||
|
||||
3. Install ROCm components using the following command:
|
||||
|
||||
sudo yum install rocm-dkms
|
||||
|
||||
4. Restart the system.The rock-dkms component is installed and the /dev/kfd device is now available.
|
||||
|
||||
5. Set permissions.
|
||||
To access the GPU, you must be a user in the video group. Ensure your user account is a member of the video group prior to using ROCm. To identify the groups you are a member of, use the following command:
|
||||
|
||||
groups
|
||||
|
||||
6. To add your user to the video group, use the following command for the sudo password:
|
||||
|
||||
sudo usermod -a -G video $LOGNAME
|
||||
|
||||
7. By default, add any future users to the video group. Run the following command to add users to the video group:
|
||||
|
||||
echo 'ADD_EXTRA_GROUPS=1' | sudo tee -a /etc/adduser.conf
|
||||
echo 'EXTRA_GROUPS=video' | sudo tee -a /etc/adduser.conf
|
||||
|
||||
|
||||
8. Restart the system.
|
||||
|
||||
9. Test the ROCm installation.
|
||||
|
||||
### Testing ROCm Installation
|
||||
After restarting the system, run the following commands to verify that the ROCm installation is successful. If you see your GPUs listed, you are good to go!
|
||||
|
||||
/opt/rocm/bin/rocminfo
|
||||
/opt/rocm/opencl/bin/x86_64/clinfo
|
||||
|
||||
Note: To run the ROCm programs more efficiently, add the ROCm binaries in your PATH for easy implementation of the ROCm programs.
|
||||
|
||||
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
|
||||
|
||||
|
||||
#### Compiling Applications Using HCC, HIP, and Other ROCm Software
|
||||
To compile applications or samples, run the following command to use gcc-7.2 provided by the devtoolset-7 environment:
|
||||
|
||||
scl enable devtoolset-7 bash
|
||||
|
||||
### Uninstalling ROCm from CentOS/RHEL v7.7
|
||||
To uninstall the ROCm packages, run the following command:
|
||||
|
||||
sudo yum autoremove rocm-dkms rock-dkms
|
||||
|
||||
### Installing Development Packages for Cross Compilation
|
||||
You can develop and test ROCm packages on different systems. For example, some development or build systems may not have an AMD GPU installed. In this scenario, you can avoid installing the ROCm kernel driver on your development system. Instead, install the following development subset of packages:
|
||||
|
||||
sudo yum install rocm-dev
|
||||
|
||||
Note: To execute ROCm-enabled applications, you will require a system installed with the full ROCm driver stack.
|
||||
|
||||
### Using ROCm with Upstream Kernel Drivers
|
||||
You can install ROCm user-level software without installing AMD's custom ROCk kernel driver. To use the upstream kernel drivers, run the following commands
|
||||
|
||||
sudo yum install rocm-dev
|
||||
echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"'
|
||||
sudo tee /etc/udev/rules.d/70-kfd.rules
|
||||
|
||||
Note: You can use these commands instead of installing rocm-dkms.
|
||||
|
||||
## SLES 15 Service Pack 1
|
||||
|
||||
The following section tells you how to perform an install and uninstall ROCm on SLES 15 SP 1.
|
||||
|
||||
### Installation
|
||||
1. Install the "dkms" package.
|
||||
|
||||
sudo SUSEConnect --product PackageHub/15.1/x86_64
|
||||
sudo zypper install dkms
|
||||
|
||||
2. Add the ROCm repo.
|
||||
|
||||
sudo zypper clean –all
|
||||
sudo zypper addrepo --no-gpgcheck http://repo.radeon.com/rocm/zyp/zypper/ rocm
|
||||
sudo zypper ref
|
||||
zypper install rocm-dkms
|
||||
sudo zypper install rocm-dkms
|
||||
sudo reboot
|
||||
|
||||
3. Run the following command once
|
||||
|
||||
cat <<EOF | sudo tee /etc/modprobe.d/10-unsupported-modules.conf
|
||||
allow_unsupported_modules 1
|
||||
EOF
|
||||
sudo modprobe amdgpu
|
||||
|
||||
4. Verify the ROCm installation.
|
||||
|
||||
5. Run /opt/rocm/bin/rocminfo and /opt/rocm/opencl/bin/x86_64/clinfo commands to list the GPUs and verify that the ROCm installation is successful.
|
||||
|
||||
6. Set permissions.
|
||||
|
||||
To access the GPU, you must be a user in the video group. Ensure your user account is a member of the video group prior to using ROCm. To identify the groups you are a member of, use the following command:
|
||||
|
||||
groups
|
||||
|
||||
7. To add your user to the video group, use the following command for the sudo password:
|
||||
|
||||
sudo usermod -a -G video $LOGNAME
|
||||
|
||||
8. By default, add any future users to the video group. Run the following command to add users to the video group:
|
||||
|
||||
echo 'ADD_EXTRA_GROUPS=1' | sudo tee -a /etc/adduser.conf
|
||||
echo 'EXTRA_GROUPS=video' | sudo tee -a /etc/adduser.conf
|
||||
|
||||
9. Restart the system.
|
||||
10. Test the basic ROCm installation.
|
||||
11. After restarting the system, run the following commands to verify that the ROCm installation is successful. If you see your GPUs listed by both commands, the installation is considered successful.
|
||||
|
||||
/opt/rocm/bin/rocminfo
|
||||
/opt/rocm/opencl/bin/x86_64/clinfo
|
||||
|
||||
Note: To run the ROCm programs more efficiently, add the ROCm binaries in your PATH.
|
||||
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
|
||||
|
||||
### Uninstallation
|
||||
To uninstall, use the following command:
|
||||
|
||||
sudo zypper remove rocm-dkms rock-dkms
|
||||
|
||||
Note: Ensure all other installed packages/components are removed.
|
||||
Note: Ensure all the content in the /opt/rocm directory is completely removed.
|
||||
|
||||
|
||||
## Performing an OpenCL-only Installation of ROCm
|
||||
Some users may want to install a subset of the full ROCm installation. 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.
|
||||
|
||||
sudo yum install rock-dkms rocm-opencl-devel
|
||||
|
||||
## ROCm Installation - Known Issues and Workarounds
|
||||
### Closed source components
|
||||
The ROCm platform relies on some closed source components to provide functionalities like HSA image support. These components are only available through the ROCm repositories, and they may be deprecated or become open source components in the future. These components are made available in the following packages:
|
||||
|
||||
• hsa-ext-rocr-dev
|
||||
|
||||
|
||||
## Getting the ROCm Source Code
|
||||
AMD ROCm is built from open source software. It is, therefore, possible to modify the various components of ROCm by downloading the source code and rebuilding the components. The source code for ROCm components can be cloned from each of the GitHub repositories using git. For easy access to download the correct versions of each of these tools, the ROCm repository contains a repo manifest file called default.xml. You can use this manifest file to download the source code for ROCm software.
|
||||
|
||||
### Installing the Repo
|
||||
The repo tool from Google® allows you to manage multiple git repositories simultaneously. Run the following commands to install the repo:
|
||||
|
||||
mkdir -p ~/bin/
|
||||
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
|
||||
chmod a+x ~/bin/repo
|
||||
|
||||
Note: You can choose a different folder to install the repo into if you desire. ~/bin/ is used as an example.
|
||||
|
||||
### Downloading the ROCm Source Code
|
||||
The following example shows how to use the repo binary to download the ROCm source code. If you choose a directory other than ~/bin/ to install the repo, you must use that chosen directory in the code as shown below:
|
||||
|
||||
mkdir -p ~/ROCm/
|
||||
cd ~/ROCm/
|
||||
~/bin/repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-3.1.0
|
||||
repo sync
|
||||
|
||||
Note: Using this sample code will cause the repo to download the open source code associated with this ROCm release. Ensure that you have ssh-keys configured on your machine for your GitHub ID prior to the download.
|
||||
|
||||
### Building the ROCm Source Code
|
||||
Each ROCm component repository contains directions for building that component. You can access the desired component for instructions to build the repository.
|
||||
|
||||
|
||||
### Hardware and Software Support
|
||||
## Hardware and Software 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.
|
||||
|
||||
@@ -502,7 +248,7 @@ The following list of GPUs are enabled in the ROCm software, though full support
|
||||
* GFX7 GPUs
|
||||
* "Hawaii" chips, such as the AMD Radeon R9 390X and FirePro W9100
|
||||
|
||||
As described in the next section, GFX8 GPUs require PCI Express 3.1.0 (PCIe 3.1.0) with support for PCIe atomics. This requires both CPU and motherboard support. GFX9 GPUs require PCIe 3.1.0 with support for PCIe atomics by default, but they can operate in most cases without this capability.
|
||||
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 require PCIe 3.0 with support for PCIe atomics by default, but they can operate in most cases without this capability.
|
||||
|
||||
The integrated GPUs in AMD APUs are not officially supported targets for ROCm.
|
||||
As described [below](#limited-support), "Carrizo", "Bristol Ridge", and "Raven Ridge" APUs are enabled in our upstream drivers and the ROCm OpenCL runtime.
|
||||
@@ -512,8 +258,8 @@ As such, they are not yet officially supported targets for ROCm.
|
||||
For a more detailed list of hardware support, please see [the following documentation](https://rocm.github.io/hardware.html).
|
||||
|
||||
#### Supported CPUs
|
||||
As described above, GFX8 GPUs require PCIe 3.1.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.1.0 and PCIe atomics.
|
||||
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:
|
||||
@@ -565,18 +311,10 @@ from the list provided above for compatibility purposes.
|
||||
##### Not supported
|
||||
|
||||
* "Tonga", "Iceland", "Vega M", and "Vega 12" GPUs are not supported in ROCm 2.9.x
|
||||
* We do not support GFX8-class GPUs (Fiji, Polaris, etc.) on CPUs that do not have PCIe 3.1.0 with PCIe atomics.
|
||||
* 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.
|
||||
|
||||
### Supported Operating Systems - New operating systems available
|
||||
|
||||
The ROCm 3.1.0.x platform supports the following operating systems:
|
||||
|
||||
* Ubuntu 16.04.5(Kernel 4.15) and 18.04.3(Kernel 4.15 and Kernel 4.18)
|
||||
* CentOS 7.7 (Using devtoolset-7 runtime support)
|
||||
* RHEL 7.7 (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.
|
||||
@@ -620,7 +358,7 @@ The releases of the upstream Linux kernel support the following GPUs in ROCm:
|
||||
|
||||
## Machine Learning and High Performance Computing Software Stack for AMD GPU
|
||||
|
||||
ROCm Version 3.1.0
|
||||
ROCm Version 3.3.0
|
||||
|
||||
### ROCm Binary Package Structure
|
||||
|
||||
@@ -727,56 +465,87 @@ Drivers, ToolChains, Libraries, and Source Code
|
||||
|
||||
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-3.1.0)
|
||||
- [ROCr Runtime](https://github.com/RadeonOpenCompute/ROCR-Runtime/tree/roc-3.1.0)
|
||||
- [ROCT Thunk Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-3.1.0)
|
||||
#### ROCm Core Components
|
||||
- [ROCk Kernel Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-3.3.0)
|
||||
- [ROCr Runtime](https://github.com/RadeonOpenCompute/ROCR-Runtime/tree/rocm-3.3.0)
|
||||
- [ROCT Thunk Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-3.3.0)
|
||||
|
||||
|
||||
#### ROCm Support Software
|
||||
- [ROCm SMI](https://github.com/RadeonOpenCompute/ROC-smi/tree/roc-3.1.0)
|
||||
- [ROCm cmake](https://github.com/RadeonOpenCompute/rocm-cmake/tree/roc-3.0.0)
|
||||
- [rocminfo](https://github.com/RadeonOpenCompute/rocminfo/tree/roc-3.1.0)
|
||||
- [ROCm Bandwidth Test](https://github.com/RadeonOpenCompute/rocm_bandwidth_test/tree/roc-3.1.0)
|
||||
- [ROCm SMI](https://github.com/RadeonOpenCompute/ROC-smi/tree/roc-3.3.0)
|
||||
- [ROCm cmake](https://github.com/RadeonOpenCompute/rocm-cmake/tree/rocm-3.3.0)
|
||||
- [rocminfo](https://github.com/RadeonOpenCompute/rocminfo/tree/rocm-3.3.0)
|
||||
- [ROCm Bandwidth Test](https://github.com/RadeonOpenCompute/rocm_bandwidth_test/tree/rocm-3.3.0)
|
||||
|
||||
#### ROCm Development ToolChains
|
||||
- [HCC compiler](https://github.com/RadeonOpenCompute/hcc/tree/roc-hcc-3.1.0)
|
||||
- [HIP](https://github.com/ROCm-Developer-Tools/HIP/tree/roc-3.1.0)
|
||||
- [ROCm Device Libraries HCC](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-hcc-3.1.0)
|
||||
- ROCm OpenCL, which is created from the following components:
|
||||
- [ROCm OpenCL Runtime](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/tree/roc-3.1.0)
|
||||
- The ROCm OpenCL compiler, which is created from the following components:
|
||||
- [ROCm LLVM OCL](http://github.com/RadeonOpenCompute/llvm-project/tree/roc-ocl-3.1.0)
|
||||
- [ROCm Device Libraries OCL](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-ocl-3.1.0)
|
||||
- [ROCM Clang-OCL Kernel Compiler](https://github.com/RadeonOpenCompute/clang-ocl/tree/roc-3.1.0)
|
||||
- [Asynchronous Task and Memory Interface (ATMI)](https://github.com/RadeonOpenCompute/atmi/tree/rocm_3.1.0)
|
||||
- [ROCr Debug Agent](https://github.com/ROCm-Developer-Tools/rocr_debug_agent/tree/roc-3.1.0)
|
||||
- [ROCm Code Object Manager](https://github.com/RadeonOpenCompute/ROCm-CompilerSupport/tree/roc-3.1.0)
|
||||
- [ROC Profiler](https://github.com/ROCm-Developer-Tools/rocprofiler/tree/roc-3.1.0)
|
||||
- [ROC Tracer](https://github.com/ROCm-Developer-Tools/roctracer/tree/roc-3.1.x)
|
||||
- [AOMP](https://github.com/ROCm-Developer-Tools/aomp/tree/roc-3.1.0)
|
||||
- [HCC compiler](https://github.com/RadeonOpenCompute/hcc/tree/rocm-hcc-3.3.0)
|
||||
|
||||
- [HIP](https://github.com/ROCm-Developer-Tools/HIP/tree/rocm-3.3.0)
|
||||
|
||||
- [ROCm Device Libraries HCC](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-ocl-3.3.0)
|
||||
|
||||
- [ROCm OpenCL Runtime](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/tree/roc-3.3.0)
|
||||
|
||||
- [ROCm LLVM OCL](http://github.com/RadeonOpenCompute/llvm-project/tree/rocm-ocl-3.3.0)
|
||||
|
||||
- [ROCm Device Libraries OCL](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/rocm-ocl-3.3.0)
|
||||
|
||||
- [ROCM Clang-OCL Kernel Compiler](https://github.com/RadeonOpenCompute/clang-ocl/tree/rocm-3.3.0)
|
||||
|
||||
- [Asynchronous Task and Memory Interface (ATMI)](https://github.com/RadeonOpenCompute/atmi/tree/rocm-3.3.0)
|
||||
|
||||
- [ROCr Debug Agent](https://github.com/ROCm-Developer-Tools/rocr_debug_agent/tree/roc-3.3.0)
|
||||
|
||||
- [ROCm Code Object Manager](https://github.com/RadeonOpenCompute/ROCm-CompilerSupport/tree/rocm-3.3.0)
|
||||
|
||||
- [ROC Profiler](https://github.com/ROCm-Developer-Tools/rocprofiler/tree/roc-3.3.0)
|
||||
|
||||
- [ROC Tracer](https://github.com/ROCm-Developer-Tools/roctracer/tree/roc-3.3.0)
|
||||
|
||||
- [AOMP](https://github.com/ROCm-Developer-Tools/aomp/tree/roc-3.3.0)
|
||||
|
||||
- [Radeon Compute Profiler](https://github.com/GPUOpen-Tools/RCP/tree/3a49405)
|
||||
- [ROCmValidationSuite](https://github.com/ROCm-Developer-Tools/ROCmValidationSuite/tree/roc-3.1.0)
|
||||
|
||||
- [ROCmValidationSuite](https://github.com/ROCm-Developer-Tools/ROCmValidationSuite/tree/roc-3.3.0)
|
||||
|
||||
- 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-3.1.0)
|
||||
|
||||
- [HIP Examples](https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/rocm-3.3.0)
|
||||
|
||||
#### ROCm Libraries
|
||||
- [rocBLAS](https://github.com/ROCmSoftwarePlatform/rocBLAS/tree/rocm-3.1)
|
||||
- [hipBLAS](https://github.com/ROCmSoftwarePlatform/hipBLAS/tree/rocm-3.1)
|
||||
- [rocFFT](https://github.com/ROCmSoftwarePlatform/rocFFT/tree/rocm-3.1)
|
||||
- [rocRAND](https://github.com/ROCmSoftwarePlatform/rocRAND/tree/3.1.0)
|
||||
- [rocSPARSE](https://github.com/ROCmSoftwarePlatform/rocSPARSE/tree/rocm-3.1)
|
||||
- [hipSPARSE](https://github.com/ROCmSoftwarePlatform/hipSPARSE/tree/rocm-3.1)
|
||||
- [rocALUTION](https://github.com/ROCmSoftwarePlatform/rocALUTION/tree/rocm-3.1)
|
||||
|
||||
- [rocBLAS](https://github.com/ROCmSoftwarePlatform/rocBLAS/tree/rocm-3.3.0)
|
||||
|
||||
- [hipBLAS](https://github.com/ROCmSoftwarePlatform/hipBLAS/tree/rocm-3.3.0)
|
||||
|
||||
- [rocFFT](https://github.com/ROCmSoftwarePlatform/rocFFT/tree/rocm-3.3)
|
||||
|
||||
- [rocRAND](https://github.com/ROCmSoftwarePlatform/rocRAND/tree/rocm-3.3.0)
|
||||
|
||||
- [rocSPARSE](https://github.com/ROCmSoftwarePlatform/rocSPARSE/tree/rocm-3.3.0)
|
||||
|
||||
- [hipSPARSE](https://github.com/ROCmSoftwarePlatform/hipSPARSE/tree/rocm-3.3.0)
|
||||
|
||||
- [rocALUTION](https://github.com/ROCmSoftwarePlatform/rocALUTION/tree/rocm-3.3.0)
|
||||
|
||||
- [MIOpenGEMM](https://github.com/ROCmSoftwarePlatform/MIOpenGEMM/tree/b51a125)
|
||||
- [MIOpen](https://github.com/ROCmSoftwarePlatform/MIOpen/tree/roc-3.1.0)
|
||||
- [rocThrust](https://github.com/ROCmSoftwarePlatform/rocThrust/tree/3.1.0)
|
||||
- [ROCm SMI Lib](https://github.com/RadeonOpenCompute/rocm_smi_lib/tree/roc-3.1.0)
|
||||
- [RCCL](https://github.com/ROCmSoftwarePlatform/rccl/tree/3.1.0)
|
||||
|
||||
- [MIOpen](https://github.com/ROCmSoftwarePlatform/MIOpen/tree/roc-3.3.0)
|
||||
|
||||
- [rocThrust](https://github.com/ROCmSoftwarePlatform/rocThrust/tree/rocm-3.3.0)
|
||||
|
||||
- [ROCm SMI Lib](https://github.com/RadeonOpenCompute/rocm_smi_lib/tree/rocm-3.3.0)
|
||||
|
||||
- [RCCL](https://github.com/ROCmSoftwarePlatform/rccl/tree/rocm-3.3.0)
|
||||
|
||||
- [MIVisionX](https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/commit/755e7a08d5299a95c42def092af7c736d5eda90c)
|
||||
- [hipCUB](https://github.com/ROCmSoftwarePlatform/hipCUB/tree/3.1.0)
|
||||
- [AMDMIGraphX](https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/tree/0.5.1)
|
||||
|
||||
- [MIVisionX] https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/tree/1.7)
|
||||
|
||||
- [hipCUB](https://github.com/ROCmSoftwarePlatform/hipCUB/tree/rocm-3.3.0)
|
||||
|
||||
- [AMDMIGraphX](https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/commit/d1e945dabce0078d44c78de67b00232b856e18bc)
|
||||
|
||||
|
||||
Features and enhancements introduced in previous versions of ROCm can be found in [version_history.md](version_history.md)
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 45 KiB |
84
default.xml
84
default.xml
@@ -12,74 +12,74 @@
|
||||
<remote name="gpuopen-tools"
|
||||
fetch="https://github.com/GPUOpen-Tools/" />
|
||||
|
||||
<default revision="refs/tags/roc-3.1.0"
|
||||
<default revision="refs/tags/rocm-3.3.0"
|
||||
remote="roc-github"
|
||||
sync-c="true"
|
||||
sync-j="4" />
|
||||
|
||||
<project name="ROCK-Kernel-Driver" />
|
||||
<project name="ROCT-Thunk-Interface" />
|
||||
<project name="ROCK-Kernel-Driver" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="ROCT-Thunk-Interface" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="ROCR-Runtime" />
|
||||
<project name="ROC-smi" />
|
||||
<project name="rocm_smi_lib" remote="roc-github" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="rocm-cmake" revision="1abe21258481d4cf92f5bab0ef5956636c52f735" />
|
||||
<project name="ROC-smi" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="rocm_smi_lib" remote="roc-github" />
|
||||
<project name="rocm-cmake" />
|
||||
<project name="rocminfo" />
|
||||
|
||||
<project name="rocprofiler" remote="rocm-devtools" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="roctracer" remote="rocm-devtools" revision="roc-3.1.x" />
|
||||
<project name="rocprofiler" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="roctracer" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
|
||||
<!-- 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 name="ROCm-OpenCL-Runtime" revision="refs/tags/roc-3.3.0" />
|
||||
|
||||
<project path="ROCm-OpenCL-Runtime/api/opencl/khronos/icd" name="OpenCL-ICD-Loader" remote="KhronosGroup" revision="6c03f8b58fafd9dd693eaac826749a5cfad515f8" />
|
||||
<project name="clang-ocl" />
|
||||
<!-- HCC needs to be recursively synced to get it submodules -->
|
||||
<project name="hcc" sync-s="true" revision="refs/tags/roc-hcc-3.1.0" />
|
||||
<project name="hcc" sync-s="true" />
|
||||
<project name="HCC-Example-Application" remote="rocm-devtools" revision="ffd6533305e79eed667badd3c4cdb7879a1281b8" />
|
||||
<project name="HIP" remote="rocm-devtools" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="HIP" remote="rocm-devtools" />
|
||||
<project name="HIP-Examples" remote="rocm-devtools" />
|
||||
|
||||
<!-- The following projects are all associated with the AMDGPU LLVM compiler -->
|
||||
<project name="llvm-project" path="llvm_amd-stg-open" revision="refs/tags/roc-ocl-3.1.0"/>
|
||||
<project name="ROCm-Device-Libs" revision="refs/tags/roc-ocl-3.1.0"/>
|
||||
<project name="atmi" revision="refs/tags/rocm_3.1.0" />
|
||||
<project name="llvm-project" path="llvm_amd-stg-open" revision="refs/tags/rocm-ocl-3.3.0"/>
|
||||
<project name="ROCm-Device-Libs" revision="refs/tags/rocm-ocl-3.3.0"/>
|
||||
<project name="atmi" revision="refs/tags/rocm-3.3.0" />
|
||||
<project name="ROCm-CompilerSupport" />
|
||||
<project name="rocr_debug_agent" remote="rocm-devtools" />
|
||||
<project name="rocr_debug_agent" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="rocm_bandwidth_test" />
|
||||
<project name="RCP" remote="gpuopen-tools" revision="3a49405a1500067c49d181844ec90aea606055bb" />
|
||||
|
||||
<!-- ROCm Libraries -->
|
||||
<project name="rocBLAS" remote="rocm-swplat" revision="refs/tags/rocm-3.1" />
|
||||
<project name="hipBLAS" remote="rocm-swplat" revision="refs/tags/rocm-3.1" />
|
||||
<project name="rocFFT" remote="rocm-swplat" revision="refs/tags/rocm-3.1" />
|
||||
<project name="rocRAND" remote="rocm-swplat" revision="refs/tags/3.1.0" />
|
||||
<project name="rocSPARSE" remote="rocm-swplat" revision="refs/tags/rocm-3.1" />
|
||||
<project name="hipSPARSE" remote="rocm-swplat" revision="refs/tags/rocm-3.1" />
|
||||
<project name="rocALUTION" remote="rocm-swplat" revision="refs/tags/rocm-3.1" />
|
||||
<project name="rocBLAS" remote="rocm-swplat" />
|
||||
<project name="hipBLAS" remote="rocm-swplat" />
|
||||
<project name="rocFFT" remote="rocm-swplat" revision="refs/tags/rocm-3.3" />
|
||||
<project name="rocRAND" remote="rocm-swplat" />
|
||||
<project name="rocSPARSE" remote="rocm-swplat" />
|
||||
<project name="hipSPARSE" remote="rocm-swplat" />
|
||||
<project name="rocALUTION" remote="rocm-swplat" />
|
||||
<project name="MIOpenGEMM" remote="rocm-swplat" revision="b51a12523676451bf38bfcf0506a0745e80ac64f" />
|
||||
<project name="MIOpen" remote="rocm-swplat" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="rccl" remote="rocm-swplat" revision="refs/tags/3.1.0" />
|
||||
<project name="MIVisionX" remote="gpuopen-libs" revision="755e7a08d5299a95c42def092af7c736d5eda90c" />
|
||||
<project name="rocThrust" remote="rocm-swplat" revision="refs/tags/3.1.0" />
|
||||
<project name="hipCUB" remote="rocm-swplat" revision="refs/tags/3.1.0" />
|
||||
<project name="rocPRIM" remote="rocm-swplat" revision="refs/tags/3.1.0" />
|
||||
<project name="AMDMIGraphX" remote="rocm-swplat" revision="79bfafc1b02dc276883fe5bab82eb9e481de8bc0" />
|
||||
<project name="ROCmValidationSuite" remote="rocm-devtools" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="MIOpen" remote="rocm-swplat" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="rccl" remote="rocm-swplat" />
|
||||
<project name="MIVisionX" remote="gpuopen-libs" revision="refs/tags/1.7" />
|
||||
<project name="rocThrust" remote="rocm-swplat" />
|
||||
<project name="hipCUB" remote="rocm-swplat" />
|
||||
<project name="rocPRIM" remote="rocm-swplat" />
|
||||
<project name="AMDMIGraphX" remote="rocm-swplat" revision="d1e945dabce0078d44c78de67b00232b856e18bc" />
|
||||
<project name="ROCmValidationSuite" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
|
||||
|
||||
<!-- Projects for AOMP -->
|
||||
<project name="ROCT-Thunk-Interface" path="aomp/roct-thunk-interface" remote="roc-github" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="ROCR-Runtime" path="aomp/rocr-runtime" remote="roc-github" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="hcc" path="aomp/hcc" remote="roc-github" revision="6d267cfb2895cb057e15b51a82c310bcc5f4462d" />
|
||||
<project name="ROCm-Device-Libs" path="aomp/rocm-device-libs" remote="roc-github" revision="8f441a8aff556ff02fb2f501a3df0377dd58d15d" />
|
||||
<project name="ROCm-CompilerSupport" path="aomp/rocm-compilersupport" remote="roc-github" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="rocminfo" path="aomp/rocminfo" remote="roc-github" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="atmi" path="aomp/atmi" remote="roc-github" revision="06e4962fab54b51cd5afa43b9118bca669e01fa3" />
|
||||
<project name="HIP" path="aomp/hip" remote="rocm-devtools" revision="6edce9543de8621ccb6442bec9ef7314d123cc1a" />
|
||||
<project name="aomp" path="aomp/aomp" remote="rocm-devtools" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="aomp-extras" path="aomp/aomp-extras" remote="rocm-devtools" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="flang" path="aomp/flang" remote="rocm-devtools" revision="refs/tags/roc-3.1.0" />
|
||||
<project name="llvm-project" path="aomp/llvm-project" remote="rocm-devtools" revision="refs/tags/roc-aomp-3.1.0" />
|
||||
<project name="ROCT-Thunk-Interface" path="aomp/roct-thunk-interface" remote="roc-github" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="ROCR-Runtime" path="aomp/rocr-runtime" remote="roc-github" revision="refs/tags/rocm-3.3.0" />
|
||||
<project name="hcc" path="aomp/hcc" remote="roc-github" revision="6776c83ff233bbc53d8e5e4185c2e53e400bef6f" />
|
||||
<project name="ROCm-Device-Libs" path="aomp/rocm-device-libs" remote="roc-github" revision="fea23ca22221ef2228d043d2e6b8ab00c8b8d60d" />
|
||||
<project name="ROCm-CompilerSupport" path="aomp/rocm-compilersupport" remote="roc-github" revision="d970a94c2d0f6f481a1bcbe7c9f0995443a75893" />
|
||||
<project name="rocminfo" path="aomp/rocminfo" remote="roc-github" revision="70ebe13a8932944bc8d369cc7a91d6e2c0c8e65f" />
|
||||
<project name="atmi" path="aomp/atmi" remote="roc-github" revision="b8cbdb710fee1776d8f7d8299e8acfdd62cbaaaf" />
|
||||
<project name="HIP" path="aomp/hip" remote="rocm-devtools" revision="83a42c24d8e719b29e4b965d7d71ce43fa9c07e2" />
|
||||
<project name="aomp" path="aomp/aomp" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="aomp-extras" path="aomp/aomp-extras" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="flang" path="aomp/flang" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
|
||||
<project name="llvm-project" path="aomp/llvm-project" remote="rocm-devtools" revision="refs/tags/roc-aomp-3.3.0" />
|
||||
</manifest>
|
||||
|
||||
BIN
singleinstance.png
Normal file
BIN
singleinstance.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
@@ -1,7 +1,8 @@
|
||||
## ROCm Version History
|
||||
This file contains archived version history information for the [ROCm project](https://github.com/RadeonOpenCompute/ROCm)
|
||||
|
||||
### Current ROCm Version: 3.0
|
||||
### Current ROCm Version: 3.3
|
||||
- [New features and enhancements in ROCm v3.1](#new-features-and-enhancements-in-rocm-v31)
|
||||
- [New features and enhancements in ROCm v3.0](#new-features-and-enhancements-in-rocm-v30)
|
||||
- [New features and enhancements in ROCm v2.10](#new-features-and-enhancements-in-rocm-v210)
|
||||
- [New features and enhancements in ROCm 2.9](#new-features-and-enhancements-in-rocm-29)
|
||||
@@ -25,7 +26,24 @@ This file contains archived version history information for the [ROCm project](h
|
||||
- [New Features as of ROCm 1.5](#new-features-as-of-rocm-15)
|
||||
|
||||
|
||||
### New features and enhancements in ROCm v3.0
|
||||
## New features and enhancements in ROCm v3.2
|
||||
The AMD ROCm v3.2 release was not productized.
|
||||
|
||||
## New features and enhancements in ROCm v3.1
|
||||
### Change in ROCm Installation Directory Structure
|
||||
|
||||
A fresh installation of the ROCm toolkit installs the packages in the /opt/rocm-<version> folder. Previously, ROCm toolkit packages were installed in the /opt/rocm folder.
|
||||
|
||||
### Reliability, Accessibility, and Serviceability Support for Vega 7nm
|
||||
|
||||
The Reliability, Accessibility, and Serviceability (RAS) support for Vega7nm is now available.
|
||||
|
||||
### SLURM Support for AMD GPU
|
||||
|
||||
SLURM (Simple Linux Utility for Resource Management) is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters.
|
||||
|
||||
|
||||
## New features and enhancements in ROCm v3.0
|
||||
### Support for CentOS RHEL v7.7 <a id="centos-anchor"></a>
|
||||
Support is extended for CentOS/RHEL v7.7 in the ROCm v3.0 release. For more information about the CentOS/RHEL v7.7 release, see:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user