Intel® Parallel Amplifier provides libittnotify.dll/libittnotify.h which can notify User Synchronization Objects to Intel® Parallel Amplifier at runtime.

Here is a test case: the function is used by many threads, and each thread computes value in local variable "lpot" in loop, and accumulates local value into global variable "pot"

1)  for( i=start; i<end; i++ ) {

      for( j=0; j<i-1; j++ ) {

        distx = pow( (r[0][j] - r[0][i]), 2 );

        disty = pow( (r[1][j] - r[1][i]), 2 );

        distz = pow( (r[2][j] - r[2][i]), 2 );

        dist = sqrt( distx + disty + distz );     

       lpot += 1.0 / dist;

      }

   }

   EnterCriticalSection(&cs);

      pot += lpot;

   LeaveCriticalSection(&cs);

In this implementation, time comsumption of sys-obj "CRITICAL_SECTION cs;" will be analyzed in the result of Intel® Parallel Amplifer

2) for( i=start; i<end; i++ ) {

      for( j=0; j<i-1; j++ ) {

        distx = pow( (r[0][j] - r[0][i]), 2 );

        disty = pow( (r[1][j] - r[1][i]), 2 );

        distz = pow( (r[2][j] - r[2][i]), 2 );

        dist = sqrt( distx + disty + distz );     

        lpot += 1.0 / dist;

      }

   }

  while (!spin) {

          spin = 1;

          pot += lpot;

   }

   spin = 0;

In this implementation, time consumption of user's "spin" will NOT be analyzed

3)  for( i=start; i<end; i++ ) {

      for( j=0; j<i-1; j++ ) {

        distx = pow( (r[0][j] - r[0][i]), 2 );

        disty = pow( (r[1][j] - r[1][i]), 2 );

        distz = pow( (r[2][j] - r[2][i]), 2 );

        dist = sqrt( distx + disty + distz );     

        lpot += 1.0 / dist;

      }

   }

   sync_prepare(&spin);

   while (!spin) {

          spin = 1;

          sync_acquired(&spin);

          pot += lpot;

   }

   sync_releasing (&spin);

   spin = 0;

In this implementation, time consumption of user's "spin" will be analyzed

Note that the user can get libittnotify's APIs as below

#include <ittnotify.h>

......

typedef void (*itt_notify_sync_prepare)(void *);

typedef void (*itt_notify_sync_acquired)(void *);

typedef void (*itt_notify_releasing)(void *);

HMODULE hMod;

itt_notify_sync_prepare sync_prepare;

itt_notify_sync_acquired sync_acquired;

itt_notify_releasing sync_releasing;

......

  hMod = LoadLibrary("libittnotify.dll");

   sync_prepare = (itt_notify_sync_prepare) GetProcAddress(hMod, "__itt_notify_sync_prepare");

   sync_acquired = (itt_notify_sync_acquired) GetProcAddress(hMod, "__itt_notify_sync_acquired");

   sync_releasing = (itt_notify_releasing) GetProcAddress(hMod, "__itt_notify_sync_releasing");

Finally the user can get Intel® Parallel Amplifier (Locks and Waits) Result -

Case 1)      Hardware PMU event-based sampling analysis (User-defined)

Case 2)      User-mode sampling and tracing analysis (User-defined)

For case 1), please refer to "Event Configuration from the Command Line" article to know How-to do this analysis. The article documents information about configuring those events.

For case 2), (User-mode sampling and tracing analysis)  - when the user runs user-mode sampling and tracing analysis in command line and requests to change sample interval from 10s (default value) to 20s, with "-collect-with runss", the user should specify collectSamplesMode explicitly (with either "stack" or "nostack"). Here is an example:

$ amplxe-cl -collect-with runss -knob interval=20 --knob collectSamplesMode=stack -- ./primes.icc 
Determining primes from 1 - 100000 
Found 9592 primes 
Using result path `/home/peter/problem_report/r012runss' Executing actions 75 % 
Generating a report 
Summary ------- 
Elapsed Time: 0.992 CPU Time: 2.290 Executing actions 100 % done 
$ amplxe-cl -report hotspots -group-by function 
Using result path `/home/peter/problem_report/r012runss' Executing actions 75 % 
Generating a report 
Function Module CPU Time 
---------- ---------- -------- 
findPrimes primes.icc 2.290 Executing actions 100 % done 

 
If collectSamplesMode is not specified explicitly (with either "stack" or "nostack"), users may see the error message below. The root-cause is - with "-collect-with runss", the user should specify collectSamplesMode explicitly (with "stack" or "nostack").

$ amplxe-cl -collect-with runss-knob interval=20 -- ./primes.icc 
Determining primes from 1 - 100000 
Found 9592 primes 
Using result path `/home/peter/problem_report/r011runss' Executing actions 75 % 
Generating a report 
Summary ------- 
Elapsed Time: 0.978 Executing actions 100 % done 
$ amplxe-cl -report hotspots -group-by function 
Using result path `/home/peter/problem_report/r011runss' Executing actions 75 % 
Generating a report Result directory does not contain CPU samples. 
Executing actions 100 % done Error: Error 0x40000024 (Reporter error)

When a user adopts stack-sampling collector analysis such as Hotspots, Concurrency or Locks Waits, Call Stack info will be displayed in Bottom-up report. (OS timer only)

Call Stack tree lists all call sequences (stacks) which called hot functions. Call Stacks from different threads are aggregated together for view type "Function - Call Stack", or Call Stacks can be displayed respectively for different thread for view type "Thread - Function - Call Stack".

Here is the Hotspot result after running a single thread application. Hot function foo_data_collected() has only one Stack wmain() in Bottom-up tree, but Call Stack pane indicates there are two Stacks.

First stack is wmain() from "test_itt_api.cpp:32", let's see what second stack is?

Second stack is wmain() from "test_itt_api.cpp:24". That means wmain() calls hot function foo_data_collected() from different source lines in same function. The bottom-up tree shown in the Bottom-up pane aggregates these stacks in one line. But the Call Stack pane shows each as a separate stack

Problem : 
Only one version of Intel® Parallel Studio can be integrated with any one version of Microsoft Visual Studio* at a time. Therefore, if you have Intel Parallel Studio installed on your system and then install a different version along side of it, the newly installed version will be integrated into Visual Studio in place of the previously installed version - this means you will see the newly installed Parallel Studio toolbars, menu items, etc. 

You can control which version of Intel Parallel Studio you use with a particular Visual Studio by performing the steps outlined below.

Environment: 
Windows systems with Microsoft Visual Studio 2005, 2008, and/or 2010 installed along with multiple versions of Intel Parallel Studio.

Root Cause: 
Limit of one Parallel Studio integrated with a version of Visual Studio.

Resolution: 
You will need to change the version of Parallel Studio that is integrated with a particular version of Visual Studio.  This will need to be done for each component of the Parallel Studio that you have installed. 

1. Begin by removing the integration from the version that is currently integrated.

For  Intel Parallel Amplifier or Intel Parallel Inspector, start by opening the Command Prompt window for the version of Parallel Studio you wish to disable. For example:

Now invoke the appropriate script to disable the integration:

For Intel Parallel Composer use the Control Panel > Add/Remove Programs for the version you want to disable:

Select Modify and disable the following options:

○ Integrated Documentation
○ Intel Parallel Debugger Extension
○ Integration(s) in Microsoft Visual Studio

            Select Next > Modify

2. Enable the Visual Studio integration.   

For  Intel Parallel Amplifier or Intel Parallel Inspector, start by opening the Command Prompt window for the version of Parallel Studio you wish to enable, then invoke the appropriate script to enable the integration:

For Intel Parallel Composer use the Control Panel > Add/Remove Programs entry for the version you want to enable:

Select Modify and enable the following options:

○ Integrated Documentation
○ Intel Parallel Debugger Extension
○ Integration(s) in Microsoft Visual Studio

The next steps are different based on your license type.

If you have a single user license, follow the simple steps below. 

Save the license file sent to you by email to:

          • On Windows*: <installation drive>\Program Files\Common Files\Intel\Licenses
          • On Linux*: /opt/intel/licenses
          • On MAC OS* X: /Users/Shared/Library/Application Support/Intel/Licenses
            Note: if the INTEL_LICENSE_FILE environment variable is defined, copy the file to the directory specified by the environment variable, instead.


If you have a counted (floating) license, you must do following to install and configure your License Host Server system and your client systems:

- Set up the license host server system
- Read the Intel License Manager for FLEXlm* User's Guide
- Download the correct Intel FLEXlm server for license host server system
- Install the FLEXlm server: after installation, the license server should start running automatically
- To manually start or stop the FLEXlm license server, please refer to the FLEXlm user's guide

References and useful articles: http://software.intel.com/en-us/articles/licensing-faq/

Intel® Parallel Amplifier Update 1 has realized this feature.

After installing the product, open a Command Prompt window and run the following command:

> C:\Program Files\Intel\Parallel Studio\Amplifier\ampl-vars.bat

Now, the environment for command line has been configured and you can use the ampl-cl command.

You can run ampl-cl -help to get familiar with the syntax of command.

Usage:

ampl-cl <-action-option [-modifier-option] [[--] target [target options]]

Action-option contains：collect, collect-list, report, report-list, finalize, help, version

Modifier-option contains： cumulative-threshold-percent, resume-after, result-dir, search-dir, start-pause, user-data-dir, verbose

Examples:

• List all data collectors
  > ampl-cl -collect-list
• run target application, collect hot functions, save results in default sub-directory
  > ampl-cl -collect hotspots matrix.exe
• run target application, collect hot functions, save result in specified sub-directory
  > ampl-cl -collect concurrency -result-dir r009cc matrix.exe
• run target application, delay 3000 million seconds (e.g., 3 sec) to collect times for all locks and waits, save results in default sub-directory
  > ampl-cl -collect lockswaits -start-paused -resume-after=3000 matrix.exe
• List all report types
  > ampl-cl -report-list
• Report a result for recent running
  > ampl-cl -report perf
• Report a result based on data  from specified sub-directory, use comma as a delimiter
  > ampl-cl -report perf-detail -csv-delimiter="," -result-dir r012hs
• Report enumerates modules that consumes 80% of total CPU time
  > ampl-cl -report perf -result-dir r012cc -cumulative-threshold-percent=80
• Compare results for two sessions
  > ampl-cl -report summary -result-dir r012cc -result-dir r009cc