You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit eb6dd11
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ The Radeon Memory Visualizer (RMV) is a software tool that will allow users to a
6
6
7
7
## Getting Started
8
8
9
-
1. Install the latest AMD Video/display driver. Completely remove previously installed drivers. On Windows, the driver installation factory reset option should be used.
9
+
1. Install the latest AMD video/display driver. Completely remove previously installed drivers. On Windows, the driver installation factory reset option should be used.
10
10
2. Unzip/Untar the download file. The directory includes the following:
11
11
* Radeon Developer Service (RDS)
12
12
* Radeon Developer Service CLI (RDS headless)
@@ -17,7 +17,7 @@ The Radeon Memory Visualizer (RMV) is a software tool that will allow users to a
17
17
* Start your application. The Radeon Developer Panel will switch to the "APPLICATIONS" tab. The overlay window in the top left of the application being traced will show if RMV tracing is enabled. If not, make sure the app is running in Vulkan® or DirectX®12 mode.
18
18
* When tracing is complete, click on the 'Memory Trace' tab and click "Dump Trace" or close your application (in this case, the trace will be dumped automatically).
19
19
4. For further detailed instructions, please see the documentation provided in the Help. Help can be found in the following locations:
20
-
* Help web pages exist in the "help" sub directory
20
+
* Help web pages exist in the "help" subdirectory
21
21
* Help web pages can be accessed from the **Help** button (?) in the Developer Panel
22
22
* Help web pages can be accessed from the Welcome screen in the Radeon Memory Visualizer, or from the **Help** menu
23
23
* The documentation is hosted publicly at:
@@ -42,7 +42,7 @@ The Radeon Memory Visualizer (RMV) is a software tool that will allow users to a
42
42
43
43
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.
44
44
45
-
## Required hardware for SAM (Smart access memory) support
45
+
## Required hardware for SAM (Smart Access Memory) support
46
46
* AMD Radeon RX 6000 series or higher
47
47
* AMD Ryzen 5000 and higher series processors with AMD RDNA Architecture Graphics
Copy file name to clipboardExpand all lines: RELEASE_NOTES.txt
+23-18Lines changed: 23 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -1,33 +1,38 @@
1
-
Radeon™ Memory Visualizer V1.15
2
-
-------------------------------
1
+
Radeon™ Memory Visualizer V1.15.1
2
+
---------------------------------
3
3
4
-
V1.15 Changes
4
+
V1.15.1 Changes
5
5
------------------------------------
6
-
1) Option to view memory as binary or decimal.
7
-
2) Dimension, mip level and format parameters added to the resource tables for texture resources.
8
-
3) Mip level slider added to resource tables.
9
-
4) Allow resource tables to be saved to disk.
10
-
5) Bug/stability fixes.
6
+
1) Resource Overview pane now uses all available space to display resources.
7
+
2) Bug/stability/security fixes.
11
8
12
9
Known Issues
13
10
------------------------------------
14
11
15
12
(1a) More than a single active device at a time within a single application is not supported. In this case, only the first device will be traced.
16
-
(1b) More than a single Vulkan/DX12 process at a time is not supported. Only the first started application will be traced.
13
+
(1b) More than a single Vulkan/DX12 process at a time is not supported. Only the first started application will be traced.
17
14
(2) In the Snapshots|Resource details pane, Physical memory mapped events may be shown before virtual allocate events.
18
15
(3) Some UI elements do not rescale properly when the OS's DPI scale settings are dynamically changed, or when dragging RMV between two monitors with different DPI scales. Close and re-open RMV to view at proper sizes.
19
16
(4) Running multiple instances of the Radeon Developer Panel is not supported.
20
-
(5) Sparse texture are not fully supported.
17
+
(5) Sparse textures are not fully supported.
21
18
(6) When tracing an application that uses a launcher, or an application that creates multiple devices, it is possible that more than one trace file will be written to disk. In the case of the launcher, adding the launcher's executable name to the Blocked applications list in the Radeon Developer Panel should prevent multiple trace files. Restarting the Radeon Developer Panel may be required before attempting to trace again.
22
-
(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.
23
-
(8) The Shader core clock frequency and Video memory clock frequency for memory traces captured on Linux may be incorrectly displayed as 0 Mhz.
19
+
(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.
20
+
(8) The Shader core clock frequency and Video memory clock frequency for memory traces captured on Linux may be incorrectly displayed as 0 MHz.
24
21
(9) The Device name may be blank for memory traces captured on Linux with some APUs.
25
22
(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.
26
-
(11) When using a 25.10-based driver or older: Installations of Ubuntu 20.04 or newer may have the RADV opensource 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.
23
+
(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.
27
24
28
25
Release Notes History
29
26
------------------------------------
30
27
28
+
V1.15 Changes
29
+
------------------------------------
30
+
1) Option to view memory as binary or decimal.
31
+
2) Dimension, mip level and format parameters added to the resource tables for texture resources.
32
+
3) Mip level slider added to resource tables.
33
+
4) Allow resource tables to be saved to disk.
34
+
5) Bug/stability fixes.
35
+
31
36
V1.14 Changes
32
37
------------------------------------
33
38
1) UI support for work graph backing memory.
@@ -81,7 +86,7 @@ V1.7 Changes
81
86
2) Support for loading Radeon GPU Detective crash dump files.
82
87
3) Resource naming and implicit buffer filtering made more reliable in DX12.
83
88
4) Support for hours added (formatted as "H:MM:SS.clk_cycles" and included with the CTRL+T time-cycling shortcut keys).
84
-
5) System memory type added to device configuration pane (e.g. DDR4).
89
+
5) System memory type added to device configuration pane (e.g., DDR4).
85
90
6) Bug/stability fixes.
86
91
87
92
V1.6.1 Changes
@@ -97,7 +102,7 @@ V1.6 Changes
97
102
98
103
V1.5 Changes
99
104
------------------------------------
100
-
1) Keyboard shortcuts added for all panes on the Welcome and Settings lists. Some keys have also been remapped to avoid conflict with the Adrenaline software. See the documentation or keyboard shortcuts pane for details.
105
+
1) Keyboard shortcuts added for all panes on the Welcome and Settings lists. Some keys have also been remapped to avoid conflict with the Adrenalin software. See the documentation or keyboard shortcuts pane for details.
101
106
2) Bug fixes.
102
107
103
108
V1.4.1 Changes
@@ -110,20 +115,20 @@ V1.4 Changes
110
115
111
116
1) Support added for traces taken from systems with LPDDR4/5 & DDR5 memory.
112
117
2) Support for traces taken with Smart Access Memory (SAM) enabled.
113
-
3) Bugs/stability fixes.
118
+
3) Bug/stability fixes.
114
119
115
120
V1.3 Changes
116
121
------------------------------------
117
122
118
123
1) DX12 Resource naming.
119
-
2) Bugs/stability fixes.
124
+
2) Bug/stability fixes.
120
125
121
126
V1.2 Changes
122
127
------------------------------------
123
128
124
129
1) Add tooltips showing resource details on the Resource overview pane.
125
130
2) Add range-based address searching for resource tables.
0 commit comments