David Galiffi
7bb45aba1c
- Check AMDSMI header version to fix compilation failure with v2.0 header change - Fix ROCM-SMI references in documentation and tests - Check AMDSMI library version at runtime and output in logs - Fix a possible exception occurring when an in-flight sample is outstanding while the component is shutting down.
2.3 KiB
2.3 KiB
Changelog for ROCm Systems Profiler
Full documentation for ROCm Systems Profiler is available at https://rocm.docs.amd.com/projects/rocprofiler-systems/en/latest/.
ROCm Systems Profiler 1.1.0 for ROCm 6.5
Added
- Added profiling and metric collection capabilities for VCN engine activity, JPEG engine activity and API tracing for rocDecode, rocJPEG and VA-APIs.
Changed
- Replaced ROCm-SMI backend with AMD-SMI backend for collecting GPU metrics.
Resolved issues
- Fixed application hang when enabling the RCCL backend
ROCm Systems Profiler 1.0.0 for ROCm 6.4
Added
- Support for VA-API and rocDecode tracing.
Changed
- Backend refactored to use rocprofiler-sdk rather than rocprofiler and roctracer.
Resolved issues
-
Fixed hardware counter summary files not being generated after profiling.
-
Fixed an application crash when collecting performance counters with rocprofiler.
-
Fixed interruption in config file generation.
-
Fixed segmentation fault while running rocprof-sys-instrument.
ROCm Systems Profiler 0.1.1 for ROCm 6.3.2
Resolved issues
- Fixed an error when building from source on some SUSE and RHEL systems when using the
ROCPROFSYS_BUILD_DYNINSToption.
ROCm Systems Profiler 0.1.0 for ROCm 6.3.1
Added
- Improvements to support OMPT target offload.
Resolved issues
-
Fixed an issue with generated Perfetto files.
-
Fixed an issue with merging multiple
.protofiles. -
Fixed an issue causing GPU resource data to be missing from traces of Instinct MI300A systems.
-
Fixed a minor issue for users upgrading to ROCm 6.3 from 6.2 post-rename from
omnitrace.
ROCm Systems Profiler 0.1.0 for ROCm 6.3.0
Changed
- Renamed Omnitrace to ROCm Systems Profiler.
Omnitrace 1.11.2 for ROCm 6.2.1
Known issues
- Perfetto can no longer open Omnitrace proto files. Loading the Perfetto trace output
.protofile inui.perfetto.devcan result in a dialog with the message, "Oops, something went wrong! Please file a bug." The information in the dialog will refer to an "Unknown field type." The workaround is to open the files with the previous version of the Perfetto UI found at https://ui.perfetto.dev/v46.0-35b3d9845/#!/.