-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding support for exporting results as Radeon GPU Profiler profile #107
Comments
I’m not familiar with this format and it’s unlikely that we will support writing data in that format but you might want to look into our new performance analysis tools AMDResearch/omnitrace and AMDResearch/omniperf |
Seems like it is more than possible, as indicated at GPUOpen-Tools/radeon_gpu_profiler#84 (comment) . |
Hi, @jrmadsen , @ApoKalipse-V , It seems like you added instruction tracing suppport in rocprofilerv2, that's more than appreciated! Any chance that you might support exporting the traces to RGP format so that they can be loaded in the RGP UI? |
rocprofiler v2 is no longer being actively developed for numerous reasons. There is a new rocprofiler-sdk that will be released as a beta in ROCm 6.2 and beyond that point, we do not intend to add any new features to rocprof or rocprofv2. However, considerations regarding RGP support in rocprofv3 are being discussed. |
@Epliz Do you still need assistance with this ticket? If not, please close the ticket. Thanks! |
@ppanchad-amd , I believe it is still very much relevant. |
Hi,
I have recently been using the Radeon GPU Profiler on Windows to optimize OpenCL/HIP kernels on RDNA2, and it has been very very useful thanks to its nice visualization and support of instruction tracing.
Would it be possible for you to consider adding support in rocProfiler for exporting the tracing results in the rgp format expected by the Radeon GPU profiler?
I asked your colleagues from RGP at GPUOpen-Tools/radeon_gpu_profiler#84 , and they indicated that rocm doesn't have the required support. Sounds like a challenge to you guys to add that support, don't you think?
Best regards,
Epliz
The text was updated successfully, but these errors were encountered: