From 6b93df5843cc424eed627bf1c2ca007c57b8e6ff Mon Sep 17 00:00:00 2001 From: Pratik Basyal Date: Thu, 24 Apr 2025 12:34:00 -0400 Subject: [PATCH] Broken link fix to How-to: Configuring Runtime Options [amd-staging] (#180) * Update to KOKKOS_TOOLS_LIBS env var (#69) * Broken link fixed --------- Co-authored-by: Maarten Arnst [ROCm/rocprofiler-systems commit: 16745948dec824c7c9f13c19bde489e915a0f0de] --- .../docs/how-to/configuring-runtime-options.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/rocprofiler-systems/docs/how-to/configuring-runtime-options.rst b/projects/rocprofiler-systems/docs/how-to/configuring-runtime-options.rst index 5006d24d67..59c1b9099e 100644 --- a/projects/rocprofiler-systems/docs/how-to/configuring-runtime-options.rst +++ b/projects/rocprofiler-systems/docs/how-to/configuring-runtime-options.rst @@ -236,7 +236,7 @@ For example, the following is a valid configuration: Supported values for ``ROCPROFSYS_AMD_SMI_METRICS`` are: ``busy``, ``temp``, ``power``, ``vcn_activity``, ``mem_usage``, ``jpeg_activity``. API tracing is configured with the ``ROCPROFSYS_ROCM_DOMAINS`` setting. The domains are used to filter the events that are captured during profiling. -Supported values for this setting are those supported by ROCprofiler-SDK, which are returned by the API ``get_callback_tracing_names()`` and ``get_buffer_tracing_names()``. See the `ROCprofiler-SDK developer API documentation `_ to learn more about ROCprofiler-SDK APIs. +Supported values for this setting are those supported by ROCprofiler-SDK, which are returned by the API ``get_callback_tracing_names()`` and ``get_buffer_tracing_names()``. See the `ROCprofiler-SDK developer API documentation `_ to learn more about ROCprofiler-SDK APIs. Use the following command to view the available domains: .. code-block:: shell