GPUOpen-Archive/CodeXL

Unable to gather profile data: Perf Counters

rNoz opened this issue · 1 comments

rNoz commented

In Linux I couldn't even install the AMD catalyst software for my GPUs. The only purpose to use the proprietary software is to use CodeXL or use OpenCL 1.2... but no luck. Bad for AMD.

So, now I am in Windows. It is not free of problems, but at least I can:

  • Run CodeXL Timeline Trace in CPU + GPU if I use Adrenalin 18.7.1.
  • Run CodeXL Timeline Trace in GPU if I use Adrenaline 20.2

The problem is that I cannot run GPU Performance Counters in CodeXL. It says:

  • Active project is not an OpenCL program: FALSE
  • Active project is an OpenCL program but did not enqueue any kernels: FALSE
  • Active project is an OpenCL Program, but it did not enqueue any kernels listed in Profile Specific Kernels section: FALSE, since I try with that field empty (thus, any kernel) or with the kernel itself (eg. saxpy).
  • Active project does not compile or run properly: FALSE, since I run it in the cmd.exe properly.
  • You do not have write access to the profile output dir: FALSE, since I can run Timeline Trace.

I tried as an User and as an Admin (run CodeXL as administrator).

Also, I tried with both versions of the driver (Adrenaline 18.7.1 and 20.2-latest)

Finally, my GPUs:

  • R7 370
  • 7770
  • R7 240

Any clue? I don't know what I can try now... apart from inspecting CodeXL to find why/where is this MsgBox/abort window generated.

rNoz commented

I found the error and a "temporary" solution for this issue, as I wrote here: GPUOpen-Tools/radeon_compute_profiler#35

Personal opinion: these projects (CodeXL/rcprof) seem dead based on the issue responses, dates of the latest bugfixes/releases and the AMD forums.

I think AMD should care more about their products and softwares if they plan to compete against Nvidia or Intel.
No makes sense that we struggle to use their tools or that it is impossible to make OpenCL work with proprietary drivers (to be used with CodeXL) in Linux for my 3 AMD GPU cards, or that the open-source OpenCL implementations are in most cases better than the proprietary.
I like the AMD policy in favor of Open Source compared with their competition, but it is so problematic (and I am a researcher/developer) that I seriously consider buying a non-AMD device in the future.

  • 👍1