Kernel and data transfer events not recorded in OpenCL applications about radeon_compute_profiler HOT 4 CLOSED

I think I made a mistake in the earlier post. If I profile an HC++ or HIP program, I can still get the kernel information. However, if I profile an OpenCL benchmark, I will not get the kernel information. It seems the main reason is that the API trace terminates early and there is some other information missing from the trace. Maybe it is because hsa_shutdown is not called? I wonder if there is a way to properly record the whole trace in an OpenCL benchmark?

from radeon_compute_profiler.

OK, I solve the problem partially by myself. I added a hsa_shutdown call at the end of the program. However, I do not think this is the legitimate solution, as the whole program is purely an OpenCL program.It there a way to avoid that?

from radeon_compute_profiler.

In current RCP builds, we don't have a relaible workaround for applications that don't call hsa_shut_down (like all OpenCL applications).

For trace profiling of an OpenCL application, you may be able to get better results if you try the latest release of RCP (the 5.3 release from here https://github.com/GPUOpen-Tools/RCP/releases)

With this release, you can try using OpenCL tracing as opposed to HSA tracing. Simply replace the "-A --hsaaqlpackettrace" with "--apitrace".

We are planning on officially supported OpenCL-on-ROCm profiling in a future RCP release, but for now, you can try the above to see if it gives better results for an OpenCL application that doesn't explicitly call hsa_shut_down.

Collecting perf counters using the OpenCL proflier (i.e. using --perfcounter) still won't work for OCL-on-ROCm applications, but this something that should work better in future releases.

from radeon_compute_profiler.

This should work better in recent RCP releases, as well as in the profiler available with ROCM 2.0 You should now be able to profile OpenCL applications using --perfcounter when running on the ROCm stack.

from radeon_compute_profiler.