Intel® VTune™ Amplifier XE

GPU profiling infor is incomplete



I am using the INtel Vtune 2013 version and whenever I do the profiling for Advanced hotspots with Trace the OPENCL kernels option enabled.

Attached is the screenshot for my GPU profiling. It doesn't show the info about EU array, sampler etc. Like shown in


VTune 2016 Beta fails on Hotspot and Advanced Hotspot


I am having endless problems getting the VTune 2016 Beta to profile my application. The application seg faults when run in VTune with a completely unhelpful stack trace despite debugging symbols being available. The application runs fine both through my debugger and on the command line.

I am currently trying to work through its warnings to figure out what might be the problem and one thing that sticks out is the following 

VTune itself not multi-threaded so well

In performing a Memory Bandwidth, the "Processing profile metrics and debug information" takes an exceedingly long time to complete (5 to 10 minutes). In watching the Task Manager Performance monitor it appears that only 1, or occasionally 2 threads are involved in this step. Could you look at making this phase, multi-threaded, or better multi-threaded.

Jim Dempsey

sep driver permissions

I have a customer who set up permissions on the driver 600.  Obviously this is wrong since a non-root user in the vtune group will not have permissions.

I advised to insmod with permission  660 to restrict use to those in the vtune group.  Fine.  Now their question is - does the group perms NEED WRITE permission?  Shouldn't the perms be 640 - in other words, why does a user need write permission?



I use solaris -- any way to use VTune ?

As VTune isn't ported to solaris, i'd like to know if there is any way to trick the software to identify hot spots, or for that matter, provide any information about problems I need to address.   Certainly I can cherry pick some source code and get it to compile and even run under LINUX, but that is going to be a manual process, and I'd really like to get as much code analyzed as possible, including (open)solaris kernel and driver code.

Any suggestions? 

Vtune Number of Cores Ambiguity

Hi, While running Vtune Amplifier XE 2015, I am encountering a situation which I am not able to understand. I have a program which I am running on my i5-4300U, 64bit Operating System and the program is completely unparallelized and hence according to my understanding should run on a single core. Now when I am running the Basic Hotspot Analysis for the program, I can see that only thread is being spawned but when I run Advanced Hotspot Analysis, and go to Bottum Up and choose "Core / H/W / Function / Call Stack" as my grouping, it shows my 2 cores are being used.

Debug symbols for libraries


I'm trying to add the debugging symbols for glibc to the hotspot analysis. I have installed the debug-info rpms under /usr/lib/debug/lib64 and am using:

amplxe-cl -collect hotspots -search-dir sym:rp=/usr/lib/debug/lib64 <application> <params> 

to perform the analysis. However while I have under /usr/lib/debug/lib, VTune still gives me a warning: 

Intel VTune Amplifier XE 2013. Modules of interest.


I'm a beginner in VTune. But I have some experience in AQTime 8. Now I'm using Intel VTune Amplifier XE 2013. In my opinion, it has many advantages over AQTime. There is a interesting question. In AQtime I can choose modules of my interest to profile them (before start the profiling, I mean). It's very useful, because I have to profile only one dll from the big project. Is there such a possibility in Intel VTune Amplifier XE 2013?


Intel® VTune™ Amplifier XE abonnieren