Update documentation and source code for RMV v1.14

Author: ahosier

BUILD.md

@@ -33,8 +33,15 @@ This can be installed once Python is installed, as follows:
 * pip install -U sphinx
 * pip install sphinx_rtd_theme
 
-Run the python pre_build.py script in the build folder from a command prompt. If no command line options are provided, the defaults will be used (Qt 6.7.0 and Visual Studio 2022)
-
+Run the python pre_build.py script from a command prompt. If no command line options are provided, the defaults will be used (Qt 6.7.0 and Visual Studio 2022)
+```bash
+python3 build\pre_build.py
+```
+or
+```bash
+cd build
+python3 pre_build.py
+```
 Some useful options of the pre_build.py script:
 * --vs <Visual Studio version>: generate the solution files for a specific Visual Studio version. For example, to target Visual Studio 2017, add --vs 2017 to the command.
 * --qt <path>: full path to the folder from where you would like the Qt binaries to be retrieved. By default, CMake would try to auto-detect Qt on the system.
@@ -73,8 +80,9 @@ XCB libraries are required for Qt v5 and above. These can be installed by using:
 sudo apt-get install libxcb-cursor-dev
 ```
 
-Run the python pre_build.py in the build folder.
+Run the python pre_build.py script.
 ```bash
+cd build
 python3 pre_build.py
 ```
 Or run the pre_build.py script with the -qt option to specify another version of Qt. For example:

CMakeLists.txt

@@ -13,7 +13,7 @@ project(RMV)
 
 # Define version information
 set(RMV_MAJOR_VERSION 1)
-set(RMV_MINOR_VERSION 13)
+set(RMV_MINOR_VERSION 14)
 if (NOT RMV_BUGFIX_NUMBER)
     set(RMV_BUGFIX_NUMBER 0)
 endif ()
@@ -111,6 +111,7 @@ endif()
 add_subdirectory(source/parser parser)
 add_subdirectory(source/backend backend)
 add_subdirectory(source/frontend frontend)
+add_subdirectory(test/source/backend_test backend_test)
 
 # Group external dependency targets into folder
 IF(WIN32)

README.md

@@ -36,8 +36,8 @@ The Radeon Memory Visualizer (RMV) is a software tool that will allow users to a
 ## Supported Operating Systems
 * Windows® 10
 * Windows® 11
-* Ubuntu 22.04 LTS (Vulkan only)
-* Ubuntu 24.04 LTS (Vulkan only)
+* Ubuntu® 24.04 LTS (Vulkan only)
+  * With the introduction of 25.20-based Linux drivers, the AMDVLK driver is no longer included in the amdgpu-pro driver package. This is a result of the AMDVLK open-source project being discontinued as mentioned [here](https://github.com/GPUOpen-Drivers/AMDVLK/discussions/416). Instead, the RADV open-source Vulkan® driver is installed by default. Consequently, the Radeon Developer Panel does not support capturing data from Vulkan applications when using these newer driver releases. To analyze Linux Vulkan workloads with Radeon GPU Profiler (RGP), Radeon Raytracing Analyzer (RRA), or Radeon Memory Visualizer (RMV), users can opt for a 25.10-based driver. Alternatively, analysis can be performed using the data capture mechanism integrated within the RADV driver, although this method is not supported by the Radeon Developer Panel. For more information on configuring RADV, refer to the environment variable documentation, specifically the [MESA_VK_TRACE_* environment variables](https://docs.mesa3d.org/envvars.html#envvar-MESA_VK_TRACE) which can be utilized for enabling and configuring tracing.
 
 Note: Before running RDP and capturing an RMV memory trace on Linux, be sure to make the necessary configuration changes by running the RDP setup.sh script each time the machine is rebooted. For more information, see the RDP documentation.
 

RELEASE_NOTES.txt

@@ -1,11 +1,10 @@
-Radeon™ Memory Visualizer V1.13 06/17/2025
-------------------------------------------
+Radeon™ Memory Visualizer V1.14
+-------------------------------
 
-V1.13 Changes
+V1.14 Changes
 ------------------------------------
-1) Optimize performance for the Allocation overview pane, helpful when allocations contain thousands of resources and/or aliasing is heavily used.
-2) Allow resource properties to be copied to the clipboard in the Resource details pane.
-3) Bug/stability fixes.
+1) UI support for work graph backing memory.
+2) Bug/stability fixes.
 
 Known Issues
 ------------------------------------
@@ -20,11 +19,18 @@ Known Issues
 (7) If a memory dump is created by shutting down the application being traced and there are a large number of resource names, some names may not be included in the RMV file.  The work-around is to use the Dump trace button in the Radeon Developer Panel and wait for the button to be disabled before shutting down the application.  This gives the buffered names a chance to be processed.
 (8) The Shader core clock frequency and Video memory clock frequency for memory traces captured on Linux may be incorrectly displayed as 0 Mhz.
 (9) The Device name may be blank for memory traces captured on Linux with some APUs.
-(10) Installations of Ubuntu 20.04 or newer may have the RADV open source Vulkan® driver installed by default on the system. As a result, after an amdgpu-pro driver install, the default Vulkan ICD may be the RADV ICD. In order to capture a memory trace, Vulkan applications must be using the amdgpu-pro Vulkan ICD. The default Vulkan ICD can be overridden by setting the following environment variable before launching a Vulkan application: VK_ICD_FILENAMES=/etc/vulkan/icd.d/amd_icd64.json
+(10) With the introduction of 25.20-based Linux drivers, the AMDVLK driver is no longer included in the amdgpu-pro driver package. This is a result of the AMDVLK open-source project being discontinued as mentioned here (https://github.com/GPUOpen-Drivers/AMDVLK/discussions/416). Instead, the RADV open-source Vulkan® driver is installed by default. Consequently, the Radeon Developer Panel does not support capturing data from Vulkan applications when using these newer driver releases. To analyze Linux Vulkan workloads with Radeon GPU Profiler (RGP), Radeon Raytracing Analyzer (RRA), or Radeon Memory Visualizer (RMV), users can opt for a 25.10-based driver. Alternatively, analysis can be performed using the data capture mechanism integrated within the RADV driver, although this method is not supported by the Radeon Developer Panel. For more information on configuring RADV, refer to the environment variable documentation, specifically the MESA_VK_TRACE_* environment variables (https://docs.mesa3d.org/envvars.html#envvar-MESA_VK_TRACE) which can be utilized for enabling and configuring tracing.
+(11) When using a 25.10-based driver or older: Installations of Ubuntu 20.04 or newer may have the RADV open source Vulkan driver installed by default on the system. As a result, after an amdgpu-pro driver install, the default Vulkan ICD may be the RADV ICD. In order to capture a profile, Vulkan applications must be using the amdgpu-pro Vulkan ICD. The default Vulkan ICD can be overridden by setting the following environment variable before launching a Vulkan application: VK_ICD_FILENAMES=/etc/vulkan/icd.d/amd_icd64.json.
 
 Release Notes History
 ------------------------------------
 
+V1.13 Changes
+------------------------------------
+1) Optimize performance for the Allocation overview pane, helpful when allocations contain thousands of resources and/or aliasing is heavily used.
+2) Allow resource properties to be copied to the clipboard in the Resource details pane.
+3) Bug/stability fixes.
+
 V1.12 Changes
 ------------------------------------
 1) Support for AMD Radeon RX 9000 series GPUs.

build/dependency_map.py

@@ -21,8 +21,10 @@
 # Define a set of dependencies that exist as separate git projects.
 # each git dependency has a desired directory where it will be cloned - along with a commit to checkout
 git_mapping = {
-    github_tools + "qt_common"                 : ["../external/qt_common",         "v4.3.0", True],
-    github_tools + "system_info_utils"         : ["../external/system_info_utils", "v2.1",   True],
-    github_tools + "update_check_api"          : ["../external/update_check_api",  "v2.1.1", True],
-    github_root  + "GPUOpen-Drivers/libamdrdf" : ["../external/rdf",               "v1.4.0", True],
+    github_tools + "qt_common"                 : ["../external/qt_common",          "v4.4.0",  True],
+    github_tools + "system_info_utils"         : ["../external/system_info_utils",  "v2.1",    True],
+    github_tools + "update_check_api"          : ["../external/update_check_api",   "v2.1.1",  True],
+    github_root  + "GPUOpen-Drivers/libamdrdf" : ["../external/rdf",                "v1.4.2",  True],
+    github_root  + "nlohmann/json"             : ["../external/third_party/json",   "v3.9.1",  True],
+    github_root  + "catchorg/Catch2"           : ["../external/third_party/catch2", "v2.13.6", True],
 }

build/pre_build.py

@@ -35,6 +35,7 @@
 else:
     can_fetch = False
 
+
 # to allow the script to be run from anywhere - not just the cwd - store the absolute path to the script file
 script_root = os.path.dirname(os.path.realpath(__file__))
 
@@ -177,6 +178,7 @@ def check_qt_path(qt_root, qt_root_arg, qt_arg):
     if args.platform == "x86":
         cmake_output_dir += args.platform
 
+
 # Clean all files generated by this script or the build process
 if (args.clean):
     log_print ("Cleaning build ...\n")
@@ -210,6 +212,7 @@ def check_qt_path(qt_root, qt_root_arg, qt_arg):
     qt_expanded_root = os.path.expanduser(args.qt_root)
     qt_found,qt_path = check_qt_path(qt_expanded_root, args.qt_root, args.qt)
 
+
     if qt_found == False:
         log_error_and_exit(qt_path)
 
@@ -270,6 +273,7 @@ def generate_config(config):
                 elif args.toolchain == "2017":
                     cmake_args.extend(["-Tv141"])
 
+
     if sys.platform.startswith('linux'):
         if args.qt_system:
             cmake_args.extend(["-DQT_SYSTEM:BOOL=TRUE"])
@@ -292,6 +296,7 @@ def generate_config(config):
     if sys.platform == "darwin":
         cmake_args.extend(["-DNO_APP_BUNDLE=" + str(args.no_bundle)])
 
+
     if args.vscode:
         # Generate data into VSCode Settings file
 
@@ -392,6 +397,7 @@ def generate_config(config):
         p.wait()
         sys.stdout.flush()
 
+
         if (args.package):
             if sys.platform == "win32":
                 cmake_args = ["cpack", "-G", "ZIP"]

cmake/devtools_qt_helper.cmake

@@ -73,7 +73,8 @@ if (Qt6_DIR)
                     )")
         else()
             # Generate deployment script of Qt binaries and plugins
-            if (QT_VERSION_MAJOR EQUAL 6 AND QT_VERSION_MINOR GREATER_EQUAL 5)
+            if (QT_VERSION_MAJOR GREATER 6 OR (QT_VERSION_MAJOR EQUAL 6 AND QT_VERSION_MINOR GREATER_EQUAL 5))
+                # Qt 6.5 or above.
                 qt_generate_deploy_app_script(TARGET ${PROJECT_NAME}
                         OUTPUT_SCRIPT deploy_script
                         NO_UNSUPPORTED_PLATFORM_ERROR
@@ -83,6 +84,7 @@ if (Qt6_DIR)
                 qt_generate_deploy_app_script(TARGET ${PROJECT_NAME}
                         FILENAME_VARIABLE deploy_script
                         NO_UNSUPPORTED_PLATFORM_ERROR
+                        NO_TRANSLATIONS
             )
             endif()
         endif()

documentation/source/conf.py

@@ -54,9 +54,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = u'1.13.0'
+version = u'1.14.0'
 # The full version, including alpha/beta/rc tags.
-release = u'1.13.0'
+release = u'1.14.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

documentation/source/index.rst

@@ -46,10 +46,10 @@ Supported graphics APIs, RDNA hardware, and operating systems
 
 -  Windows® 10/11
 
--  Ubuntu® 22.04 LTS (Vulkan only)
-
 -  Ubuntu® 24.04 LTS (Vulkan only)
 
+ -  With the introduction of 25.20-based Linux drivers, the AMDVLK driver is no longer included in the amdgpu-pro driver package. This is a result of the AMDVLK open-source project being discontinued as mentioned `here <https://github.com/GPUOpen-Drivers/AMDVLK/discussions/416>`_. Instead, the RADV open-source Vulkan® driver is installed by default. Consequently, the Radeon Developer Panel does not support capturing data from Vulkan applications when using these newer driver releases. To analyze Linux Vulkan workloads with Radeon GPU Profiler (RGP), Radeon Raytracing Analyzer (RRA), or Radeon Memory Visualizer (RMV), users can opt for a 25.10-based driver. Alternatively, analysis can be performed using the data capture mechanism integrated within the RADV driver, although this method is not supported by the Radeon Developer Panel. For more information on configuring RADV, refer to the environment variable documentation, specifically the `MESA_VK_TRACE_* environment variables <https://docs.mesa3d.org/envvars.html#envvar-MESA_VK_TRACE>`_ which can be utilized for enabling and configuring tracing.
+
 
 DISCLAIMER
 ----------