Preparing a Target Linux* System for Remote Analysis

Setting up SSH for Remote Collection

Configure SSH to work in password-less mode so it does not prompt for the password on each invocation.

For remote collection with Cygwin*, set up the password-less mode as follows:

1. Set a path to the Cygwin bin directory:

   host> set PATH=CYGWIN_ROOT\bin;%path%

2. Create a user directory in CYGWIN_ROOT\home if it does not exist:

   host> mkdir CYGWIN_ROOT\home\hostuser

3. Generate the dsa key with an empty passphrase:

   host> ssh-keygen -t dsa

4. Set correct permissions on the generated file:

   host> chmod 600 /home/hostuser/.ssh/id_dsa

5. Make sure the .ssh directory exists in the home directory on your device. If it is missing, create it.

   host> ssh user@target mkdir -p .ssh

6. Copy the generated id_dsa.pub file to the device:

   host> scp /home/user/.ssh/id_dsa.pub user@target:.ssh/authorized_keys

7. In the command console, you can login to a remote target system without password. VTune Amplifier GUI will try to find the ssh from environment. You may need to add CYGWIN_ROOT\bin into Windows PATH environment variable so that VTune Amplifier GUI can find the ssh command when doing the remote collection.

For remote collection with PuTTY* Plink, set up the password-less mode as follows:

1. Install the PuTTY package from www.putty.org.

2. Add the path to the PuTTy tools directory to the System variables> PATH variable and verify the connection, for example:

   host> plink.exe user@target ls

3. In the PuTTY Key Generator dialog box, click the Generate button (with all default settings intact) to generate keys.

4. Save the private key to your local drive, for example: C:\temp\linux_private_key.ppk.

5. Copy the public key from the PuTTY Key Generator dialog box and paste it to the file in the shared Linux /home directory: ~/.ssh/authorized_keys. If the file is absent, create it.

6. In the PuTTY Configuration dialog box, make sure to have the following settings:

7. Save the settings as the Default Settings session in PuTTY.

Building and Installing the Drivers

To enable Power analysis and hardware event-based sampling analysis on your target device:

1. Build the sampling driver and power driver on the host.

   Note

   • For Advanced Hotspots, General Exploration and Custom event-based sampling analysis types, you may not need root credentials and installing the sampling driver for systems with kernel 2.6.32 or higher, which exports CPU PMU programming details over /sys/bus/event_source/devices/cpu/format file system. Your operating system limits on the maximum amount of files opened by a process as well as maximum memory mapped to a process address space still apply and may affect profiling capabilities. These capabilities are based on Linux Perf* functionality and all its limitations fully apply to the VTune Amplifier as well. For more information, see the Tutorial: Troubleshooting and Tips topic at https://perf.wiki.kernel.org/index.php/Main_Page.

   • Make sure kernel headers correspond to the kernel version running on the device.

   • Make sure compiler version corresponds to the architecture (x86 or x86_64) of the kernel running on the target system.

2. Copy <install_dir>/sepdk and <install_dir>/powerdk folders to the /opt/intel/vtune_amplifier_<version> directory on the target device.

   You may choose another directory if this location is not accessible/does not exist or you can mount those folders via NFS.

3. On the target device, install the drivers.

   If scripts do not work on the target system due to absence of standard Linux commands, you may install drivers manually using the insmod command.

Installing the VTune Amplifier Collectors on the Target Device

To install the VTune Amplifier collectors on a regular Linux target system (applicable to the VTune Amplifier XE):

1. Copy the CLI_install folder from the top level in the extracted product install package to the remote machine.

2. On the target system, run the ./install.sh script file located in the CLI_install folder. No activation is required.

To install the VTune Amplifier collectors on an embedded or regular Linux system (applicable to the Intel VTune Amplifier for Systems):

1. Copy the required target package archive, located at <install_dir>\target\linux32[64], to the target device using ftp, sftp or scp. The following target packages are available:

   • linux32\vtune_amplifier_target_sep_x86.tgz - provides hardware event-based sampling collector only (SEP) for x86 systems

   • linux32\vtune_amplifier_target_x86.tgz - provides all VTune Amplifier collectors for x86 systems

   • linux64\vtune_amplifier_target_sep_x86_64.tgz - provides hardware event-based sampling collector only (SEP) for 64-bit systems

   • linux64\vtune_amplifier_target_x86_64.tgz - provides all VTune Amplifier collectors for 64-bit systems

   Note

   • Use both *_x86 and *_x86_64 packages if you plan to run and analyze 32-bit processes on 64-bit systems.

   • Remote collectors are also available in the <Intel_System_studio_install_dir>\Targets\ system_studio_target.tgz.

2. On the target device, unpack the product package to the /opt/intel directory:

   target> tar -zxvf <target_package>.tgz

   VTune Amplifier target package is located in the newly created directory /opt/intel/vtune_amplifier_2015_for_systems.<package_num>.

When collecting data remotely, the VTune Amplifier looks for the collectors on the target device in its default location: /opt/intel/vtune_amplifier_2015_for_systems.<package_num>. It also temporary stores performance results on the target system in the /tmp directory. If you installed the target package to a different location and need to specify another temporary directory, make sure to configure your target properties in the Project Properties dialog box > Target tab as follows:

• Use the VTune Amplifier installation directory on the remote system option to specify the path to the VTune Amplifier on the remote system. If default location is used, the path is provided automatically.

• Use the Temporary directory on the remote system option to specify a non-default temporary directory.

Alternatively, use the -target-install-dir and -target-tmp-diramplxe-cl options from command line.