I am running GPA 2012 R5 on an Ivy Bridge machine with Intel HD 2500 graphics (OS is windows 7 and latest driver is installed). When I run the GPA monitor even on the sample executable provided, no trace file is being generated. In the Documents\GPA_2012_R5\Logs folder, a log file is generated with a sample of its contents following. What could be the issue?
[TAL][WIN pid=2984][ 10c4] Export "__itt_pause" is not found.
[TAL][WIN pid=2984][ 10c4] Export "__itt_resume" is not found.
[TAL][WIN pid=2984][ 10c4] Export "__itt_thread_ignore" is not found.
[TAL][WIN pid=2984][ 10c4] Export "__itt_sync_createA" is not found.
[TAL][WIN pid=2984][ 10c4] Export "__itt_sync_createW" is not found.
Thanks in advance,
- What happens when you try to create a trace file? Does Intel GPA print any message (either success or error), or does it look like Intel GPA didn't do anything at all?
- Can you create a frame capture file OK, or does this only happen with trace capture files?
- Is 2012 R5 the only version that fails? In other words, did you upgrade from a previous version that worked, or is 2012 R5 the only version that you've been testing.
- How did you start creating the trace capture file? Was it via a trigger (such as frame number = 100), or did you use a keyboard shortcut for this (such as Ctrl-Shift-T)?
It sounds like some good news in that you can see some information when using the Intel GPA sample application. However, it looks like there are still some issues when trying to see traces using your sample OpenCL* application.
I think the issue may be that other settings are required to use the two tools together. For example, I saw a note in our online help for using OpenCL* with Intel GPA (http://software.intel.com/sites/products/documentation/gpa/12.5/index.htm and search for "OpenCL"):
For profiling OpenCL* applications, install the Intel® SDK for OpenCL* Applications and use the OpenCL* Profiler to collect traces. You can collect additional CPU tracing information by setting the CL_GPA_CONFIG_ENABLE_API_TRACING environment variable to TRUE. This will enable you to (1) view detailed timing information about your OpenCL* workload by inspecting the time the host API took to execute, and (2) know when certain parts of the host API took more time to execute.
There's also a separate section in the OpenCL* online help as well that talks about using Intel GPA and OpenCL* together: http://software.intel.com/sites/landingpage/opencl/user-guide/hh_goto.htm#Tuning_with_the_Intel_Grap...
Hopefully the two notes above help resolve the issue about not seeing the trace data, but you should be able to get both CPU and GPU activity in Intel GPA Platform Analyzer. However, due to the way Intel GPA System Analyzer works you won't be able to directly observe OpenCL* kernel activity.
As to your issue about the crash of the Intel GPA Monitor, this shouldn't happen (crashes are never good!) -- do you have more details on this specific issue?