[currently posting here since the Intel Premier Support portal does not seem to work for me - I stop at the first step, where I am unable to select my product. Forced to use Internet Explorer 9]
Hi,
I am currently evaluating VTUNE Amplifier XE on a peculiar Linux setup (Gentoo-based) with a Linux 3.10.17 kernel patched with the Xenomai RT framework, release 2.6.4. I am currently looking for a Linux equivalent to the 'SystemViewer' profiler available on VxWorks systems.
I first installed the application on the above kernel; then, upon trying to use the "Advanced Hotspots" analysis type I discovered that I needed to build my own SEP driver. I recompiled another version of the above kernel + RT patch with the flags required by sepdk, and then I built sepdk on it.
When I installed the associated kernel modules for group 'eats', this is what I obtained (everything appeared to work fine):
eats@finx-EATS ~ $ cd /opt/intel/vtune_amplifier_xe/sepdk/src/
eats@finx-EATS /opt/intel/vtune_amplifier_xe/sepdk/src $ sudo ./insmod-sep3 -r -g eats
Warning: no sep3_15 driver was found loaded in the kernel.
Warning: no vtsspp driver was found loaded in the kernel.
Attempting to stop PAX service ...
Warning: no pax driver was found loaded in the kernel.
PAX service has been stopped.
Checking for PMU arbitration service (PAX) ... not detected.
Attempting to start PAX service ...
Executing: insmod ./pax/pax-x32_64-3.10.17-xenomaiVTUNEsmp.ko
Creating /dev/pax device with major number 244 ... done.
Setting group ownership of devices to group "eats" ... done.
Setting file permissions on devices to "666" ... done.
The pax driver has been successfully loaded.
PAX service has been started.
PAX service is accessible to all users.
Executing: insmod ./sep3_15-x32_64-3.10.17-xenomaiVTUNEsmp.ko
Creating /dev/sep3_15 base devices with major number 243 ... done.
Creating /dev/sep3_15 percpu devices with major number 242 ... done.
Setting group ownership of devices to group "eats" ... done.
Setting file permissions on devices to "666" ... done.
The sep3_15 driver has been successfully loaded.
Checking for vtsspp driver ... not detected.
Executing: insmod ./vtsspp/vtsspp-x32_64-3.10.17-xenomaiVTUNEsmp.ko gid=1000 mode=0666
The vtsspp driver has been successfully loaded.
eats@finx-EATS /opt/intel/vtune_amplifier_xe/sepdk/src $ sudo ./boot-script --install -g eats
Configuring sep3_15 boot script with the following options:
driver files = /opt/intel/vtune_amplifier_xe_2015.4.0.410668/sepdk/src/.
driver group = eats
Creating boot script /etc/rc.d/init.d/sep3_15 ... done.
Configuring autoload of sep3_15 driver for runlevels 2 through 5 ... done.
eats@finx-EATS /opt/intel/vtune_amplifier_xe/sepdk/src $
However, when I configured the tool via GUI to launch / attach to my application process and analyze it by using 'Advanced Hotspots', this is what I got:
![]()
In fact, the process under test exits immediately (total execution time is a fraction of second, while it should stay there until an explicit break command) and the above warnings are displayed - although the build and installation phases previously appeared to complete flawlessly. And a few seconds after this message, the system freezes completely and the only option left for me is a cold reboot. I attempted to re-install the .ko modules under the 'root' group, but the outcome was exactly the same.
Ultimately, I would like to ask the following questions:
- Do the above warnings reveal that I have done something wrong during the installation?
- Is it mandatory to configure the tool for group 'root', and run it as 'root' in any case (i.e. no 'sudo')?
- Is 1ms the minimum time granularity that can be configured for sampling? Supposing that we would like to go down to the microsecond, could the tool allow for it?
Please let me know - or if possible, please forward my request to the above-quoted support board which I was unable to use in the first place.
-- Andrea Ferrato