Intel(R) VTune(TM) Profiler Self Check Utility Copyright (C) 2009-2019 Intel Corporation. All rights reserved. Build Number: 605129 Ignored warnings: ['To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location.', 'To enable hardware event-base sampling, PRODUCT_LEGAL_SHORT_NAME has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.'] Check of files: Ok ================================================================================ Context values: Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/amplxe-runss --context-value-list Stdout: targetOS: Linux OS: Linux OSBuildNumber: 0 OSBitness: 64 RootPrivileges: true isPtraceScopeLimited: false isCATSupportedByCPU: false isTSXAvailable: true isHTEnabled: false fpgaOnBoard: None omniPathOnBoard: None genArchOnBoard: 6 pciClassParts: isSGXAvailable: true LinuxRelease: 4.19.0-rc8-custom is3DXPPresent: false is3DXP2LMMode: false is3DXPAppDirectMode: false IsNUMANodeWithoutCPUsPresent: false Hypervisor: None PerfmonVersion: 4 isMaxDRAMBandwidthMeasurementSupported: true isPtraceAvailable: true areGpuHardwareMetricsAvailable: true i915Status: KernelNotPatched isPAVPEnabled: false gpuPlatformIndex: 7 isFtraceAvailable: yes isMdfEtwAvailable: false isCSwitchAvailable: yes isGpuBusynessAvailable: yes isGpuWaitAvailable: yes isFunctionTracingAvailable: yes isIowaitTracingAvailable: yes isVSyncAvailable: yes HypervisorType: None isDeviceOrCredentialGuardEnabled: false isSEPDriverAvailable: false isPAXDriverLoaded: false platformType: 103 CPU_NAME: Intel(R) Processor code named Skylake PMU: skylake availablePmuTypes: core,cbo,imc,gt,edram,ncu,power referenceFrequency: 2600000000 isPStateAvailable: true isVTSSPPDriverAvailable: false isNMIWatchDogTimerRunning: true LinuxPerfCredentials: Unlimited LinuxPerfCapabilities: breakpoint:raw;cpu:raw,format,events,ldlat,frontend;cstate_core:raw,format,events;cstate_pkg:raw,format,events;i915:raw,format,events;intel_pt:raw,format;kprobe:raw,format;msr:raw,format,events;power:raw,format,events;software:raw;tracepoint:raw;uncore_arb:raw,format;uncore_cbox:4,raw,format,events;uncore_imc:raw,format,events;uprobe:raw,format LinuxPerfStackCapabilities: fp,dwarf,lbr areKernelPtrsRestricted: no isTPSSAvailable: true isPytraceAvailable: true isGENDebugInfoAvailable: true isGTPinCollectionAvailable: true isSTTAvailable: no isNnpiHwTraceToolAvailable: false isEnergyCollectionSupported: true isSocwatchDriverLoaded: false Getting context values: OK ================================================================================ Check driver: isSEPDriverAvailable: false isPAXDriverLoaded: false Command line: lsmod Is SEP in lsmod: False The SEP driver is not available. ================================================================================ SEP version: Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/sep -version Stdout: Sampling Enabling Product version: 5.14 built on Nov 26 2019 10:48:27 SEP User Mode Version: 5.14 SEP Driver Version: PAX Driver Version: Platform type: 103 CPU name: Intel(R) Processor code named Skylake PMU: skylake Stderr: Error retrieving SEP driver version Error retrieving PAX driver version Check driver with sep -version: Fail ================================================================================ Running collection... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -collect hotspots -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_tpss -data-limit 0 -finalization-mode none -- /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/matrix -source-search-dir /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/src Stdout: Addr of buf1 = 0x7f9b9ad52010 Offs of buf1 = 0x7f9b9ad52180 Addr of buf2 = 0x7f9b98d51010 Offs of buf2 = 0x7f9b98d511c0 Addr of buf3 = 0x7f9b96d50010 Offs of buf3 = 0x7f9b96d50100 Addr of buf4 = 0x7f9b94d4f010 Offs of buf4 = 0x7f9b94d4f140 Threads #: 4 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 35.204 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_tpss -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_tpss' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done Instrumentation based analysis check Example of analysis types: Hotspots with default knob sampling-mode=sw, Threading with default knob sampling-and-waits=sw Collection: Ok -------------------------------------------------------------------------------- Running finalization... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_tpss Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_tpss' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-9941-jflmkl110.jf.intel. vtune: Executing actions 25 % Loading 'systemcollector-9941-jflmkl110.jf.intel. vtune: Executing actions 25 % Loading '9954.stat.perf' file vtune: Executing actions 25 % Loading '9941-9954.0.trace' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 39 % Resolving information for `libc.so.6' vtune: Executing actions 41 % Resolving information for `libc.so.6' vtune: Executing actions 41 % Resolving information for `libpthread.so.0' vtune: Executing actions 43 % Resolving information for `libpthread.so.0' vtune: Executing actions 45 % Resolving information for `libpthread.so.0' vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 49 % Resolving thread name information vtune: Executing actions 49 % Resolving call target names for dynamic code vtune: Executing actions 51 % Resolving call target names for dynamic code vtune: Executing actions 53 % Resolving call target names for dynamic code vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 60 % Setting data model parameters vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 72 % Updating precomputed scalar metrics vtune: Executing actions 75 % Updating precomputed scalar metrics vtune: Executing actions 75 % Discarding redundant overtime data vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 78 % Saving the result vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok -------------------------------------------------------------------------------- Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_tpss Stdout: Function,CPU Time,CPU Time:Effective Time,CPU Time:Effective Time:Idle,CPU Time:Effective Time:Poor,CPU Time:Effective Time:Ok,CPU Time:Effective Time:Ideal,CPU Time:Effective Time:Over,CPU Time:Spin Time,CPU Time:Overhead Time,Module,Function (Full),Source File,Start Address multiply1,140.069380,140.069380,0.0,1.203812,0.0,138.865568,0.0,0.0,0.0,matrix,multiply1,multiply.c,0x401550 init_arr,0.010000,0.010000,0.0,0.010000,0.0,0.0,0.0,0.0,0.0,matrix,init_arr,matrix.c,0x400bab init_arr,0.010000,0.010000,0.0,0.010000,0.0,0.0,0.0,0.0,0.0,matrix,init_arr,matrix.c,0x400d4f Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_tpss' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ Running collection... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -collect hotspots -knob sampling-mode=hw -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah -data-limit 0 -finalization-mode none -- /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/matrix -source-search-dir /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/src Stdout: Addr of buf1 = 0x7f613c2fe010 Offs of buf1 = 0x7f613c2fe180 Addr of buf2 = 0x7f613a2fd010 Offs of buf2 = 0x7f613a2fd1c0 Addr of buf3 = 0x7f61382fc010 Offs of buf3 = 0x7f61382fc100 Addr of buf4 = 0x7f61362fb010 Offs of buf4 = 0x7f61362fb140 Threads #: 4 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 35.398 seconds Stderr: vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis check (Perf) Example of analysis types: Hotspots with knob sampling-mode=hw, HPC Performance Characterization, etc. Collection: Ok vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. -------------------------------------------------------------------------------- Running finalization... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-10019-jflmkl110.jf.intel vtune: Executing actions 25 % Loading 'systemcollector-10019-jflmkl110.jf.intel vtune: Executing actions 25 % Loading '10029.perf' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for `ld-2.27.so' vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 40 % Resolving information for `matrix' vtune: Executing actions 40 % Resolving information for `e1000e.ko' vtune: Executing actions 42 % Resolving information for `e1000e.ko' vtune: Warning: Cannot locate debugging information for file `/lib/modules/4.19.0-rc8-custom/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko'. vtune: Executing actions 43 % Resolving information for `e1000e.ko' vtune: Executing actions 43 % Resolving information for `vmlinux' vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. vtune: Executing actions 45 % Resolving information for `vmlinux' vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 49 % Resolving thread name information vtune: Executing actions 49 % Resolving call target names for dynamic code vtune: Executing actions 51 % Resolving call target names for dynamic code vtune: Executing actions 53 % Resolving call target names for dynamic code vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 54 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 60 % Setting data model parameters vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 62 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 65 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 72 % Updating precomputed scalar metrics vtune: Executing actions 75 % Updating precomputed scalar metrics vtune: Executing actions 75 % Discarding redundant overtime data vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 78 % Saving the result vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. -------------------------------------------------------------------------------- Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah Stdout: Function,CPU Time,CPU Time:Effective Time,CPU Time:Effective Time:Idle,CPU Time:Effective Time:Poor,CPU Time:Effective Time:Ok,CPU Time:Effective Time:Ideal,CPU Time:Effective Time:Over,CPU Time:Spin Time,CPU Time:Overhead Time,Instructions Retired,Microarchitecture Usage(%),Microarchitecture Usage:Microarchitecture Usage(%),Microarchitecture Usage:CPI Rate,Module,Function (Full),Source File,Start Address multiply1,138.566350,138.566350,0.001003,1.471528,0.0,137.093819,0.0,0.0,0.0,68962400000,15.9,15.9,2.012630,matrix,multiply1,multiply.c,0x401550 interrupt_entry,0.055170,0.055170,0.0,0.002006,0.0,0.053164,0.0,0.0,0.0,7800000,8.9,8.9,4.333333,vmlinux,interrupt_entry,[Unknown],0xffffffff81a00880 apic_timer_interrupt,0.041127,0.041127,0.0,0.001003,0.0,0.040123,0.0,0.0,0.0,0,11.0,11.0,,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81a01a50 smp_call_function_many,0.024074,0.024074,0.0,0.0,0.0,0.024074,0.0,0.0,0.0,0,0.0,0.0,,vmlinux,smp_call_function_many,[Unknown],0xffffffff811323e0 swapgs_restore_regs_and_return_to_usermode,0.024074,0.024074,0.0,0.0,0.0,0.024074,0.0,0.0,0.0,5200000,26.6,26.6,6.500000,vmlinux,swapgs_restore_regs_and_return_to_usermode,[Unknown],0xffffffff81a00974 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ Running collection... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -collect uarch-exploration -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ge -data-limit 0 -finalization-mode none -- /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/matrix -source-search-dir /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/src Stdout: Addr of buf1 = 0x7f86c27b6010 Offs of buf1 = 0x7f86c27b6180 Addr of buf2 = 0x7f86c07b5010 Offs of buf2 = 0x7f86c07b51c0 Addr of buf3 = 0x7f86be7b4010 Offs of buf3 = 0x7f86be7b4100 Addr of buf4 = 0x7f86bc7b3010 Offs of buf4 = 0x7f86bc7b3140 Threads #: 4 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 36.093 seconds Stderr: vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ge -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ge' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis check (Perf) Example of analysis types: Microarchitecture Exploration Collection: Ok vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. -------------------------------------------------------------------------------- Running finalization... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ge Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ge' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-10101-jflmkl110.jf.intel vtune: Executing actions 25 % Loading 'systemcollector-10101-jflmkl110.jf.intel vtune: Executing actions 25 % Loading 'system-wide.perf' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 39 % Resolving information for `e1000e.ko' vtune: Warning: Cannot locate debugging information for file `/lib/modules/4.19.0-rc8-custom/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko'. vtune: Executing actions 40 % Resolving information for `e1000e.ko' vtune: Executing actions 42 % Resolving information for `e1000e.ko' vtune: Executing actions 42 % Resolving information for `lockd.ko' vtune: Warning: Cannot locate debugging information for file `/lib/modules/4.19.0-rc8-custom/kernel/fs/lockd/lockd.ko'. vtune: Executing actions 43 % Resolving information for `lockd.ko' vtune: Executing actions 43 % Resolving information for `vmlinux' vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. vtune: Executing actions 45 % Resolving information for `vmlinux' vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 49 % Resolving thread name information vtune: Executing actions 49 % Resolving call target names for dynamic code vtune: Executing actions 51 % Resolving call target names for dynamic code vtune: Executing actions 53 % Resolving call target names for dynamic code vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 54 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 60 % Setting data model parameters vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 62 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 65 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 72 % Updating precomputed scalar metrics vtune: Executing actions 75 % Updating precomputed scalar metrics vtune: Executing actions 75 % Discarding redundant overtime data vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 78 % Saving the result vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. -------------------------------------------------------------------------------- Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ge Stdout: Function,CPU Time,Clockticks,Instructions Retired,CPI Rate,Retiring(%),Retiring:General Retirement(%),Retiring:General Retirement:FP Arithmetic(%),Retiring:General Retirement:FP Arithmetic:FP x87(%),Retiring:General Retirement:FP Arithmetic:FP Scalar(%),Retiring:General Retirement:FP Arithmetic:FP Vector(%),Retiring:General Retirement:Other(%),Retiring:Microcode Sequencer(%),Retiring:Microcode Sequencer:Assists(%),Front-End Bound(%),Front-End Bound:Front-End Latency(%),Front-End Bound:Front-End Latency:ICache Misses(%),Front-End Bound:Front-End Latency:ITLB Overhead(%),Front-End Bound:Front-End Latency:Branch Resteers(%),Front-End Bound:Front-End Latency:Branch Resteers:Mispredicts Resteers(%),Front-End Bound:Front-End Latency:Branch Resteers:Clears Resteers(%),Front-End Bound:Front-End Latency:Branch Resteers:Unknown Branches(%),Front-End Bound:Front-End Latency:DSB Switches(%),Front-End Bound:Front-End Latency:Length Changing Prefixes(%),Front-End Bound:Front-End Latency:MS Switches(%),Front-End Bound:Front-End Bandwidth(%),Front-End Bound:Front-End Bandwidth:Front-End Bandwidth MITE(%),Front-End Bound:Front-End Bandwidth:Front-End Bandwidth DSB(%),Front-End Bound:Front-End Bandwidth:(Info) DSB Coverage(%),Bad Speculation(%),Bad Speculation:Branch Mispredict(%),Bad Speculation:Machine Clears(%),Back-End Bound(%),Back-End Bound:Memory Bound(%),Back-End Bound:Memory Bound:L1 Bound(%),Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead(%),Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead:Load STLB Hit(%),Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead:Load STLB Miss(%),Back-End Bound:Memory Bound:L1 Bound:Loads Blocked by Store Forwarding(%),Back-End Bound:Memory Bound:L1 Bound:Lock Latency(%),Back-End Bound:Memory Bound:L1 Bound:Split Loads(%),Back-End Bound:Memory Bound:L1 Bound:4K Aliasing(%),Back-End Bound:Memory Bound:L1 Bound:FB Full(%),Back-End Bound:Memory Bound:L2 Bound(%),Back-End Bound:Memory Bound:L3 Bound(%),Back-End Bound:Memory Bound:L3 Bound:Contested Accesses(%),Back-End Bound:Memory Bound:L3 Bound:Data Sharing(%),Back-End Bound:Memory Bound:L3 Bound:L3 Latency(%),Back-End Bound:Memory Bound:L3 Bound:SQ Full(%),Back-End Bound:Memory Bound:DRAM Bound(%),Back-End Bound:Memory Bound:DRAM Bound:Memory Bandwidth(%),Back-End Bound:Memory Bound:DRAM Bound:Memory Latency(%),Back-End Bound:Memory Bound:Store Bound(%),Back-End Bound:Memory Bound:Store Bound:Store Latency(%),Back-End Bound:Memory Bound:Store Bound:False Sharing(%),Back-End Bound:Memory Bound:Store Bound:Split Stores(%),Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead(%),Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead:Store STLB Hit(%),Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead:Store STLB Hit(%),Back-End Bound:Core Bound(%),Back-End Bound:Core Bound:Divider(%),Back-End Bound:Core Bound:Port Utilization(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Serializing Operations(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 1 Port Utilized(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 2 Ports Utilized(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 0(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 1(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 5(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 6(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Load Operation Utilization(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Load Operation Utilization:Port 2(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Load Operation Utilization:Port 3(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Store Operation Utilization(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Store Operation Utilization:Port 4(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Store Operation Utilization:Port 7(%),Back-End Bound:Core Bound:Port Utilization:Vector Capacity Usage (FPU)(%),Average CPU Frequency,Module,Function (Full),Source File,Start Address multiply1,140.593587,140756200000,69040400000,2.038751,12.4,12.3,24.5,0.0,24.5,0.0,75.5,0.1,0.0,0.3,0.3,0.0,0.0,0.2,0.0,0.1,0.0,0.0,0.0,0.0,0.0,0.3,0.1,98.4,0.3,0.0,0.3,87.0,68.3,0.5,92.7,0.0,92.7,0.0,0.0,0.0,0.2,100.0,0.0,0.8,0.9,1.0,8.8,0.0,62.0,97.4,1.5,0.0,0.1,0.0,0.0,0.3,0.0,0.2,18.7,0.0,17.3,0.2,0.5,17.1,11.7,6.5,25.8,40.2,37.9,9.6,15.3,6.2,9.1,9.5,6.1,6.1,0.0,25.0,1001156615.930052,matrix,multiply1,multiply.c,0x401550 interrupt_entry,0.044136,46800000,2600000,18.000000,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,25.8,0.0,0.0,25.8,0.0,0.0,0.0,0.0,0.0,0.0,0.0,14.3,0.0,14.3,85.7,0.0,0.0,14.3,0.0,14.3,0.0,0.0,0.0,0.0,0.0,57.2,0.0,0.0,0.0,0.0,0.0,57.2,0.0,57.2,0.0,0.0,0.0,0.0,17.2,0.0,17.2,85.7,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,28.6,0.0,57.2,0.0,0.0,0.0,0.0,1060363700.181818,vmlinux,interrupt_entry,[Unknown],0xffffffff81a00880 apic_timer_interrupt,0.042130,49400000,0,,,,0.0,0.0,0.0,0.0,100.0,,,,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,,,,0.0,,,,,,0.0,13.6,0.0,13.6,0.0,0.0,0.0,0.0,0.0,54.3,0.0,0.0,0.0,0.0,,0.0,0.0,54.2,0.0,0.0,0.0,,,,,,0.0,54.2,,54.2,,,,,,,,,,,,,,,0.0,1172571499.142857,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81a01a50 smp_call_function_many,0.031096,26000000,2600000,10.000000,,,0.0,0.0,0.0,0.0,100.0,,,,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,,,,0.0,,,,,,0.0,5.2,0.0,5.2,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,,0.0,0.0,0.0,0.0,0.0,0.0,,,,,,0.0,0.0,,0.0,,,,,,,,,,,,,,,0.0,836129082.580645,vmlinux,smp_call_function_many,[Unknown],0xffffffff811323e0 swapgs_restore_regs_and_return_to_usermode,0.029090,33800000,5200000,6.500000,19.8,,0.0,0.0,0.0,0.0,100.0,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,79.3,0.0,0.0,0.0,-0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,7.9,0.0,7.9,100.0,0.0,79.1,79.1,79.1,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,1161931104.413793,vmlinux,swapgs_restore_regs_and_return_to_usermode,[Unknown],0xffffffff81a00974 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ge' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ Running collection... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -collect memory-access -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ma -data-limit 0 -finalization-mode none -- /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/matrix -source-search-dir /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/src Stdout: Addr of buf1 = 0x7fc73bae7010 Offs of buf1 = 0x7fc73bae7180 Addr of buf2 = 0x7fc739ae6010 Offs of buf2 = 0x7fc739ae61c0 Addr of buf3 = 0x7fc737ae5010 Offs of buf3 = 0x7fc737ae5100 Addr of buf4 = 0x7fc735ae4010 Offs of buf4 = 0x7fc735ae4140 Threads #: 4 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 36.679 seconds Stderr: vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Peak bandwidth measurement started. vtune: Peak bandwidth measurement finished. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ma -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ma' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with uncore events (Perf) Example of analysis types: Memory Access Collection: Ok vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. -------------------------------------------------------------------------------- Running finalization... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ma Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ma' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-10193-jflmkl110.jf.intel vtune: Executing actions 25 % Loading 'systemcollector-10193-jflmkl110.jf.intel vtune: Executing actions 25 % Loading 'system-wide.perf' file vtune: Executing actions 25 % Loading 'system-wide.stat.perf' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for dangling locations vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 39 % Resolving information for `libahci.ko' vtune: Warning: Cannot locate debugging information for file `/lib/modules/4.19.0-rc8-custom/kernel/drivers/ata/libahci.ko'. vtune: Executing actions 39 % Resolving information for `rpcsec_gss_krb5.ko' vtune: Warning: Cannot locate debugging information for file `/lib/modules/4.19.0-rc8-custom/kernel/net/sunrpc/auth_gss/rpcsec_gss_krb5.ko'. vtune: Executing actions 40 % Resolving information for `rpcsec_gss_krb5.ko' vtune: Executing actions 40 % Resolving information for `e1000e.ko' vtune: Executing actions 41 % Resolving information for `e1000e.ko' vtune: Executing actions 41 % Resolving information for `ld-2.27.so' vtune: Warning: Cannot locate debugging information for file `/lib/modules/4.19.0-rc8-custom/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko'. vtune: Executing actions 42 % Resolving information for `ld-2.27.so' vtune: Executing actions 43 % Resolving information for `ld-2.27.so' vtune: Executing actions 44 % Resolving information for `ld-2.27.so' vtune: Executing actions 44 % Resolving information for `vmlinux' vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. vtune: Executing actions 45 % Resolving information for `vmlinux' vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 49 % Resolving thread name information vtune: Executing actions 49 % Resolving call target names for dynamic code vtune: Executing actions 51 % Resolving call target names for dynamic code vtune: Executing actions 53 % Resolving call target names for dynamic code vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 54 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 62 % Processing profile metrics and debug information vtune: Executing actions 63 % Processing profile metrics and debug information vtune: Executing actions 63 % Preparing output tree vtune: Executing actions 63 % Parsing columns in input tree vtune: Executing actions 64 % Parsing columns in input tree vtune: Executing actions 64 % Creating top-level columns vtune: Executing actions 65 % Creating top-level columns vtune: Executing actions 65 % Creating top-level rows vtune: Executing actions 67 % Creating top-level rows vtune: Executing actions 67 % Setting data model parameters vtune: Executing actions 68 % Setting data model parameters vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 73 % Precomputing frequently used data vtune: Executing actions 74 % Precomputing frequently used data vtune: Executing actions 75 % Precomputing frequently used data vtune: Executing actions 76 % Precomputing frequently used data vtune: Executing actions 77 % Precomputing frequently used data vtune: Executing actions 78 % Precomputing frequently used data vtune: Executing actions 79 % Precomputing frequently used data vtune: Executing actions 79 % Updating precomputed scalar metrics vtune: Executing actions 82 % Updating precomputed scalar metrics vtune: Executing actions 82 % Discarding redundant overtime data vtune: Executing actions 85 % Discarding redundant overtime data vtune: Executing actions 85 % Saving the result vtune: Executing actions 89 % Saving the result vtune: Executing actions 92 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. -------------------------------------------------------------------------------- Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ma Stdout: Function,CPU Time,Memory Bound(%),Memory Bound:L1 Bound(%),Memory Bound:L2 Bound(%),Memory Bound:L3 Bound(%),Memory Bound:DRAM Bound(%),Memory Bound:Store Bound(%),Loads,Stores,LLC Miss Count,Average Latency (cycles),Module,Function (Full),Source File,Start Address multiply1,141.158325,68.4,0.3,0.0,0.7,62.6,0.0,17134700103,8557046093,4363517696,148.829345,matrix,multiply1,multiply.c,0x401550 interrupt_entry,0.057176,38.4,62.3,0.0,0.0,0.0,0.0,685770,8245855,0,0.0,vmlinux,interrupt_entry,[Unknown],0xffffffff81a00880 apic_timer_interrupt,0.054167,56.3,31.1,31.1,0.0,31.1,0.0,0,0,0,0.0,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81a01a50 swapgs_restore_regs_and_return_to_usermode,0.041127,,0.0,0.0,0.0,0.0,0.0,22673255,3439251,0,7.000000,vmlinux,swapgs_restore_regs_and_return_to_usermode,[Unknown],0xffffffff81a00974 smp_call_function_many,0.025077,,0.0,0.0,0.0,0.0,0.0,2062059,685770,0,0.0,vmlinux,smp_call_function_many,[Unknown],0xffffffff811323e0 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ma' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ Running collection... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah_with_stacks -data-limit 0 -finalization-mode none -- /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/matrix -source-search-dir /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/src Stdout: Addr of buf1 = 0x7f8d3bf9a010 Offs of buf1 = 0x7f8d3bf9a180 Addr of buf2 = 0x7f8d39f99010 Offs of buf2 = 0x7f8d39f991c0 Addr of buf3 = 0x7f8d37f98010 Offs of buf3 = 0x7f8d37f98100 Addr of buf4 = 0x7f8d35f97010 Offs of buf4 = 0x7f8d35f97140 Threads #: 4 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 35.904 seconds Stderr: vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah_with_stacks -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah_with_stacks' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with stacks (Perf) Example of analysis types: Hotspots with knob sampling-mode=hw and knob enable-stack-collection=true, etc. Collection: Ok vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. -------------------------------------------------------------------------------- Running finalization... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah_with_stacks Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah_with_stacks' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-10291-jflmkl110.jf.intel vtune: Executing actions 25 % Loading 'systemcollector-10291-jflmkl110.jf.intel vtune: Executing actions 25 % Loading '10301.perf' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for `libahci.ko' vtune: Warning: Cannot locate debugging information for file `/lib/modules/4.19.0-rc8-custom/kernel/drivers/ata/libahci.ko'. vtune: Executing actions 39 % Resolving information for `libc-2.27.so' vtune: Executing actions 39 % Resolving information for `ld-2.27.so' vtune: Executing actions 39 % Resolving information for `libpthread-2.27.so' vtune: Executing actions 40 % Resolving information for `libpthread-2.27.so' vtune: Executing actions 40 % Resolving information for dangling locations vtune: Executing actions 41 % Resolving information for dangling locations vtune: Executing actions 41 % Resolving information for `e1000e.ko' vtune: Warning: Cannot locate debugging information for file `/lib/modules/4.19.0-rc8-custom/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko'. vtune: Executing actions 42 % Resolving information for `e1000e.ko' vtune: Executing actions 42 % Resolving information for `matrix' vtune: Executing actions 43 % Resolving information for `matrix' vtune: Executing actions 44 % Resolving information for `matrix' vtune: Executing actions 44 % Resolving information for `vmlinux' vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. vtune: Executing actions 45 % Resolving information for `vmlinux' vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 49 % Resolving thread name information vtune: Executing actions 49 % Resolving call target names for dynamic code vtune: Executing actions 51 % Resolving call target names for dynamic code vtune: Executing actions 53 % Resolving call target names for dynamic code vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 54 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 60 % Setting data model parameters vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 62 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 65 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 72 % Updating precomputed scalar metrics vtune: Executing actions 75 % Updating precomputed scalar metrics vtune: Executing actions 75 % Discarding redundant overtime data vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 78 % Saving the result vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. -------------------------------------------------------------------------------- Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah_with_stacks Stdout: Function,CPU Time,CPU Time:Effective Time,CPU Time:Effective Time:Idle,CPU Time:Effective Time:Poor,CPU Time:Effective Time:Ok,CPU Time:Effective Time:Ideal,CPU Time:Effective Time:Over,CPU Time:Spin Time,CPU Time:Overhead Time,Instructions Retired,Microarchitecture Usage(%),Microarchitecture Usage:Microarchitecture Usage(%),Microarchitecture Usage:CPI Rate,Module,Function (Full),Source File,Start Address multiply1,137.577306,137.577306,0.001003,7.889274,0.0,129.687029,0.0,0.0,0.0,68967600000,15.8,15.8,2.021564,matrix,multiply1,multiply.c,0x401550 apic_timer_interrupt,0.362114,0.362114,0.0,0.019059,0.0,0.343056,0.0,0.0,0.0,184600000,20.3,20.3,2.239437,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81a01a50 page_fault,0.104321,0.104321,0.0,0.016049,0.0,0.088272,0.0,0.0,0.0,83200000,20.3,20.3,1.718750,vmlinux,page_fault,[Unknown],0xffffffff81a01070 call_function_interrupt,0.063194,0.063194,0.0,0.002006,0.0,0.061188,0.0,0.0,0.0,7800000,10.5,10.5,7.333333,vmlinux,call_function_interrupt,[Unknown],0xffffffff81a01b10 interrupt_entry,0.045139,0.045139,0.0,0.001003,0.0,0.044136,0.0,0.0,0.0,10400000,1.5,1.5,6.500000,vmlinux,interrupt_entry,[Unknown],0xffffffff81a00880 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_ah_with_stacks' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ Running collection... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_th -data-limit 0 -finalization-mode none -- /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/matrix -source-search-dir /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/samples/en/C++/matrix/src Stdout: Addr of buf1 = 0x7ffae789b010 Offs of buf1 = 0x7ffae789b180 Addr of buf2 = 0x7ffae589a010 Offs of buf2 = 0x7ffae589a1c0 Addr of buf3 = 0x7ffae3899010 Offs of buf3 = 0x7ffae3899100 Addr of buf4 = 0x7ffae1898010 Offs of buf4 = 0x7ffae1898140 Threads #: 4 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 35.043 seconds Stderr: vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_th -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_th' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with context switches (Perf) Example of analysis types: Threading with knob sampling-and-waits=hw Collection: Ok vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. -------------------------------------------------------------------------------- Running finalization... Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_th Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_th' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-10356-jflmkl110.jf.intel vtune: Executing actions 25 % Loading 'systemcollector-10356-jflmkl110.jf.intel vtune: Executing actions 25 % Loading '10366.perf' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for dangling locations vtune: Executing actions 39 % Resolving information for `ld-2.27.so' vtune: Executing actions 40 % Resolving information for `ld-2.27.so' vtune: Executing actions 40 % Resolving information for `e1000e.ko' vtune: Warning: Cannot locate debugging information for file `/lib/modules/4.19.0-rc8-custom/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko'. vtune: Executing actions 41 % Resolving information for `e1000e.ko' vtune: Executing actions 41 % Resolving information for `matrix' vtune: Executing actions 42 % Resolving information for `matrix' vtune: Executing actions 44 % Resolving information for `matrix' vtune: Executing actions 44 % Resolving information for `vmlinux' vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. vtune: Executing actions 45 % Resolving information for `vmlinux' vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 49 % Resolving thread name information vtune: Executing actions 49 % Resolving call target names for dynamic code vtune: Executing actions 51 % Resolving call target names for dynamic code vtune: Executing actions 53 % Resolving call target names for dynamic code vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 54 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 62 % Processing profile metrics and debug information vtune: Executing actions 63 % Processing profile metrics and debug information vtune: Executing actions 63 % Setting data model parameters vtune: Executing actions 64 % Setting data model parameters vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 67 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 73 % Precomputing frequently used data vtune: Executing actions 74 % Precomputing frequently used data vtune: Executing actions 75 % Precomputing frequently used data vtune: Executing actions 76 % Precomputing frequently used data vtune: Executing actions 76 % Updating precomputed scalar metrics vtune: Executing actions 78 % Updating precomputed scalar metrics vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 82 % Discarding redundant overtime data vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 89 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. -------------------------------------------------------------------------------- Command line: /localdisk2/mkl/hsadia/vtune_profiler_2020.0.0.605129/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_th Stdout: Function,CPU Time,CPU Time:Effective Time,CPU Time:Effective Time:Idle,CPU Time:Effective Time:Poor,CPU Time:Effective Time:Ok,CPU Time:Effective Time:Ideal,CPU Time:Effective Time:Over,CPU Time:Spin Time,CPU Time:Overhead Time,Inactive Wait Time,Inactive Wait Time:Inactive Sync Wait Time,Inactive Wait Time:Inactive Sync Wait Time:Idle,Inactive Wait Time:Inactive Sync Wait Time:Poor,Inactive Wait Time:Inactive Sync Wait Time:Ok,Inactive Wait Time:Inactive Sync Wait Time:Ideal,Inactive Wait Time:Inactive Sync Wait Time:Over,Inactive Wait Time:Preemption Wait Time,Inactive Wait Time:Preemption Wait Time:Idle,Inactive Wait Time:Preemption Wait Time:Poor,Inactive Wait Time:Preemption Wait Time:Ok,Inactive Wait Time:Preemption Wait Time:Ideal,Inactive Wait Time:Preemption Wait Time:Over,Inactive Wait Count,Inactive Wait Count:Inactive Sync Wait Count,Inactive Wait Count:Inactive Sync Wait Count:Idle,Inactive Wait Count:Inactive Sync Wait Count:Poor,Inactive Wait Count:Inactive Sync Wait Count:Ok,Inactive Wait Count:Inactive Sync Wait Count:Ideal,Inactive Wait Count:Inactive Sync Wait Count:Over,Inactive Wait Count:Preemption Wait Count,Inactive Wait Count:Preemption Wait Count:Idle,Inactive Wait Count:Preemption Wait Count:Poor,Inactive Wait Count:Preemption Wait Count:Ok,Inactive Wait Count:Preemption Wait Count:Ideal,Inactive Wait Count:Preemption Wait Count:Over,Module,Function (Full),Source File,Start Address multiply1,138.251380,138.251380,0.001003,1.740355,0.0,136.510022,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,matrix,multiply1,multiply.c,0x401550 interrupt_entry,0.040123,0.040123,0.0,0.0,0.0,0.040123,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,interrupt_entry,[Unknown],0xffffffff81a00880 smp_call_function_many,0.026080,0.026080,0.0,0.0,0.0,0.026080,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,smp_call_function_many,[Unknown],0xffffffff811323e0 swapgs_restore_regs_and_return_to_usermode,0.026080,0.026080,0.0,0.003009,0.0,0.023071,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,swapgs_restore_regs_and_return_to_usermode,[Unknown],0xffffffff81a00974 apic_timer_interrupt,0.019059,0.019059,0.0,0.001003,0.0,0.018056,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81a01a50 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/result_th' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok The system is ready to be used for performance analysis with Intel VTune Profiler. Review warnings in the output above to find product limitations, if any. Log location: /tmp/vtune-tmp-root/self-checker-2020.04.14_12.47.50/log.txt