Quantcast
Channel: Intel® VTune™ Profiler (Intel® VTune™ Amplifier)
Viewing all 1347 articles
Browse latest View live

Basic Hotspots vs Advanced Hotspots regarding CPU Usage (differ)

$
0
0

Why the CPU Usage differ between Basic Hotspots and Advanced Hotspots?

Two images: in the basic hotspots is what I was expecting (towards 400% utilization, the "4" cores used by threads). In the Advanced hotspots (not even 100% utilization), like only 1 core used.

In the Advanced, If I check the platform or bottom-up with threads/cores there is no overlapping, it just shows the same, like only 1 core is used. I don't specify any type of AFFINITY.


VTune and Application slowdown/hang

$
0
0

Hi Folks,

I'm working on profiling a third-party database server running on a single baremetal Skylake Xeon Platinum 8180 node running CentOS 7.2.  The server software is running as root user as well as the vtune command-line tool.  When using any preconfigured user sampling profile such as hotspots, VTune will not stop recording after the given duration.  In addition, my query benchmark running on a separate client machine runs well past its own time limits on execution.  At a certain point, the query rate just slows to a crawl and I cannot break out of amplxe-cl using Ctrl-C or its own stop command (that gives me an internal error).  Any advice is much appreciated.

-Marc

UPDATE:  Through some strange combination of *when* I start the benchmark, I'm able to capture some of the trace inside the GUI.  It finalizes results but the collection log shows:

Data collection is completed with warnings
    Tue 19 Dec 2017 12:51:18 AM CET  The result file '/root/profiling/vtune/ML/MarkLogic/r003hs/r003hs.amplxe' is created and added to the project MarkLogic. Please see warning messages for details. 
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.
    Cannot stop posix timer: __NR_timer_settime() system call returned -1.

Finalization completed with warnings 
    Tue 19 Dec 2017 12:52:20 AM CET  Result finalization has completed with warnings that may affect the representation of the analysis data. Please see details below. 
    The database has been cleared, elapsed time is 1.096 seconds.
    Raw data has been loaded to the database, elapsed time is 14.503 seconds.
    Data transformations have been finished, elapsed time is 0.019 seconds.
    Cannot locate debugging information for file `/opt/intel/vtune_amplifier_2018.1.0.535340/lib64/pinruntime/libc-dynamic.so'.
    XXXredactedXXXX
    Cannot locate debugging information for file `/opt/intel/vtune_amplifier_2018.1.0.535340/bin64/pinbin'.
    Cannot locate debugging information for file `/opt/intel/vtune_amplifier_2018.1.0.535340/lib64/libtpsstool.so'.
    Symbol resolution has been finished, elapsed time is 36.520 seconds.
    Deferred data transformations have been finished, elapsed time is 1.452 seconds.
    Data model parameters have been set, elapsed time is 0.096 seconds.
    Precomputing frequently used data has been finished, elapsed time is 0.913 seconds.
    Redundant overtime data has been discarded, elapsed time is 0.005 seconds.
    Raw collector data has been discarded, elapsed time is 0.000 seconds.
    Finalizing the result took 57.474 seconds.

FPU Utilization: Not supported for this CPU.

$
0
0

Hi, I want to run an HPC analysis since our app is heavy FPU intensive.

Our setup is an OSX host, Parallels VM with Windows 10 insider preview guest running on an "Intel(R) Core(TM) Processor code name Penryn" with Frequency: 3.2 GHz and  Logical CPU Count: 2

The FPU intensive part is inside a DLL that is loaded dynamically by our EXE.

I'm getting an "FPU Utilization: Not supported for this CPU." message, which I don't understand. Any idea what to do to measure FPU utilization etc.?

 

 

can't install SEP driver with VTune 2018 update 1

$
0
0

I update VTune to 2018 update 1. It reports "Cannot enable Hardware Event-based Sampling due to a problem with the driver (sep*/sepdrv*). Check that the driver is running and the driver group is in the current user group list. See the "Sampling Drivers" help topic for further details."

my machine installs Windows 10

OS Name Microsoft Windows 10 Enterprise
Version 10.0.14393 Build 14393
 

I referred  to the help page, and run "amplxe-sepreg.exe -i". it fails with the following error message

amplxe-sepreg.exe -i -v
Stopping service sepdrv4_1...NOT FOUND
Stopping service socperf2_0...NOT FOUND
Copying file C:\Program Files (x86)\IntelSWTools\VTune Amplifier 2018\bin64\sepdrv\win7\socperf2_0.sys to C:\Windows\System32\Drivers\socperf2_0.sys...FAILED
Reason: failed to copy C:\Program Files (x86)\IntelSWTools\VTune Amplifier 2018\bin64\sepdrv\win7\socperf2_0.sys to C:\Windows\System32\Drivers\socperf2_0.sys. Please check file permissions.
VTSS++ driver found
Deleting system32/drivers/vtss.sys file...FAILED
Forming source path for vtss.sys...OK
Forming destination path for vtss.sys...OK
Installing and starting VTSS++ driver...OK

amplxe-sepreg.exe -c
Checking platform...
Platform is genuine Intel: OK
Platform has SSE2: OK
Platform architecture: INTEL64
User has admin rights: OK
Drivers will be installed to C:\Windows\System32\Drivers\
Checking sepdrv4_1 driver path...OK
Checking sepdrv4_1 service...FAILED
Checking sepdal driver path...OK
Checking sepdal service...
Driver status: the sepdal service is running
Checking socperf2_0 driver path...OK
Checking socperf2_0 service...FAILED

 

is there any idea to fix the problem? 

Batch file analysis in Vtune

$
0
0

I am trying to analyze 100 different types of pdfs in adobe reader , is there any way for batch analysis of those files one after the other.Thank You.

Convert already generated report to csv without the gui

$
0
0

The results are generated by the following structure.

 

 

How to convert it to CSV or any other available format through the command line.

Group results by synchronization event

$
0
0

Hello All,

I was wondering if there is a way from the command line to group the results by synchronization event. By synchronization event I mean each time a synchronization was called. For example, if the same barrier wait is called multiple times, I would like to see stats for each of these times individually.

Thank you very much in advance

Win 7, Vtune 2017 update 3 ... cannot do first hot spot ... "serious problem"

$
0
0

I have created a simple C++ app called timeWaster. Built it using MSVC  19. This app runs fine in a command window created by Parallel Studio. (compiled using cl -EHsc -Zi timeWaster.cpp)

Sample run:

D:\Users\...\VTune\timeWaster>timeWaster64.exe

a=3.21061e+006

primeCnt=348844

11.2066  seconds

Done

Launch Vtune with admin rights.

Go to configure, select “Launch Application”, browse to the timeWaster64.exe, set working dir to same.

Toggle over to the run screen, “Basic Hotspots” selected, everything set to default. Hit start …

Up pops a command window … that stays empty (this window sticks around till killed with task master, timeWaster process still running 0% cpu).

Then within seconds of hitting start:

Intel VTune Amplifier XE 2017 has faced a serious problem

1/11/2018 6:21:45 AM  Cannot open data: Intel VTune Amplifier XE 2017 has faced a serious problem.

Error 0x40000024 (No data) -- No data is collected. Possible reasons:

 - Workload is too small. No samples are collected.

 - The application environment is not specified correctly.

 See the Troubleshooting help topic for more details. 

Trouble shooting area of of no help so I am here.

So where do I start tracking this down? I have already considered dll dependencies and pruned that list down to a minimum.

 


Recipe: How to detect OpenMP* Imbalance and Scheduling overhead with VTune Amplifier HPC Performance Characterization Analysis

$
0
0

Hello VTune Users,

With constant interest to OpenMP parallel efficiently analysis and growing popularity of VTune Amplifier Performance Analysis Cookbook we added a recipe that explains how to detect OpenMP imbalance on barriers and scheduling overhead based on a use case with prime numbers calculation: https://software.intel.com/en-us/vtune-amplifier-cookbook-openmp-imbalance-and-scheduling-overhead. 

It would be great to hear your feedback on the article usefulness, format convenience and what we can do more to make OpenMP analysis in VTune Amplifier better.

Thank you, Regards, Dmitry

 

Crash with internal Linux distro based on Debian testing

$
0
0

Hi,

In our internal linux distribution based on "Debian testing" I get a complete system crash when starting a profiling session (even if the command being profiled is as simple as a "/bin/ls"). As a starting point, hoping that this issue is not exclusive to our internal distro, can anyone please confirm whether VTune works in "debian testing"?

This is with VTune Amplifier 2018 Update 1 (build 535340):

1- Run VTune and press "New Project" toolbar button.
2- Set "target type" to "launch application", and "Application" to "/bin/ls".
3- Press "Choose Analysis" button on the right
4- Choose "Advanced Hotspots" analysis (I haven't tried other modes yet)
5- Press "Start" button on the right.

Result: the system crashes completely.

Thanks,
Ricardo

Reproducible windows crash when launching exe in visual studio debugger after running vtune on it in visual studio

$
0
0

- vtune (20128 u1) in visual studio 2017 (all updates applied as of today)

- in visual studio, have vtune profile the executable (which is built by the open solution)

- after that finishes, attempt to launch the executable in the vs debugger

-> screen goes back and the machine restarts. There are no errors in the system event log or a code dump file for the system (according to our IT guy).

 

Any ideas? This is the only time the machine has crashes recently. Happened 2x with the above workflow.

Thanks.

Debugging Symbols not found while compiling report

$
0
0

 

 

Will this error produce some unwanted results ? if yes how to fix it .

Thank You

process crashes when running with VTune

$
0
0

I am using VTune 2018 update 1 and when running my application via VTune it crashes immediately at startup. I also tried executing vtune via command line: amplxe-cl -c hotspots application.exe

I also tried attaching VTune to a running process and that goes fine until application shutdown, than VTune seems to think its a crash and loses all profiling information. If i collect profiling information before shutdown the results look good.

Its a 32 bit process  on windows 10 (delphi) which run's C++ code.

Any tips for investigation or possible causes?

 

Win Defender Device Guard: VTSS driver not loadable on Win 10 1703 and BSOD on Win 10 1709

$
0
0

Dear forum,

we recently ran into a problem with Intel VTune™ Amplifier 2018 update 1:

  • Win 10 1703: Failing to start VTSS driver: error 0xfffffffa on "net start vtss"
  • Win 10 1709: BSOD when starting the VTSS driver

After quite a lot of troubleshooting we narrowed the problem down to the following:

  • Together with rolling out Win 10 in the company, our IT department decided to increase security by activating Windows Defender Device Guard
  • If I take away the respective registry keys, everything runs as expected again.

Now our questions:

  • Is there already a version of VTSS (maybe also beta) that is compatible with device guard
  • When will there be an officially released version of VTune / VTSS fully compatible with Defender Device Guard
  • Are there known workarounds for the problem other than deactivation of Device Guard?

Thanks a lot for your help in advance and best wishes,
Brainlab Team

 

Open source license

$
0
0

Has anyone gotten an Open Source non-commercial license for VTune (Parallel Studio XE) lately, e.g., following this process:

https://software.intel.com/en-us/qualify-for-free-software/opensourcecon...

That is, within the last couple of months or so?

It worked flawlessly for me a year ago, but this time there has been zero response despite the following "confirmation" message in registrationcenter:

Please check your email for instructions to download your product. Note that this may take up to two business days.

that was six weeks ago and I've been kind of chasing my tail with support. Trying to figure out if this is affecting other non-commercial users or "just me".

I mostly use this pacakge so I can support the icc compiler in addition to the other major compilers, but I'm starting to question my commitment. Some more details on my ICC thread.

 

 


Error while profiling xeon-phi using Vtune Amplifier 2018

$
0
0

Hello

I want to profile my application on Intel Xeon-Phi co-processor using Intel Vtune Amplifier 2018. I am using the following command : 

amplxe-cl -target-system:mic-native:mic0 -collect-with runsa -knob event-config=?

to get all the PMU events for xeon-phi, but I am getting the following error :

amplxe: Error: FailedTo Read Content Definition(mic-native)

The xeon-phi card(mic0) is working.

What is the issue here? 

vtsspp driver fails to build on Linux kernel 4.13

$
0
0

I am trying to build VTune sampling drivers on Ubuntu 16.04 with Linux kernel version 4.13.0-32-generic. The compilation fails for vtsspp driver. The command line and log is given below:

Before building, the instructions in /opt/intel/vtune_amplifier_2018/sepdk/src/README.txt were followed and then build was issues as below:

username@server:/opt/intel/vtune_amplifier_2018/sepdk/src$ sudo ./build-driver
[sudo] password for ......:

Options in brackets "[ ... ]" indicate default values
that will be used when only the ENTER key is pressed.

C compiler to use: [ /usr/bin//gcc ]

Make command to use: [ /usr/bin//make ]

Kernel source directory: [ /lib/modules/4.13.0-32-generic/build ]
rm -f *.o .*.o.cmd .*.o.d .*.ko.cmd .*.ko.unsigned.cmd *.gcno
rm -f sep4_1.ko sep4_1.ko.unsigned
rm -f sep4_1*x32_64-4.13.0-32-genericsmp.ko
rm -f Module.symvers Modules.symvers *.mod.c modules.order Module.markers
rm -rf .tmp_versions
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax'
rm -f *.o .*.o.cmd .*.o.d .*.ko.cmd .*.ko.unsigned.cmd *.gcno
rm -f pax.ko pax.ko.unsigned pax-x32_64-4.13.0-32-genericsmp.ko
rm -f Module.symvers Modules.symvers *.mod.c modules.order Module.markers
rm -rf .tmp_versions
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax'
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src'
rm -f *.o .*.o.cmd .*.o.d .*.ko.cmd .*.ko.unsigned.cmd *.gcno
rm -f socperf2_0.ko socperf2_0.ko.unsigned
rm -f socperf2_0*x32_64-4.13.0-32-genericsmp.ko
rm -f Module.symvers Modules.symvers *.mod.c modules.order Module.markers
rm -rf .tmp_versions
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src'
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp'
rm -f *.o .*.o.cmd .*.o.d .*.ko.cmd .*.ko.unsigned.cmd *.gcno
rm -f Module.symvers Modules.symvers *.mod.c modules.order Module.markers
rm -rf .tmp_versions
rm -f /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/vtss_autoconf.h
rm -f vtsspp.ko vtsspp.ko.unsigned vtsspp-x32_64-4.13.0-32-genericsmp.ko
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp'
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src'
/usr/bin//make -C /lib/modules/4.13.0-32-generic/build M=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src LDDINCDIR=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/../include LDDINCDIR1=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/inc modules PWD=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src -j4
make[2]: Entering directory '/usr/src/linux-headers-4.13.0-32-generic'
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/socperfdrv.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/control.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/utility.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/pci.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/soc_uncore.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/haswellunc_sa.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/axi_uncore.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/npk_uncore.o
  LD [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/socperf2_0.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/socperf2_0.mod.o
  LD [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/socperf2_0.ko
make[2]: Leaving directory '/usr/src/linux-headers-4.13.0-32-generic'
cp socperf2_0.ko socperf2_0-x32_64-4.13.0-32-genericsmp.ko
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src'
/usr/bin//make -C /lib/modules/4.13.0-32-generic/build M=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src LDDINCDIR=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/../include LDDINCDIR1=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/inc modules PWD=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-32-generic'
***************************************************************
NOTE: NMI Interrupt Mode is set on 4.13.0-32-generic kernel
***************************************************************
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/lwpmudrv.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/control.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/cpumon.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/eventmux.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/linuxos.o
/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/linuxos.c:81:30: warning: ‘cpuhp_sepdrv_state’ defined but not used [-Wunused-variable]
 static enum cpuhp_state      cpuhp_sepdrv_state;
                              ^
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/output.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pmi.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sys_info.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/utility.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/valleyview_sochap.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_power.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pci.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/chap.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/gmch.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/gfx.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_sa.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/core2.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/perfver4.o
  AS [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sys64.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/silvermont.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/apic.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pebs.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_gt.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_mmio.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_msr.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_common.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_pci.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sepdrv_p_state.o
  LD [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sep4_1.o
  Building modules, stage 2.
***************************************************************
NOTE: NMI Interrupt Mode is set on 4.13.0-32-generic kernel
***************************************************************
  MODPOST 1 modules
  CC      /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sep4_1.mod.o
  LD [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sep4_1.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-32-generic'
cp sep4_1.ko sep4_1-x32_64-4.13.0-32-genericsmp.ko
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax'
/usr/bin//make -C /lib/modules/4.13.0-32-generic/build M=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax LDDINCDIR=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/../../include LDDINCDIR1=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/../inc modules PWD=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax
make[2]: Entering directory '/usr/src/linux-headers-4.13.0-32-generic'
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/pax.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/pax.mod.o
  LD [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/pax.ko
make[2]: Leaving directory '/usr/src/linux-headers-4.13.0-32-generic'
cp pax.ko pax-x32_64-4.13.0-32-genericsmp.ko
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax'
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp'
make[2]: Entering directory '/usr/src/linux-headers-4.13.0-32-generic'
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/module.o
  CC [M]  /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/collector.o
In file included from ./arch/x86/include/asm/cpufeature.h:4:0,
                 from ./arch/x86/include/asm/thread_info.h:63,
                 from ./include/linux/thread_info.h:37,
                 from ./arch/x86/include/asm/preempt.h:6,
                 from ./include/linux/preempt.h:80,
                 from ./include/linux/smp.h:142,
                 from /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/vtss_config.h:38,
                 from /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/collector.c:27:
/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/collector.c: In function ‘vtss_sched_switch_to’:
./arch/x86/include/asm/processor.h:820:39: error: implicit declaration of function ‘task_stack_page’ [-Werror=implicit-function-declaration] unsigned long __ptr = (unsigned long)task_stack_page(task);\
                                       ^
./arch/x86/include/asm/processor.h:897:26: note: in expansion of macro ‘task_pt_regs’
 #define KSTK_EIP(task)  (task_pt_regs(task)->ip)
                          ^
/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/collector.c:2257:29: note: in expansion of macro ‘KSTK_EIP’
                 ip = (void*)KSTK_EIP(task);
                             ^
cc1: all warnings being treated as errors
scripts/Makefile.build:308: recipe for target '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/collector.o' failed
make[3]: *** [/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/collector.o] Error 1
Makefile:1550: recipe for target '_module_/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp' failed
make[2]: *** [_module_/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-4.13.0-32-generic'
Makefile:244: recipe for target 'all' failed
make[1]: [all] Error 2 (ignored)
cp -f vtsspp.ko vtsspp-x32_64-4.13.0-32-genericsmp.ko
cp: cannot stat 'vtsspp.ko': No such file or directory
Makefile:244: recipe for target 'all' failed
make[1]: [all] Error 1 (ignored)
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp'

vtsspp seems to be broken with the lastest update to the kernel in Ubuntu 16.04 (Kernel 4.4.0-112 update)

$
0
0

I'm evaulating VTUNE but I ran into a problem.

It looks like X86_FEATURE_MFENCE_RDTSC was removed? (IDK if it is related to this ... https://lkml.org/lkml/2018/1/5/383)

linux-headers-4.4.0-104/arch/x86/include/asm/cpufeatures.h:#define X86_FEATURE_MFENCE_RDTSC ( 3*32+17) /* "" Mfence synchronizes RDTSC */
linux-headers-4.4.0-104/arch/x86/include/asm/msr.h: alternative_2("", "mfence", X86_FEATURE_MFENCE_RDTSC,
linux-headers-4.4.0-104/arch/x86/include/asm/mmu_context.h: * and neither LOCK nor MFENCE orders them.
linux-headers-4.4.0-104/arch/x86/include/asm/special_insns.h: * // MFENCE via mb() also works
linux-headers-4.4.0-104/arch/x86/include/asm/special_insns.h: * PCOMMIT must always be ordered by an MFENCE or SFENCE, so to help simplify

linux-headers-4.4.0-112/arch/x86/include/asm/special_insns.h: * // MFENCE via mb() also works
linux-headers-4.4.0-112/arch/x86/include/asm/special_insns.h: * PCOMMIT must always be ordered by an MFENCE or SFENCE, so to help simplify

*************************** ./build-driver log

Options in brackets "[ ... ]" indicate default values
that will be used when only the ENTER key is pressed.

C compiler to use: [ /usr/bin//gcc ]

Make command to use: [ /usr/bin//make ]

Kernel source directory: [ /lib/modules/4.4.0-112-generic/build ]
rm -f *.o .*.o.cmd .*.o.d .*.ko.cmd .*.ko.unsigned.cmd *.gcno
rm -f sep4_1.ko sep4_1.ko.unsigned
rm -f sep4_1*x32_64-4.4.0-112-genericsmp.ko
rm -f Module.symvers Modules.symvers *.mod.c modules.order Module.markers
rm -rf .tmp_versions
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax'
rm -f *.o .*.o.cmd .*.o.d .*.ko.cmd .*.ko.unsigned.cmd *.gcno
rm -f pax.ko pax.ko.unsigned pax-x32_64-4.4.0-112-genericsmp.ko
rm -f Module.symvers Modules.symvers *.mod.c modules.order Module.markers
rm -rf .tmp_versions
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax'
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src'
rm -f *.o .*.o.cmd .*.o.d .*.ko.cmd .*.ko.unsigned.cmd *.gcno
rm -f socperf2_0.ko socperf2_0.ko.unsigned
rm -f socperf2_0*x32_64-4.4.0-112-genericsmp.ko
rm -f Module.symvers Modules.symvers *.mod.c modules.order Module.markers
rm -rf .tmp_versions
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src'
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp'
rm -f *.o .*.o.cmd .*.o.d .*.ko.cmd .*.ko.unsigned.cmd *.gcno
rm -f Module.symvers Modules.symvers *.mod.c modules.order Module.markers
rm -rf .tmp_versions
rm -f /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/vtss_autoconf.h
rm -f vtsspp.ko vtsspp.ko.unsigned vtsspp-x32_64-4.4.0-112-genericsmp.ko
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp'
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src'
/usr/bin//make -C /lib/modules/4.4.0-112-generic/build M=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src LDDINCDIR=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/../include LDDINCDIR1=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/inc modules PWD=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src -j4
make[2]: Entering directory '/usr/src/linux-headers-4.4.0-112-generic'
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/socperfdrv.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/control.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/utility.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/pci.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/soc_uncore.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/haswellunc_sa.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/axi_uncore.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/npk_uncore.o
LD [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/socperf2_0.o
Building modules, stage 2.
MODPOST 1 modules
CC /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/socperf2_0.mod.o
LD [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src/socperf2_0.ko
make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-112-generic'
cp socperf2_0.ko socperf2_0-x32_64-4.4.0-112-genericsmp.ko
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/socperf/src'
/usr/bin//make -C /lib/modules/4.4.0-112-generic/build M=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src LDDINCDIR=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/../include LDDINCDIR1=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/inc modules PWD=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src
make[1]: Entering directory '/usr/src/linux-headers-4.4.0-112-generic'
***************************************************************
NOTE: NMI Interrupt Mode is set on 4.4.0-112-generic kernel
***************************************************************
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/lwpmudrv.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/control.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/cpumon.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/eventmux.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/linuxos.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/output.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pmi.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sys_info.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/utility.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/valleyview_sochap.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_power.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pci.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/chap.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/gmch.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/gfx.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_sa.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/core2.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/perfver4.o
AS [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sys64.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/silvermont.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/apic.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pebs.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_gt.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_mmio.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_msr.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_common.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/unc_pci.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sepdrv_p_state.o
LD [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sep4_1.o
Building modules, stage 2.
***************************************************************
NOTE: NMI Interrupt Mode is set on 4.4.0-112-generic kernel
***************************************************************
MODPOST 1 modules
CC /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sep4_1.mod.o
LD [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/sep4_1.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-112-generic'
cp sep4_1.ko sep4_1-x32_64-4.4.0-112-genericsmp.ko
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax'
/usr/bin//make -C /lib/modules/4.4.0-112-generic/build M=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax LDDINCDIR=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/../../include LDDINCDIR1=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/../inc modules PWD=/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax
make[2]: Entering directory '/usr/src/linux-headers-4.4.0-112-generic'
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/pax.o
Building modules, stage 2.
MODPOST 1 modules
CC /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/pax.mod.o
LD [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax/pax.ko
make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-112-generic'
cp pax.ko pax-x32_64-4.4.0-112-genericsmp.ko
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/pax'
make[1]: Entering directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp'
make[2]: Entering directory '/usr/src/linux-headers-4.4.0-112-generic'
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/module.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/collector.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/procfs.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/transport.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/record.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/task_map.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/globals.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/cpuevents.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/user_vm.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/stack.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/apic.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/dsa.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/bts.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/pebs.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/lbr.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/nmiwd.o
CC [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/ipt.o
AS [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/sys64.o
LD [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/vtsspp.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "X86_FEATURE_MFENCE_RDTSC" [/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/vtsspp.ko] undefined!
CC /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/vtsspp.mod.o
LD [M] /opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp/vtsspp.ko
make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-112-generic'
cp -f vtsspp.ko vtsspp-x32_64-4.4.0-112-genericsmp.ko
make[1]: Leaving directory '/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src/vtsspp'

****************DMESG

[20838.643824] socperf2_0: SocPerf Driver loading...
[20838.643831] socperf2_0: SocPerf Driver about to register chrdev...
[20838.643836] socperf2_0: SocPerf Driver: result of alloc_chrdev_region is 0
[20838.643839] socperf2_0: SocPerf Driver: major number is 237
[20838.643842] socperf2_0: SocPerf Driver: detected 8 CPUs in lwpmudrv_Load
[20838.643847] socperf2_0: SocPerf Driver v2.0.0 has been loaded.
[20839.663683] sep4_1: PMU collection driver v4.1.0 has been loaded.
[20839.663688] sep4_1: Chipset support is enabled.
[20839.663690] sep4_1: Graphics support is enabled.
[20839.663692] sep4_1: NMI will be used for handling PMU interrupts.
[20843.750448] vtsspp: Unknown symbol X86_FEATURE_MFENCE_RDTSC (err 0)

VTSSPP driver failed to load.

$
0
0

Unable to load vtsspp driver on my ubuntu 16.04 devbox.

Am I missing something? 

Thank you very much !!

murthy@murthy-desktop:/opt/intel/vtune_amplifier_2018.1.0.535340/sepdk/src$ sudo ./vtsspp/insmod-vtsspp
Executing: insmod ./vtsspp/vtsspp-x32_64-4.4.0-112-genericsmp.ko gid=1001 mode=0666
insmod: ERROR: could not insert module ./vtsspp/vtsspp-x32_64-4.4.0-112-genericsmp.ko: Unknown symbol in module

Error:  vtsspp driver failed to load!

You may need to build vtsspp driver for your kernel.
Please see the vtsspp driver README for instructions.

nodes crash using SEP collectors after Meltdown/Spectre patches

$
0
0

After patching our OS for Meltdown we're seeing nodes crash during amplxe-cl collection using the HW counters (any of the non-PIN collections)

PIN collections work ( simple hotspots )

Also, using the older 2017 Update 1 VTune and collectors there are no issues.

But 2018 Update 1 with event counters crashes the node almost immediately after start of collection on any application. 

SEP drivers were not rebuilt after the Meltdown kernel patches - perhaps that is a test to do?

Anyone else seen this behavior?  Nodes crash hard and have to be power cycled.

Viewing all 1347 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>