Merge pull request #1028 from RadeonOpenCompute/master

revision update

README.md

@@ -1,35 +1,32 @@
-# AMD ROCm Release Notes v2.10
+# AMD ROCm Release Notes v3.1.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 v2.10 release.
+It also covers known issues and deprecated features in the ROCm v3.1 release.
 
 - [What Is ROCm?](#What-Is-ROCm)
   * [ROCm Components](#ROCm-Components)
   * [Supported Operating Systems](#Supported-Operating-Systems)
   * [Important ROCm Links](#Important-ROCm-Links)
   
-- [Whats New in This Release](#Whats-New-in-This-Release)
-  * [rocBLAS Support for Complex GEMM](#rocBLAS-Support-for-Complex-GEMM)
-  * [Support for SLES 15 SP1](#Support-for-SLES-15-SP1)
-  * [Code Marker Support for rocProfiler and rocTracer Libraries](#Code-Marker-Support-for-rocProfiler-and-rocTracer-Libraries)
+- [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)
   
-- [Fixed Issues](#Fixed-Issues)
-   * [Running TensorFlow and PyTorch Frameworks Consecutively Results in the Memory Access Fault error ](#Running-TensorFlow-and-PyTorch-Frameworks-Consecutively-Results-in-the-Memory-Access-Fault-error)
-   * [Issue with the Docker Container Environment Variable Setting](#Issue-with-the-Docker-Container-Environment-Variable-Setting)
-   * [Printf Functionality in ROCm Re-Enabled](#Printf-functionality-in-ROCm-Re-Enabled)
+  
+- [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)
+    	
  
- - [Known Issues](#Known-Issues)
-   * [Memory Access Fault Error While Running RCCL in Docker Container](#Memory-Access-Fault-Error-While-Running-RCCL-in-Docker-Container)
-   * [Workaround for Tracer Library Fails to Load on RHEL](#Workaround-for-Tracer-Library-Fails-to-Load-on-RHEL)
-   
-- [Deprecated Features](#Deprecated-Features)
-  * [ROCm OpenCL Driver](#ROCm-OpenCL-Driver)
-  * [Peer-to-Peer Bridge Driver for PeerDirect](#Peer-to-Peer-Bridge-Driver-for-PeerDirect)
   
 - [Deploying ROCm](#Deploying-ROCm)
   * [Ubuntu](#Ubuntu)
-  * [CentOS RHEL](#CentOS-RHEL)
+  * [CentOS RHEL v7](#CentOS-RHEL-v7)
+  * [SLES 15 Service Pack 1](#SLES-15-Service-Pack-1)
+
 
-- [ROCm Installation](#ROCm-Installation)
 - [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)
@@ -44,7 +41,8 @@ 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 v2.10 release:
+The following components for the ROCm platform are released and available for the v3.1
+release:
 
 • Drivers
 
@@ -58,164 +56,93 @@ You can access the latest supported version of drivers, tools, libraries, and so
 https://github.com/RadeonOpenCompute/ROCm
 
 ### Supported Operating Systems
-The ROCm v2.10.x platform is designed to support the following operating systems:
+The ROCm v3.1.x platform is designed to support the following operating systems:
 
-•	SLES 15 SP1 
 
-•	Ubuntu 16.04.6(Kernel 4.15) and 18.04.3(Kernel 5.0)
+* Ubuntu 16.04.6(Kernel 4.15) and 18.04.3(Kernel 5.3)
 
-•	CentOS 7.6 (Using devtoolset-7 runtime support)
+* CentOS v7.7 (Using devtoolset-7 runtime support)
 
-•	RHEL 7.6 (Using devtoolset-7 runtime support)
+* RHEL v7.7 (Using devtoolset-7 runtime support)
 
-For details about deploying the ROCm v2.10.x on these operating systems, see the Deploying ROCm section later in the document.
+* 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
+
 Access the following links for more information on:
-•	ROCm documentation, see 
+
+* ROCm documentation, see 
 https://rocm-documentation.readthedocs.io/en/latest/index.html
 
-•	ROCm binary structure, see
+* ROCm binary structure, see
 https://github.com/RadeonOpenCompute/ROCm/blob/master/README.md#rocm-binary-package-structure
 
-•	Common ROCm installation issues, see
+* 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
+* Instructions to install PyTorch after ROCm is installed – https://rocm-documentation.readthedocs.io/en/latest/Deep_learning/Deep-learning.html#pytorch
 
-Note: These instructions reference the rocm/pytorch:rocm2.9_ubuntu16.04_py2.7_pytorch image. However, you can substitute the Ubuntu 18.04 image listed at https://hub.docker.com/r/rocm/pytorch/tags
+Note: These instructions reference the rocm/pytorch:rocm3.0_ubuntu16.04_py2.7_pytorch image. However, you can substitute the Ubuntu 18.04 image listed at https://hub.docker.com/r/rocm/pytorch/tags
 
 
-## Whats New in This Release
+## What\'s New in This Release
 
-### rocBLAS Support for Complex GEMM
-The rocBLAS library is a gpu-accelerated implementation of the standard Basic Linear Algebra Subroutines (BLAS). rocBLAS is designed to enable you to develop algorithms, including high performance computing, image analysis, and machine learning.
-
-In the AMD ROCm release v2.10, support is extended to the General Matrix Multiply (GEMM) routine for multiple small matrices processed simultaneously for rocBLAS in AMD Radeon Instinct MI50.  Both single and double precision, CGEMM and ZGEMM, are now supported in rocBLAS.
-
-### Support for SLES 15 SP1
-In the AMD ROCm v2.10 release, support is added for SUSE Linux® Enterprise Server (SLES) 15 SP1. SLES is a modular operating system for both multimodal and traditional IT.
-
-Note: The SUSE Linux® Enterprise Server is a licensed platform. Ensure you have registered and have a license key prior to installation. Use the following SUSE command line to apply your license:
-SUSEConnect -r < Key>
-
-#### SLES 15 SP1 
-The following section tells you how to perform an install and uninstall ROCm on SLES 15 SP 1. 
-Run the following commands once for a fresh install on the operating system:
-
-	sudo usermod -a -G video  $LOGNAME
-	sudo usermod  -a -G sudo $LOGNAME
-	sudo reboot
-
-Installation
-1. Install the "dkms" package.
-
-		sudo SUSEConnect --product PackageHub/15.1/x86_64
-		sudo zypper install dkms
+### Change in ROCm Installation Directory Structure
+A fresh installation of the ROCm toolkit installs the packages in the */opt/rocm-\<version>* folder. 
 	
-2. Add the ROCm repo.
+Previously, ROCm toolkit packages were installed in the */opt/rocm* folder. 
 
-		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
+![ScreenShot](Versionchange1.png)
 
-#Run the following command once
+## Reliability, Accessibility, and Serviceability Support for Vega7nm
+The Reliability, Accessibility, and Serviceability (RAS) support for Vega7nm is now available. The support includes:
 
-	cat <<EOF | sudo tee /etc/modprobe.d/10-unsupported-modules.conf
- 	allow_unsupported_modules 1
-	EOF
-	sudo modprobe amdgpu
-	
-3. Verify the ROCm installation.
+* 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
 
-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.
-
-Uninstallation
-
-To uninstall, use the following command:
-
-	sudo zypper remove rocm-dkms rock-dkms
-	
-#Ensure all other installed packages/components are removed
-
-Note: Ensure all the content in the /opt/rocm directory is completely removed.
+## 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.
 
 
-### Code Marker Support for rocProfiler and rocTracer Libraries
-Code markers provide the external correlation ID for the calling thread. This function indicates that the calling thread is entering and leaving an external API region.
 
-• The rocProfiler library enables you to profile performance counters and derived metrics. This library supports GFX8/GFX9 and provides a hardware-specific low-level performance analysis interface for profiling of GPU compute applications. The profiling includes hardware performance counters with complex performance metrics.
+## Known Issues 
 
-• The rocTracer library provides a specific runtime profiler to trace API and asynchronous activity. The API provides functionality for registering the runtimes API callbacks and the asynchronous activity records pool support.
+### MIVision MIGraphX Installation
 
-• rocTX provides a C API for code markup for performance profiling and supports annotation of code ranges and ASCII markers.
+* 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. 
 
+### Using TensorFlow
+The TensorFlow build system requires the following additional changes to support the new installation path:
 
-## Fixed Issues
-Fixed Issues in the v2.10 Release
-### Running TensorFlow and PyTorch Frameworks Consecutively Results in the Memory Access Fault error 
-Issue: Running the TensorFlow and PyTorch frameworks in quick succession results in a Memory Access Fault error.
+* 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
 
-Resolution: This issue is resolved, and the error no longer appears.
+### HIP Compiler Dependency Issue
+If the HIP compiler has a dependency on /opt/rocm, use the following workaround: 
 
-### Issue with the Docker Container Environment Variable Setting
-Issue: Applications fail when the docker container is launched on the NUMA system without the ‘security-opt seccomp=unconfined’ setting.
+* 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.	
 
-Resolution: Configure the “–security-opt seccomp=unconfined” variable setting to avoid this issue.
+### Error Running ROC Profiler
+**Issue:** Running ROC profiler results in the following error -
+“: hip / hsa trace due to "ImportError: No module named sqlite3" error”
 
-### Printf Functionality in ROCm Re-Enabled
-Known issues with hc:printf have been addressed in ROCm v2.10. The hc:printf functionality has now been re-enabled on all supported distros.
+**Workaround:** Export the Python version before running ROC profiler: 
 
-## Known Issues
-### Memory Access Fault Error While Running RCCL in Docker Container
-Issue: The Memory Access Fault error appears while running ROCm Communication Collectives Library (RCCL) tests in the Docker container.
+	*export ROCP_PYTHON_VERSION=<python version>*
+	*ex: export ROCP_PYTHON_VERSION=python3*
 
-Resolution: While launching the Docker container to run tests related to RCCL, including PyTorch, increase the size limit for the shared memory (SHM) directory to 1 GB. To increase the size limit of the shared memory directory, enter:
-
-	“--shm-size = 1G”
-
-By default, Docker uses only16 MB of shared memory. Running a Docker container for RCCL requires you to resize the limit to 1 GB.
-
-### Workaround for Tracer Library Fails to Load on RHEL
-Issue: When running /opt/rocm/bin/rocprof --hip-trace <output filename>, a warning message is printed to console: "Tool lib "/opt/rocm/roctracer/tool/libtracer_tool.so" failed to load", and no output file is generated, on systems with RHEL distro.
-
-Resolution: You can use either of the following workarounds to fix the issue:
-
-• Run Idconfig
-
-	'SUDO LDCONFIG' 
-
- or 
- 
-• Configure LD_LIBRARY_PATH  
-
-	'EXPORT LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/OPT/ROCM/ROCTRACER/LIB'
-
-
-## Deprecated Features
-The following features are deprecated in the AMD ROCm v2.10 release. 
-
-### ROCm OpenCL Driver
-The AMD ROCm-OpenCL-Driver is now deprecated. Users should migrate to ROCm-CompilerSupport, which provides more comprehensive functionality. The compiler support repository provides various lightning compiler-related services. It currently contains a single library, the Code Object Manager (Comgr) at lib/comgr.
-
-ROCm-OpenCL-Driver will no longer be actively maintained after the v2.10 release. If your application was developed with the ROCm-OpenCL-Driver, we would encourage you to switch to the ROCm-CompilerSupport repository.
-
-### Peer-to-Peer Bridge Driver for PeerDirect
-The Peer-to-Peer bridge driver for the PeerDirect feature still works in the current release, however, it is now included as part of the ROCk kernel driver. ROCmRDMA allows third-party kernel drivers to utilize DMA access to the GPU memory. It allows a direct path for data exchange (peer-to-peer) using the standard features of PCI Express.
-
-Currently, ROCmRDMA provides the following benefits:
-
-•	Direct access to ROCm memory for 3rd party PCIe devices
-
-•	Support for PeerDirect(c) interface to offloads the CPU when dealing with ROCm memory for RDMA network stacks
 
 ## Deploying ROCm
-AMD hosts both Debian and RPM repositories for the ROCm v2.10x packages. 
+AMD hosts both Debian and RPM repositories for the ROCm v3.1.0x packages. 
 
-The following directions show how to install ROCm on supported Debian-based systems such as Ubuntu 18.04. 
+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.
 
@@ -242,13 +169,10 @@ To install from a Debian Repository:
 
      For Debian-based systems like Ubuntu, configure the Debian ROCm repository as follows:
    
-      	wget -q0 –
-     	 http://repo.radeon.com/rocm/apt/debian/rocm.gpg.key | 
+        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
 
-      	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 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. 
 
@@ -277,9 +201,10 @@ To install from a Debian Repository:
 
 6. 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
+   		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.
 
@@ -301,15 +226,15 @@ https://rocm.github.io/install_issues.html
 
 
 ### Uninstalling ROCm Packages from Ubuntu 
-To uninstall the ROCm packages from Ubuntu 1v6.04 or Ubuntu v18.04, run the following command:
+To uninstall the ROCm packages from Ubuntu v16.04 or Ubuntu v18.04.x, run the following command:
 
-	sudo apt autoremove rocm-dkms rocm-dev rocm-utils
+	sudo apt autoremove rocm-dkms 
 
 
 ### Installing Development Packages for Cross Compilation
-It is recommended that you develop and test development packages 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. 
+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 packages:
+Instead, install the following development subset of applications:
 
 	sudo apt update
 	sudo apt install rocm-dev
@@ -322,22 +247,18 @@ You can install the ROCm user-level software without installing the AMD's custom
 
 	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
+	echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"' 
+	sudo tee /etc/udev/rules.d/70-kfd.rules
 
 
+## CentOS RHEL v7 
 
-## CentOS RHEL 
-
-This section describes how to install ROCm on supported RPM-based systems such as CentOS v7.6. 
-
-Note: The following instructions may not work on unsupported RPM-based distributions. For example, Fedora may not be compatible with the rock-dkms kernel driver. You can exclude the rocm-dkms and rock-dkms packages and use the upstream kernel driver instead.
-
-Note: Although support for CentOS/RHEL v7 was added in ROCm v1.8, ROCm requires a special runtime environment provided by the RHEL Software Collections and additional dkms support packages to install and run correctly.
+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.6) for Installation
+### 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.
@@ -346,33 +267,33 @@ Note: The following steps do not apply to the CentOS installation.
 
 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
+		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 
+		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/
+  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.
+  Note: devtoolset-7 is a software collections package and is not supported by AMD.
 
-### Installing CentOS/RHEL (v7.6) for DKMS
+### Installing CentOS/RHEL (v7.7) for DKMS
 
-Use the dkms tool to install the kernel drivers on CentOS/RHEL v7.6:
+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`
 
-
-## ROCm Installation
 ### Installing ROCm 
 
 To install ROCm on your system, follow the instructions below:
@@ -380,66 +301,57 @@ 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
+		[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
+		sudo yum install rocm-dkms
 
-4.Restart the system.
-The rock-dkms component is installed and the /dev/kfd device is now available.
+4. Restart the system.The rock-dkms component is installed and the /dev/kfd device is now available.
 
-### Setting Permissions
-To configure permissions, following the instructions below:
+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:
 
-1. 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:
-
-	groups
+		groups
 	
-2. Add your user to the video (or wheel) group you will need the sudo password and can use the following command:
+6. To add your user to the video group, use the following command for the sudo password:
 
-	sudo usermod -a -G video $LOGNAME
+		sudo usermod -a -G video $LOGNAME
 	
-Note: All future users must be added to the "video" group by default. To add the users to the group, run the following commands
+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
 
-Note: The current release supports CentOS/RHEL v7.6. Before updating to the latest version of the operating system, delete the ROCm packages to avoid DKMS-related issues.
 
-3. Restart the system.
+8. Restart the system.
 
-### Testing the ROCm Installation
+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: Add the ROCm binaries in your PATH for easy implementation of the ROCm programs.
+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
+	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
 
-For more information about installation issues, see:
-https://rocm.github.io/install_issues.html
-
-
-### 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
 
 #### 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.6
+### Uninstalling ROCm from CentOS/RHEL v7.7
 To uninstall the ROCm packages, run the following command:
 
 	sudo yum autoremove rocm-dkms rock-dkms
@@ -455,19 +367,84 @@ Note: To execute ROCm-enabled applications, you will require a system installed
 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
+	echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"'  
+	sudo tee /etc/udev/rules.d/70-kfd.rules
 	
-Note: You can use this command instead of installing rocm-dkms.
+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.
 
 
-### ROCm Installation - Known Issues and Workarounds 
-#### Docker container environment variable setting
+## 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.
 
-Issue: Applications fail when a Docker container is launched on a NUMA system without --security-opt seccomp=unconfined. 
-
-Resolution: Set "--security-opt seccomp=unconfined" to fix this issue.
-
-#### Closed source components
+	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
@@ -490,7 +467,7 @@ The following example shows how to use the repo binary to download the ROCm sour
 
 	mkdir -p ~/ROCm/
 	cd ~/ROCm/
-	~/bin/repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-2.10.0
+	~/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.
@@ -499,7 +476,6 @@ Note: Using this sample code will cause the repo to download the open source cod
 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
 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.
@@ -526,7 +502,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.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.
+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.
 
 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.
@@ -536,8 +512,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.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.
+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.
 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:
@@ -558,7 +534,7 @@ GFX9 GPUs can now be run on CPUs without PCIe atomics and on older PCIe generati
 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.
+When you install your GPUs, make sure you install them in a PCIe 3.1.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.
@@ -576,7 +552,7 @@ from the list provided above for compatibility purposes.
 ##### Limited support
 
 * ROCm 2.9.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.
+* 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.1.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.
@@ -589,17 +565,17 @@ 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.0 with PCIe atomics.
+* We do not support GFX8-class GPUs (Fiji, Polaris, etc.) on CPUs that do not have PCIe 3.1.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 2.9.x platform supports the following operating systems:
+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.6 (Using devtoolset-7 runtime support)
- * RHEL 7.6 (Using devtoolset-7 runtime support)
+ * CentOS 7.7 (Using devtoolset-7 runtime support)
+ * RHEL 7.7 (Using devtoolset-7 runtime support)
 
 #### ROCm support in upstream Linux kernels
 
@@ -621,7 +597,7 @@ For users that have the option of using either AMD's or the upstreamed driver, t
 |      | 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 |
+|      | Not currently supported on kernels newer than 5.4 | Limits GPU's usage of system memory to 3/8 of system memory (before 5.6). For 5.6 and beyond, both DKMS and upstream kernels allow use of 15/16 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 |
@@ -640,14 +616,11 @@ The releases of the upstream Linux kernel support the following GPUs in ROCm:
 • Fiji, Polaris 10, Polaris 11, Vega10
 • Fiji, Polaris 10, Polaris 11, Vega10, Vega 7nm
 
-#### Supported Products
-
-• CUDA v8
 
 
 ## Machine Learning and High Performance Computing Software Stack for AMD GPU
 
-ROCm Version 2.10
+ROCm Version 3.1.0
 
 ### ROCm Binary Package Structure
 
@@ -708,33 +681,37 @@ 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
-       |--hsakmt-roct
-       |--hsakmt-roct-dev
-       |--rocm-cmake
-       |--rocm-device-libs
+       |--comgr
        |--hcc
        |--hip_base
        |--hip_doc
        |--hip_hcc
        |--hip_samples
-       |--rocm-smi
+       |--hsakmt-roct
+       |--hsakmt-roct-dev
        |--hsa-amd-aqlprofile
-       |--comgr
+       |--hsa-ext-rocr-dev
+       |--hsa-rocr-dev
+       |--rocm-cmake
+       |--rocm-device-libs
+       |--rocm-smi
+       |--rocprofiler-dev
        |--rocr_debug_agent
        \--rocm-utils
           |--rocminfo
           \--rocm-clang-ocl # This will cause OpenCL to be installed
 
   rocm-libs
-    |--rocalution
     |--hipblas
+    |--hipcub
+    |--hipsparse
+    |--rocalution
     |--rocblas
     |--rocfft
+    |--rocprim
     |--rocrand
-    |--hipsparse
-    \--rocsparse
+    |--rocsparse
+    \--rocthrust
 ```
 
 These meta-packages are not required but may be useful to make it easier to install ROCm on most systems.
@@ -751,57 +728,55 @@ 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-2.10.0)
-  - [ROCr Runtime](https://github.com/RadeonOpenCompute/ROCR-Runtime/tree/roc-2.10.0)
-  - [ROCt Thunk Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-2.10.0)  
+  - [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 Support Software
-  - [ROCm SMI](https://github.com/RadeonOpenCompute/ROC-smi/tree/roc-2.10.0)
-  - [ROCm cmake](https://github.com/RadeonOpenCompute/rocm-cmake/tree/roc-2.10.0)
-  - [rocminfo](https://github.com/RadeonOpenCompute/rocminfo/tree/roc-2.10.0)
-  - [ROCm Bandwidth Test](https://github.com/RadeonOpenCompute/rocm_bandwidth_test/tree/roc-2.10.0)
+  - [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 Development ToolChains
-  - [HCC compiler](https://github.com/RadeonOpenCompute/hcc/tree/roc-hcc-2.10.0)
-  - [HIP](https://github.com/ROCm-Developer-Tools/HIP/tree/roc-2.10.0)
-  - [ROCm Device Libraries](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-hcc-2.10.0)
+  - [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-2.10.0)
-    - [ROCm OpenCL Driver](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Driver/tree/roc-2.10.0)
-  - The ROCm OpenCL compiler, which is created from the following components:
-      - [ROCm LLVM OCL](http://github.com/RadeonOpenCompute/llvm/tree/roc-ocl-2.10.0)
-      - [ROCm LLVM HCC](http://github.com/RadeonOpenCompute/llvm/tree/roc-hcc-2.10.0)
-      - [ROCm Clang](http://github.com/RadeonOpenCompute/clang/tree/roc-2.10.0)
-      - [ROCm lld OCL](http://github.com/RadeonOpenCompute/lld/tree/roc-ocl-2.10.0)
-      - [ROCm lld HCC](http://github.com/RadeonOpenCompute/lld/tree/roc-hcc-2.10.0)
-      - [ROCm Device Libraries](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-ocl-2.10.0)
-  - [ROCM Clang-OCL Kernel Compiler](https://github.com/RadeonOpenCompute/clang-ocl/tree/roc-2.10.0)
-  - [Asynchronous Task and Memory Interface (ATMI)](https://github.com/RadeonOpenCompute/atmi/tree/rocm_2.10.0)
-  - [ROCr Debug Agent](https://github.com/ROCm-Developer-Tools/rocr_debug_agent/tree/roc-2.10.0)
-  - [ROCm Code Object Manager](https://github.com/RadeonOpenCompute/ROCm-CompilerSupport/tree/roc-2.10.0)
-  - [ROC Profiler](https://github.com/ROCm-Developer-Tools/rocprofiler/tree/roc-2.10.0)
-  - [ROC Tracer](https://github.com/ROCm-Developer-Tools/roctracer/tree/roc-2.10.x)
+    - [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)
   - [Radeon Compute Profiler](https://github.com/GPUOpen-Tools/RCP/tree/3a49405)
+  - [ROCmValidationSuite](https://github.com/ROCm-Developer-Tools/ROCmValidationSuite/tree/roc-3.1.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-2.10.0)
+    - [HIP Examples](https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/roc-3.1.0)
     
 #### ROCm Libraries
-  - [rocBLAS](https://github.com/ROCmSoftwarePlatform/rocBLAS/tree/rocm-2.10)
-  - [hipBLAS](https://github.com/ROCmSoftwarePlatform/hipBLAS/tree/rocm-2.10)
-  - [rocFFT](https://github.com/ROCmSoftwarePlatform/rocFFT/tree/rocm-2.10)
-  - [rocRAND](https://github.com/ROCmSoftwarePlatform/rocRAND/tree/2.10.0)
-  - [rocSPARSE](https://github.com/ROCmSoftwarePlatform/rocSPARSE/tree/rocm-2.10)
-  - [hipSPARSE](https://github.com/ROCmSoftwarePlatform/hipSPARSE/tree/rocm-2.10)
-  - [rocALUTION](https://github.com/ROCmSoftwarePlatform/rocALUTION/tree/rocm-2.10)
-  - [MIOpenGEMM](https://github.com/ROCmSoftwarePlatform/MIOpenGEMM/tree/6275a879)
-  - [MIOpen](https://github.com/ROCmSoftwarePlatform/MIOpen/tree/roc-2.10.0)
-  - [rocThrust](https://github.com/ROCmSoftwarePlatform/rocThrust/tree/2.10.0)
-  - [ROCm SMI Lib](https://github.com/RadeonOpenCompute/rocm_smi_lib/tree/roc-2.10.0)
-  - [RCCL](https://github.com/ROCmSoftwarePlatform/rccl/tree/2.10.0)
-  - [MIVisionX](https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/tree/1.5)
-  - [hipCUB](https://github.com/ROCmSoftwarePlatform/hipCUB/tree/2.10.0)
+  - [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)
+  - [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)
+  - [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)
 
 
 Features and enhancements introduced in previous versions of ROCm can be found in [version_history.md](version_history.md)

default.xml

@@ -12,7 +12,7 @@
     <remote name="gpuopen-tools"
             fetch="https://github.com/GPUOpen-Tools/" />
 
-    <default revision="refs/tags/roc-2.10.0"
+    <default revision="refs/tags/roc-3.1.0"
              remote="roc-github"
              sync-c="true"
              sync-j="4" />
@@ -21,56 +21,65 @@
     <project name="ROCT-Thunk-Interface" />
     <project name="ROCR-Runtime" />
     <project name="ROC-smi" />
-    <project name="rocm-cmake" />
+    <project name="rocm_smi_lib" remote="roc-github" revision="refs/tags/roc-3.1.0" />
+    <project name="rocm-cmake" revision="1abe21258481d4cf92f5bab0ef5956636c52f735" />
     <project name="rocminfo" />
 
-    <project name="rocprofiler" remote="rocm-devtools" revision="refs/tags/roc-2.10.0" />
-    <project name="roctracer" remote="rocm-devtools" revision="roc-2.10.x" />
+    <project name="rocprofiler" remote="rocm-devtools" revision="refs/tags/roc-3.1.0" />
+    <project name="roctracer" remote="rocm-devtools" revision="roc-3.1.x" />
     <!-- 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/compiler/driver" name="ROCm-OpenCL-Driver"/>
-    <project path="ROCm-OpenCL-Runtime/compiler/llvm" name="llvm" revision="refs/tags/roc-ocl-2.10.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.10.0" />
-    <project path="ROCm-OpenCL-Runtime/library/amdgcn" name="ROCm-Device-Libs" revision="refs/tags/roc-ocl-2.10.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-2.10.0" />
+    <project name="hcc" sync-s="true" revision="refs/tags/roc-hcc-3.1.0" />
     <project name="HCC-Example-Application" remote="rocm-devtools" revision="ffd6533305e79eed667badd3c4cdb7879a1281b8" />
-    <project name="HIP" remote="rocm-devtools" revision="refs/tags/roc-2.10.0" />
+    <project name="HIP" remote="rocm-devtools" revision="refs/tags/roc-3.1.0" />
     <project name="HIP-Examples" remote="rocm-devtools" />
+
     <!-- The following projects are all associated with the AMDGPU LLVM compiler -->
-    <project name="llvm" path="llvm_amd-common" revision="refs/tags/roc-ocl-2.10.0" />
-    <project name="lld" path="llvm_amd-common/lld" revision="refs/tags/roc-ocl-2.10.0" />
-    <project name="clang" path="llvm_amd-common/clang" />
-    <project name="ROCm-Device-Libs" revision="refs/tags/roc-ocl-2.10.0" />
-    <project name="atmi" revision="refs/tags/rocm_2.10.0" />
+    <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="ROCm-CompilerSupport" />
     <project name="rocr_debug_agent" remote="rocm-devtools" />
     <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-2.10" />
-    <project name="hipBLAS" remote="rocm-swplat" revision="refs/tags/rocm-2.10" />
-    <project name="rocFFT" remote="rocm-swplat" revision="refs/tags/rocm-2.10" />
-    <project name="rocRAND" remote="rocm-swplat" revision="refs/tags/2.10.0" />
-    <project name="rocSPARSE" remote="rocm-swplat" revision="refs/tags/rocm-2.10" />
-    <project name="hipSPARSE" remote="rocm-swplat" revision="refs/tags/rocm-2.10" />
-    <project name="rocALUTION" remote="rocm-swplat" revision="refs/tags/rocm-2.10" />
-    <project name="MIOpenGEMM" remote="rocm-swplat" revision="6275a879995b58a6e0b8cca7b1ad8421a5e02ade" />
-    <project name="MIOpen" remote="rocm-swplat" revision="refs/tags/roc-2.10.0" />
-    <project name="rocm_smi_lib" />
-    <project name="rccl" remote="rocm-swplat" revision="refs/tags/2.10.0" />
-    <project name="MIVisionX" remote="gpuopen-libs" revision="refs/tags/1.5" />
-    <project name="rocThrust" remote="rocm-swplat" revision="refs/tags/2.10.0" />
-    <project name="hipCUB" remote="rocm-swplat" revision="refs/tags/2.10.0" />
-    <project name="rocPRIM" remote="rocm-swplat" revision="refs/tags/2.10.0" />
+    <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="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" />
 
+    <!-- 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" />
 </manifest>

version_history.md

@@ -1,7 +1,9 @@
 ## ROCm Version History
 This file contains archived version history information for the [ROCm project](https://github.com/RadeonOpenCompute/ROCm)
 
-### Current ROCm Version: 2.10
+### Current ROCm Version: 3.0
+- [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)
 - [New features and enhancements in ROCm 2.8](#new-features-and-enhancements-in-rocm-28)
 - [New features and enhancements in ROCm 2.7.2](#new-features-and-enhancements-in-rocm-272)
@@ -23,7 +25,48 @@ 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
+### 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:
 
+[CentOS/RHEL](https://centos.org/forums/viewtopic.php?t=71657)
+
+
+### Initial distribution of AOMP 0.7-5 in ROCm v3.0 <a id="aomp-anchor"></a> 
+The code base for this release of AOMP is the Clang/LLVM 9.0 sources as of October 8th, 2019. The LLVM-project branch used to build this release is AOMP-191008. It is now locked. With this release, an artifact tarball of the entire source tree is created. This tree includes a Makefile in the root directory used to build AOMP from the release tarball. You can use Spack to build AOMP from this source tarball or build manually without Spack.
+
+For more information about AOMP 0.7-5, see: [AOMP](https://github.com/ROCm-Developer-Tools/aomp/tree/roc-3.0.0)
+
+
+### Fast Fourier Transform Updates
+The Fast Fourier Transform (FFT) is an efficient algorithm for computing the Discrete Fourier Transform. Fast Fourier transforms are used in signal processing, image processing, and many other areas. The following real FFT performance change is made in the ROCm v3.0 release:
+
+•	Implement efficient real/complex 2D transforms for even lengths.
+
+Other improvements:
+
+•	More 2D test coverage sizes.
+
+•	Fix buffer allocation error for large 1D transforms.
+
+•	C++ compatibility improvements.
+
+### MemCopy Enhancement for rocProf
+In the v3.0 release, the rocProf tool is enhanced with an additional capability to dump asynchronous GPU memcopy information into a .csv file. You can use the '-hsa-trace' option to create the results_mcopy.csv file.
+Future enhancements will include column labels.
+
+
+### New features and enhancements in ROCm v2.10
+#### rocBLAS Support for Complex GEMM
+The rocBLAS library is a gpu-accelerated implementation of the standard Basic Linear Algebra Subroutines (BLAS). rocBLAS is designed to enable you to develop algorithms, including high performance computing, image analysis, and machine learning.
+
+In the AMD ROCm release v2.10, support is extended to the General Matrix Multiply (GEMM) routine for multiple small matrices processed simultaneously for rocBLAS in AMD Radeon Instinct MI50. Both single and double precision, CGEMM and ZGEMM, are now supported in rocBLAS.
+
+#### Support for SLES 15 SP1
+In the AMD ROCm v2.10 release, support is added for SUSE Linux® Enterprise Server (SLES) 15 SP1. SLES is a modular operating system for both multimodal and traditional IT.
+
+#### Code Marker Support for rocProfiler and rocTracer Libraries
+Code markers provide the external correlation ID for the calling thread. This function indicates that the calling thread is entering and leaving an external API region.
 
 ### New features and enhancements in ROCm 2.9