Intel® VTune™ Profiler User Guide

User Guide

Contents

Set Up Remote Linux* Target

Use the
Intel® VTune™
Profiler
 installed on the Windows*, Linux*, or macOS* host to analyze code performance on remote Linux systems.
VTune
Profiler
 supports the following usage modes for remote analysis of Linux applications on regular and embedded systems:

Remote CLI and GUI Usage Mode

Requirements for the target system:
 ~25 MB disk space
This mode is recommended for most cross-development scenarios supported by the
VTune
Profiler
, especially if your target system is resource-constrained (insufficient disk space, memory, or CPU power) or if you use a highly customized Linux target system.
To collect data on a remote Linux system:
1. Install
VTune
Profiler
Install the full-scale
VTune
Profiler
 product on the host system.
  1. Set up a password-less SSH access to the target using RSA keys.
  2. Install the
    VTune
    Profiler
     target package     with data collectors on the target Linux system.
    If you choose to install the target package to a non-default location, make sure to specify the correct path either with the
    VTune
    Profiler
     installation directory on the remote system
     option in the
    WHERE
     pane (GUI) or with the option (CLI).
  3. Build the drivers on the host (if required), copy them to the target system and install the drivers.
    To build the sampling driver as RPM using build services as Open Build Service (OBS), use the
    sepdk.spec
     file located at
    <
    install_dir
    >/sepdk/src
     the directory.
3. Configure and run remote analysis
  1. On your host system, open the
    VTune
    Profiler
     GUI and select
    Configure Analysis
    .
  2. In the
    Where
     pane, specify an SSH connection to a remote Linux system.
  3. In the
    What
     pane, specify your target application on the remote system. Make sure to specify search directories for symbol/source files required for finalization on the host.
  4. In the
    How
     pane, choose and configure an analysis type.
  5. Start the analysis.
VTune
Profiler
 launches your application on the target, collects data, copies the analysis result and binary files to the host, and finalizes the data.
4. View results

Native Usage Mode

Requirements for the target system:
 ~200 MB disk space.
This mode is recommended for regular Linux target systems from supported operating systems listed in the product Release Notes. In this mode, you install the full-scale
VTune
Profiler
 product on the host system and install the command line interface of the
VTune
Profiler
,
vtune
, on the target system, which enables you to run native data collection directly on the target.
The following figure shows an overview of the remote analysis that is run with
vtune
 directly on the target system:
In the native usage mode, workflow steps to configure and run analysis on a remote system are similar to the remote collectors mode.

Native Sampling Collector (SEP) Usage Mode

Sampling сollector (SEP) is a command-line tool for hardware event-based sampling analysis targeted for resource-restricted systems. The SEP package is delivered as part of the target package of the
VTune
Profiler
. The SEP package contains both
sep
 utilities and the
sepdk
 source code (for
pax.ko
 and
sep4_x.ko
) to build the sampling drivers.
To use SEP, extract the SEP package from the
vtune_
profiler
_target_sep_x86.tgz
 or
vtune_
profiler
_target_sep_x86_64.tgz
 file, build the driver and upload both driver and
sep
 utilities to the target, and then collect the event-based sampling performance data in command line. See the
Sampling Enabling Product User's Guide
 for more details.
VTune
Profiler
 also provides the
sepdk
 sources for building sampling drivers. This source code could be same as the source code provided in the SEP package, if the
VTune
Profiler
 uses the same driver as SEP.
VTune
Profiler
sepdk
 sources also include the event-based stack sampling data collector that is not part of the SEP package.

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.