Set Up Linux* System for Remote Analysis
You can collect data remotely on a target Linux* system by specifying the system as the analysis target in
field.
Intel® VTune™
by selecting
Profiler
Remote Linux (SSH)
in the
Where
pane when configuring an analysis.
VTune
provides an option to automatically install the appropriate collectors on the target system. Specify a location for the install using the
Profiler
VTune
installation directory on the remote system Profiler
The automatic installation on the remote Linux system does not build the sampling drivers although you can install the pre-built sampling drivers if you connect via password-less SSH as the root user.
Driverless sampling data collection is based on the Linux Perf* tool functionality, which is available without Root access and has a limited scope of analysis options. To collect advanced hardware event-based sampling data, manually install the sampling driver or set up the password-less SSH connection with the Root user account.
- Install theVTunecollectors on the target system.Profiler
- If the collectors are not automatically installed or you get an error message after an automatic install attempt, use the following steps to manually prepare for data collection on a remote Linux system:
- Build and install sampling drivers. (Optional).
Install the
VTune
Profiler Collectors Automatically
VTune
Collectors Automatically Profiler
When you enter the connection parameters in the
Remote Linux* (SSH)
window of the
WHERE
pane,
VTune
checks for the presence of
Profiler
VTune
collector package on the target system specified.
Profiler
If an appropriate package was not located on the target system,
VTune
offers to deploy the package automatically.
Profiler

Press the
Deploy
button to start the automatic collectors package deployment process.
If the collectors are not automatically installed or you get an error message after an automatic install attempt, you can install the collectors manually.
Install the
VTune
Profiler Collectors Manually
VTune
Collectors Manually Profiler
Use the following steps to set up analysis on a target regular or embedded Linux target system.
- Copy the required target package archive to the target device using ftp, sftp, or scp. The following target packages are available on the host system where theVTuneis installed:Profiler
- <>/target/linux/vtune_- provides hardware event-based sampling collector only (SEP) for x86 systems_target_sep_x86.tgzprofiler
- - provides hardware event-based sampling collector only (SEP) for 64-bit systems<install-dir>/target/linux/vtune__target_sep_x86_64.tgzprofiler
- - provides all<install-dir>/target/linux/vtune__target_x86.tgzprofilerVTunecollectors for x86 systemsProfiler
- - provides all<install-dir>/target/linux/vtune__target_x86_64.tgzprofilerVTunecollectors for 64-bit systemsProfiler
Use both*_x86and*_x86_64packages if you plan to run and analyze 32-bit processes on 64-bit systems. - On the target device, unpack the product package to the/tmpdirectory or another writable location on the system:target> tar -zxvf <target_package>.tgzVTunetarget package is located in the newly created directoryProfiler/tmp/vtune_._<profilerversion>.<package_num>
When collecting data remotely, the
VTune
looks for the collectors on the target device in its default location:
Profiler
/tmp/vtune__<
. It also temporary stores performance results on the target system in the
profiler
version
>.<package_num
>/tmp
directory. If you installed the target package to a different location or need to specify another temporary directory, make sure to configure your target properties in the
Configure Analysis
window as follows:
- Use theoption to specify the path to theVTuneinstallation directory on the remote systemProfilerVTuneon the remote system. If default location is used, the path is provided automatically.Profiler
- Use theTemporary directory on the remote systemoption to specify a non-default temporary directory.
Build and Install the Drivers Manually
Building the sampling drivers is only required if the drivers were not built as part of the collector installation. The installation output should inform you if building the sampling driver is required.
To enable
hardware event-based sampling analysis on your target device:
- Build the sampling driver on the target system.
- Make sure kernel headers correspond to the kernel version running on the device. For details, see theREADME.txtfile in thesepdk/srcdirectory.
- Make sure compiler version corresponds to the architecture (x86 or x86_64) of the kernel running on the target system.
- For Hotspots in hardware event-based sampling mode, Microarchitecture 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/formatfile 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 theVTuneas well. For more information, see theProfilerTutorial: Troubleshooting and Tipstopic at https://perf.wiki.kernel.org/index.php/Main_Page.
- On the target device, install the drivers.If theinsmod-sepscript does not work on the target system due to absence of standard Linux commands, you may install drivers manually using the Linux OSinsmodcommand directly.
To build the sampling driver as RPM using build services as Open Build Service (OBS), use the
sepdk.spec
file located at the
<
the directory.
install-dir
>/sepdk/src