So actual cycles forline>=samples * SAV_value, but < (samples+1) * SAV_value.
You have to use "-g"option to build your code, sodebugging symbols and source line info will be generated.
For displaying performance dataofsome functionson kernel module, please refer to this article.
Given your circumstances, I would try collecting and doing symbol mapping on the non-GUI machine (a process in the helps called "finalization") and then try migrating that project result to the machine that can run the GUI. You'll probably need to have a lot of the same files in the same places and VTune Amplifier, in an attempt to avoid displaying invalidated data, can be persnickety regarding file time stamps: be sure the objects and symbols are newer than the sources. I've never tried expanding to source for a driverbut there should be a way to do it. Use the command line switch "-search-dir" to identify the location of the driver symbols and source during the amplxe-cl collection run, and then try copying the result directory produced by thatto the GUI-capable machine (whichhas the same source and symbol-loadedbinaries in the same places) and open the result file there. Not having tried it, I can't guarantee this will work, but it should have the best chance of working in the environment you describe.