- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello. I am attempting to calculate estimated call counts using the command line instructions on this page: https://software.intel.com/en-us/articles/calculating-estimated-call-counts-with-intel-vtune-amplifier-xe-2013?language=ru. ; OS is RHEL 6.4 with kernel version 2.6.32-358.6.1.el6.x86_64.
My command line input is: mpirun -n 2 amplxe-cl -collect lightweight-hotspots -r <results directory> -knob enable-stack-collection=true -knob enable-call-counts=true -- /opt/parallel/dev/v20150/cmx/impi_3.4.4/cmx QBV_TILT_Test2
Before the application starts to execute, this produces:
amplxe: Error: PMU resource(s) currently being used by another profiling tool or process.
amplxe: Internal Error
This error occurs even immediately after a system reboot. The error does not occur when mpirun is not used. Is there a workaround for this, or is this type of collection not supported when using MPI?
Thanks for any input.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You might consider collecting from one of the mpi processes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
> mpirun -n 2 amplxe-cl -collect lightweight-hotspots -r <results directory> -knob enable-stack-collection=true -knob enable-call-counts=true -- /opt/parallel/dev/v20150/cmx/impi_3.4.4/cmx QBV_TILT_Test2
Based one your command line, analysis type was "lightweight-hotspots" - which is not used in latest product. Please try 2015 version Update 1, collection type is "advanced-hotspots", note that you have to with option "-knob collection-detail=stack-and-callcount"
About message,
> amplxe: Error: PMU resource(s) currently being used by another profiling tool or process.
Was it possible that you ran prior collection but exited abnormally? The workaround is to 1. stop running vtune process. 2. unload/reload vtune drivers 3. uninstall/reinstall vtune drivers. about 2) & 3), please go vtune/sepdk/src to find utilities.
Another note is : don't run PMU event-based sampling collections on VM.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page