Intel(R) VTune(TM) Profiler Self Check Utility Copyright (C) 2009-2020 Intel Corporation. All rights reserved. Build Number: 613804 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-based 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: /opt/intel/oneapi/vtune/2021.1.1/bin64/amplxe-runss --context-value-list Stdout: targetOS: Linux OS: Linux OSBuildNumber: 48 OSBitness: 64 RootPrivileges: false isPtraceScopeLimited: false isCATSupportedByCPU: false isL3MonitoringSupportedByCPU: false isTSXAvailable: false isPTAvailable: true isHTEnabled: false fpgaOnBoard: None omniPathOnBoard: None genArchOnBoard: 10 pciClassParts: isSGXAvailable: true LinuxRelease: 5.4.48+dg1145 is3DXPPresent: false is3DXP2LMMode: false is3DXPAppDirectMode: false IsNUMANodeWithoutCPUsPresent: false Hypervisor: None PerfmonVersion: 4 isMaxDRAMBandwidthMeasurementSupported: true tidValuesForIO: preferedGpuAdapter: 0:3:0.0 gpuAdapterNameList: 0:3:0.0|Display controller: Intel Corporation Device 18693; isPtraceAvailable: true areGpuHardwareMetricsAvailableList: 0:3:0.0|InitializationError; gpuPlatformIndexList: 0:3:0.0|0; i915Status: KernelNotPatched isFtraceAvailable: ftraceAccessError,debugfsNotAccessible isMdfEtwAvailable: false isCSwitchAvailable: no isGpuBusynessAvailable: i915TracepointsConfigOff,notAccessible isGpuWaitAvailable: no isFunctionTracingAvailable: no isIowaitTracingAvailable: no isVSyncAvailable: no HypervisorType: None isDeviceOrCredentialGuardEnabled: false isSEPDriverAvailable: true SEPDriverVersion: 5.22 isPAXDriverLoaded: true PAXDriverVersion: 1.0 platformType: 122 CPU_NAME: Intel(R) microarchitecture code named Coffeelake PMU: skylake availablePmuTypes: core,cbo,imc,edram,ncu,gt,power referenceFrequency: 3600000000 isPStateAvailable: true isVTSSPPDriverAvailable: true isNMIWatchDogTimerRunning: true LinuxPerfCredentials: User LinuxPerfCapabilities: breakpoint:raw;cpu:raw,format,events,ldlat,frontend;cstate_core:raw,format,events;cstate_pkg:raw,format,events;i915_0000_03_00.0:raw,format,events;intel_bts:raw;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:8,raw,format,events;uncore_imc:raw,format,events;uprobe:raw,format LinuxPerfStackCapabilities: fp,dwarf,lbr areKernelPtrsRestricted: yes LinuxPerfMuxIntervalMs: 4 isAOCLAvailable: false isTPSSAvailable: true isPytraceAvailable: true isGENDebugInfoAvailableList: 0:3:0.0|true; isGTPinCollectionAvailableList: 0:3:0.0|true; forceShowInlines: false isSTTAvailable: no isNnpiHwTraceToolAvailable: false isNnpiTraceToolAvailable: false isEnergyCollectionSupported: true isSocwatchDriverLoaded: true isCPUSupportedBySocwatch: true isIPMWatchReady: false isNvdimmAvailable: false isOsCountersCollectorAvailable: true Getting context values: OK ================================================================================ Check driver: isSEPDriverAvailable: true isPAXDriverLoaded: true Command line: lsmod Stdout: sep5 2121728 0 socperf3 598016 2 sep5,socwatch2_13 Is SEP in lsmod: True Ok ================================================================================ SEP version: Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/sep -version Stdout: Sampling Enabling Product Version: 5.22 Beta built on Nov 10 2020 18:15:43 SEP Driver Version: 5.22 Beta (public) PAX Driver Version: 1.0 Platform type: 122 CPU name: Intel(R) microarchitecture code named Coffeelake PMU: skylake Driver configs: Non-Maskable Interrupt, REGISTER CHECK ON Copyright(C) 2007-2020 Intel Corporation. All rights reserved. Check driver with sep -version: Ok ================================================================================ Running collection... Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -collect performance-snapshot -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ps -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f032e572010 Offs of buf1 = 0x7f032e572180 Addr of buf2 = 0x7f032c571010 Offs of buf2 = 0x7f032c5711c0 Addr of buf3 = 0x7f032a570010 Offs of buf3 = 0x7f032a570100 Addr of buf4 = 0x7f032856f010 Offs of buf4 = 0x7f032856f140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 17.003 seconds Stderr: vtune: Warning: Cannot collect GPU hardware metrics because libmd.so cannot be initialized. Make sure you have installed Metrics Discovery API library from https://github.com/intel/metrics-discovery correctly. See Error Message: Cannot Collect GPU Hardware Metrics help topic for more details. 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-linliu/self-checker-2021.01.08_16.11.52/result_ps -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ps' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis (counting mode) (Intel driver) Example of analysis types: Performance Snapshot Collection: Ok vtune: Warning: Cannot collect GPU hardware metrics because libmd.so cannot be initialized. Make sure you have installed Metrics Discovery API library from https://github.com/intel/metrics-discovery correctly. See Error Message: Cannot Collect GPU Hardware Metrics help topic for more details. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -finalize -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ps Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ps' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Warning: Cannot collect GPU hardware metrics because libmd.so cannot be initialized. Make sure you have installed Metrics Discovery API library from https://github.com/intel/metrics-discovery correctly. See Error Message: Cannot Collect GPU Hardware Metrics help topic for more details. 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-7273-shliclel570.sc' fil vtune: Executing actions 25 % Loading 'systemcollector-7273-shliclel570.sc' fil vtune: Executing actions 25 % Loading '/tmp/vtune-tmp-linliu/self-checker-2021. 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 thread name information vtune: Executing actions 43 % Resolving thread name information vtune: Executing actions 43 % Resolving call target names for dynamic code vtune: Executing actions 48 % Resolving call target names for dynamic code vtune: Executing actions 48 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information 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 59 % 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 collect GPU hardware metrics because libmd.so cannot be initialized. Make sure you have installed Metrics Discovery API library from https://github.com/intel/metrics-discovery correctly. See Error Message: Cannot Collect GPU Hardware Metrics help topic for more details. -------------------------------------------------------------------------------- Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -R summary -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ps Stdout: Elapsed Time: 17.027s IPC: 0.113 | The IPC may be too low. This could be caused by issues such as memory | stalls, instruction starvation, branch misprediction or long latency | instructions. Explore the other hardware-related metrics to identify what | is causing low IPC. | SP GFLOPS: 0.000 DP GFLOPS: 1.011 x87 GFLOPS: 0.000 Average CPU Frequency: 4.600 GHz Effective Logical Core Utilization: 99.1% (7.926 out of 8) Effective Physical Core Utilization: 99.1% (7.926 out of 8) Microarchitecture Usage: 2.8% of Pipeline Slots | You code efficiency on this platform is too low. | | Possible cause: memory stalls, instruction starvation, branch misprediction | or long latency instructions. | | Next steps: Run Microarchitecture Exploration analysis to identify the cause | of the low microarchitecture usage efficiency. | Retiring: 2.8% of Pipeline Slots Front-End Bound: 0.2% of Pipeline Slots Back-End Bound: 96.9% of Pipeline Slots | A significant portion of pipeline slots are remaining empty. When | operations take too long in the back-end, they introduce bubbles in the | pipeline that ultimately cause fewer pipeline slots containing useful | work to be retired per cycle than the machine is capable to support. This | opportunity cost results in slower execution. Long-latency operations | like divides and memory operations can cause this, as can too many | operations being directed to a single execution port (for example, more | multiply operations arriving in the back-end per cycle than the execution | unit can support). | Memory Bound: 92.3% of Pipeline Slots | The metric value is high. This can indicate that the significant | fraction of execution pipeline slots could be stalled due to demand | memory load and stores. Use Memory Access analysis to have the metric | breakdown by memory hierarchy, memory bandwidth information, | correlation by memory objects. | Core Bound: 4.6% of Pipeline Slots Bad Speculation: 0.1% of Pipeline Slots Memory Bound: 92.3% of Pipeline Slots | The metric value is high. This can indicate that the significant fraction of | execution pipeline slots could be stalled due to demand memory load and | stores. Use Memory Access analysis to have the metric breakdown by memory | hierarchy, memory bandwidth information, correlation by memory objects. | L1 Bound: 0.0% of Clockticks L2 Bound: 0.0% of Clockticks L3 Bound: 0.9% of Clockticks DRAM Bound: 90.6% of Clockticks | This metric shows how often CPU was stalled on the main memory (DRAM). | Caching typically improves the latency and increases performance. | DRAM Bandwidth Bound: 0.0% of Elapsed Time Store Bound: 0.0% of Clockticks Vectorization: 0.0% of Packed FP Operations | A significant fraction of floating point arithmetic instructions are scalar. | Use Intel Advisor to see possible reasons why the code was not vectorized. | Instruction Mix SP FLOPs: 0.0% of uOps Packed: 0.0% from SP FP 128-bit: 0.0% from SP FP 256-bit: 0.0% from SP FP Scalar: 100.0% from SP FP | This code has floating point operations and is not vectorized. | Consider using Intel Advisor to vectorize the loops. | DP FLOPs: 24.6% of uOps Packed: 0.0% from DP FP 128-bit: 0.0% from DP FP 256-bit: 0.0% from DP FP Scalar: 100.0% from DP FP | This code has floating point operations and is not vectorized. | Consider using Intel Advisor to vectorize the loops. | x87 FLOPs: 0.0% of uOps Non-FP: 75.4% of uOps FP Arith/Mem Rd Instr. Ratio: 0.984 FP Arith/Mem Wr Instr. Ratio: 1.962 Collection and Platform Info Application Command Line: /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/matrix Operating System: 5.4.48+dg1145 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" Computer Name: shliclel570 Result Size: 3.5 MB Collection start time: 08:11:56 08/01/2021 UTC Collection stop time: 08:12:13 08/01/2021 UTC Collector Type: Event-based counting driver CPU Name: Intel(R) microarchitecture code named Coffeelake Frequency: 3.600 GHz Logical CPU Count: 8 Max DRAM Single-Package Bandwidth: 38.000 GB/s Cache Allocation Technology Level 2 capability: not detected Level 3 capability: not detected Recommendations: Hotspots: Start with Hotspots analysis to understand the efficiency of your algorithm. | Use Hotspots analysis to identify the most time consuming functions. | Drill down to see the time spent on every line of code. Memory Access: The Memory Bound metric is high (92.3%). A significant fraction of execution pipeline slots could be stalled due to demand memory load and stores. | Use Memory Access analysis to measure metrics that can identify memory | access issues. If you want to skip descriptions of detected performance issues in the report, enter: vtune -report summary -report-knob show-issues=false -r . Alternatively, you may view the report in the csv format: vtune -report -format=csv. Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ps' 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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -collect hotspots -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_tpss -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/matrix Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_tpss -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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: Fail ================================================================================ Running collection... Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -collect hotspots -knob sampling-mode=hw -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ah -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f19abc73010 Offs of buf1 = 0x7f19abc73180 Addr of buf2 = 0x7f19a9c72010 Offs of buf2 = 0x7f19a9c721c0 Addr of buf3 = 0x7f19a7c71010 Offs of buf3 = 0x7f19a7c71100 Addr of buf4 = 0x7f19a5c70010 Offs of buf4 = 0x7f19a5c70140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 16.974 seconds Stderr: vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ah -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ah' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis check (Intel driver) Example of analysis types: Hotspots with knob sampling-mode=hw, HPC Performance Characterization, etc. Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -finalize -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ah Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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-7405-shliclel570.sc' fil vtune: Executing actions 25 % Loading 'systemcollector-7405-shliclel570.sc' fil vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t vtune: Executing actions 25 % Loading 'sep7f0df9b4b700.20210108T161220.249121.t 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' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.4.48+dg1145/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko'. vtune: Executing actions 40 % Resolving information for `e1000e' vtune: Executing actions 41 % Resolving information for `e1000e' vtune: Executing actions 41 % Resolving information for `kvm' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.4.48+dg1145/kernel/arch/x86/kvm/kvm.ko'. vtune: Executing actions 42 % Resolving information for `kvm' vtune: Warning: Cannot locate file `sep5.ko'. vtune: Executing actions 42 % Resolving information for `sep5' vtune: Executing actions 44 % Resolving information for `sep5' 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 48 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information 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 62 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 65 % 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 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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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,134.677324,134.677324,0.0,0.185000,3.287008,131.205316,0.0,0.0,0.0,68860800000,2.8,2.8,8.996588,matrix,multiply1,multiply.c,0x401550 smp_call_function_many,0.025000,0.025000,0.0,0.0,0.001000,0.024000,0.0,0.0,0.0,0,0.9,0.9,,vmlinux,smp_call_function_many,[Unknown],0xffffffff8114cc40 call_function_interrupt,0.016000,0.016000,0.0,0.0,0.002000,0.014000,0.0,0.0,0.0,0,4.1,4.1,,vmlinux,call_function_interrupt,[Unknown],0xffffffff81c01d20 native_flush_tlb_one_user,0.010000,0.010000,0.0,0.0,0.0,0.010000,0.0,0.0,0.0,3600000,4.3,4.3,12.777516,vmlinux,native_flush_tlb_one_user,[Unknown],0xffffffff81077960 apic_timer_interrupt,0.009000,0.009000,0.0,0.0,0.0,0.009000,0.0,0.0,0.0,3600000,2.4,2.4,11.499894,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81c01c60 Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -collect uarch-exploration -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ge -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fc111234010 Offs of buf1 = 0x7fc111234180 Addr of buf2 = 0x7fc10f233010 Offs of buf2 = 0x7fc10f2331c0 Addr of buf3 = 0x7fc10d232010 Offs of buf3 = 0x7fc10d232100 Addr of buf4 = 0x7fc10b231010 Offs of buf4 = 0x7fc10b231140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 21.708 seconds Stderr: vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ge -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ge' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis check (Intel driver) Example of analysis types: Microarchitecture Exploration Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -finalize -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ge Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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-7487-shliclel570.sc' fil vtune: Executing actions 25 % Loading 'systemcollector-7487-shliclel570.sc' fil vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t vtune: Executing actions 25 % Loading 'sep7f0277e26700.20210108T161248.063541.t 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 `ld-2.31.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/ld-2.31.so'. vtune: Executing actions 39 % Resolving information for `libc-2.31.so' vtune: Executing actions 39 % Resolving information for `e1000e' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.4.48+dg1145/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko'. vtune: Executing actions 40 % Resolving information for `e1000e' vtune: Executing actions 41 % Resolving information for `e1000e' vtune: Executing actions 41 % Resolving information for `kvm' vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libc-2.31.so'. vtune: Executing actions 42 % Resolving information for `kvm' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.4.48+dg1145/kernel/arch/x86/kvm/kvm.ko'. vtune: Executing actions 43 % Resolving information for `kvm' vtune: Warning: Cannot locate file `sep5.ko'. vtune: Executing actions 43 % Resolving information for `sep5' vtune: Executing actions 44 % Resolving information for `sep5' 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 48 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information 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 62 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 65 % 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 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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ge Stdout: Function,CPU Time,Clockticks,Instructions Retired,CPI Rate,Retiring(%),Retiring:Light Operations(%),Retiring:Light Operations:FP Arithmetic(%),Retiring:Light Operations:FP Arithmetic:FP x87(%),Retiring:Light Operations:FP Arithmetic:FP Scalar(%),Retiring:Light Operations:FP Arithmetic:FP Vector(%),Retiring:Light Operations:Other(%),Retiring:Heavy Operations(%),Retiring:Heavy Operations:Microcode Sequencer(%),Retiring:Heavy Operations: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:Front-End Bandwidth LSD(%),Front-End Bound:Front-End Bandwidth:(Info) DSB Coverage(%),Front-End Bound:Front-End Bandwidth:(Info) LSD 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 0 Ports Utilized:Serializing Operations:Slow Pause(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Mixing Vectors(%),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,170.062409,782359200000,69411600000,11.271303,2.3,2.2,23.3,0.0,23.3,0.0,76.7,0.1,0.1,0.0,0.4,0.1,0.2,0.1,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.3,0.0,0.0,0.0,94.3,0.0,0.1,0.0,0.1,97.2,93.5,0.0,54.7,0.3,54.4,0.0,0.0,0.0,0.0,100.0,0.0,0.4,0.4,6.1,3.7,0.0,92.9,99.3,0.6,0.0,0.7,0.0,0.0,0.1,0.1,0.0,3.7,0.0,3.7,0.1,0.3,0.0,0.1,3.6,2.1,1.1,5.3,8.5,7.9,1.8,2.9,1.1,1.6,1.8,1.1,1.1,0.0,24.9,4600424079.042090,matrix,multiply1,multiply.c,0x401550 call_function_interrupt,0.022000,108000000,3600000,30.000000,7.9,0.8,0.0,0.0,0.0,0.0,100.0,7.0,,0.0,7.9,0.0,31.5,6.3,0.0,0.0,0.0,0.0,0.0,0.0,0.0,7.9,31.5,0.0,0.0,0.0,0.0,0.0,-0.0,0.0,92.1,85.4,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,31.5,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,6.7,0.0,2.5,0.0,31.5,0.0,0.0,0.0,31.5,0.0,7.9,31.5,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,4909079110.909091,vmlinux,call_function_interrupt,[Unknown],0xffffffff81c01d20 smp_call_function_many,0.019000,75600000,0,,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,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,100.0,45.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,45.0,89.9,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.0,0.0,0.0,0.0,0.0,0.0,0.0,3978937805.684211,vmlinux,smp_call_function_many,[Unknown],0xffffffff8114cc40 apic_timer_interrupt,0.017000,57600000,0,,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,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,59.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,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,3388227151.058824,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81c01c60 native_flush_tlb_one_user,0.012000,36000000,3600000,10.000000,0.0,2.5,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,9.4,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,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,94.4,0.0,0.0,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,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,2999992790.000000,vmlinux,native_flush_tlb_one_user,[Unknown],0xffffffff81077960 Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -collect memory-access -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ma -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f660be78010 Offs of buf1 = 0x7f660be78180 Addr of buf2 = 0x7f6609e77010 Offs of buf2 = 0x7f6609e771c0 Addr of buf3 = 0x7f6607e76010 Offs of buf3 = 0x7f6607e76100 Addr of buf4 = 0x7f6605e75010 Offs of buf4 = 0x7f6605e75140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 20.417 seconds Stderr: vtune: Peak bandwidth measurement started. vtune: Peak bandwidth measurement finished. vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ma -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ma' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with uncore events (Intel driver) Example of analysis types: Memory Access Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -finalize -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ma Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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-7570-shliclel570.sc' fil vtune: Executing actions 25 % Loading 'systemcollector-7570-shliclel570.sc' fil vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t vtune: Executing actions 25 % Loading 'sep7f39c4786700.20210108T161325.871922.t 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 `nvme' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.4.48+dg1145/kernel/drivers/nvme/host/nvme.ko'. vtune: Executing actions 40 % Resolving information for `nvme' vtune: Executing actions 40 % Resolving information for `e1000e' vtune: Executing actions 41 % Resolving information for `e1000e' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.4.48+dg1145/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko'. vtune: Executing actions 42 % Resolving information for `e1000e' vtune: Executing actions 42 % Resolving information for `kvm' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.4.48+dg1145/kernel/arch/x86/kvm/kvm.ko'. vtune: Executing actions 43 % Resolving information for `kvm' vtune: Warning: Cannot locate file `sep5.ko'. vtune: Executing actions 43 % Resolving information for `sep5' vtune: Executing actions 44 % Resolving information for `sep5' 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 48 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 54 % Processing profile metrics and debug information vtune: Executing actions 55 % 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 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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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,159.249383,93.2,0.0,0.0,0.5,92.5,0.0,17235217041,8624958741,6056123899,741.312743,matrix,multiply1,multiply.c,0x401550 apic_timer_interrupt,0.018000,0.0,0.0,0.0,0.0,77.8,0.0,0,0,0,0.0,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81c01c60 call_function_interrupt,0.017000,0.0,0.0,23.6,0.0,35.4,0.0,0,700021,0,0.0,vmlinux,call_function_interrupt,[Unknown],0xffffffff81c01d20 page_fault,0.014000,0.0,0.0,55.6,55.6,0.0,0.0,0,0,0,0.0,vmlinux,page_fault,[Unknown],0xffffffff81c01250 native_flush_tlb_one_user,0.011000,0.0,0.0,0.0,0.0,0.0,0.0,700021,0,0,0.0,vmlinux,native_flush_tlb_one_user,[Unknown],0xffffffff81077960 Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fdeeaf08010 Offs of buf1 = 0x7fdeeaf08180 Addr of buf2 = 0x7fdee8f07010 Offs of buf2 = 0x7fdee8f071c0 Addr of buf3 = 0x7fdee6f06010 Offs of buf3 = 0x7fdee6f06100 Addr of buf4 = 0x7fdee4f05010 Offs of buf4 = 0x7fdee4f05140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 22.853 seconds Stderr: vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ah_with_stacks -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ah_with_stacks' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with stacks (Intel driver) Example of analysis types: Hotspots with knob sampling-mode=hw and knob enable-stack-collection=true, etc. Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -finalize -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_ah_with_stacks Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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-7663-shliclel570.sc' fil vtune: Executing actions 25 % Loading 'systemcollector-7663-shliclel570.sc' fil vtune: Executing actions 25 % Loading '7663-7669.0.vtss' file vtune: Executing actions 25 % Loading '7663-7669.1.vtss' 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 `ld-2.31.so' vtune: Executing actions 39 % Resolving information for `nvme' vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/ld-2.31.so'. vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.4.48+dg1145/kernel/drivers/nvme/host/nvme.ko'. vtune: Executing actions 39 % Resolving information for `e1000e' vtune: Executing actions 39 % Resolving information for `libc-2.31.so' vtune: Executing actions 39 % Resolving information for dangling locations vtune: Executing actions 40 % Resolving information for dangling locations vtune: Executing actions 41 % Resolving information for dangling locations vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.4.48+dg1145/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko'. vtune: Executing actions 42 % Resolving information for dangling locations vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libc-2.31.so'. vtune: Executing actions 43 % Resolving information for dangling locations vtune: Warning: Cannot locate file `nvme_core.ko'. vtune: Executing actions 43 % Resolving information for `nvme_core' vtune: Executing actions 44 % Resolving information for `nvme_core' vtune: Warning: Cannot locate file `vtsspp.ko'. vtune: Executing actions 44 % Resolving information for `vtsspp' 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 48 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information 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 62 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 65 % 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 69 % 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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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,178.627721,178.627721,0.001001,5.032838,21.626449,151.967433,0.0,0.0,0.0,69204715359,2.1,2.1,11.875806,matrix,multiply1,multiply.c,0x401550 apic_timer_interrupt,0.177242,0.177242,0.0,0.004006,0.020024,0.153212,0.0,0.0,0.0,69255147,5.2,5.2,12.527788,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81c01c60 page_fault,0.084144,0.084144,0.0,0.001002,0.005008,0.078134,0.0,0.0,0.0,32351758,2.5,2.5,13.679653,vmlinux,page_fault,[Unknown],0xffffffff81c01250 call_function_interrupt,0.062096,0.062096,0.0,0.001002,0.008013,0.053082,0.0,0.0,0.0,25533508,3.8,3.8,11.351471,vmlinux,call_function_interrupt,[Unknown],0xffffffff81c01d20 native_write_msr,0.030052,0.030052,0.0,0.0,0.004007,0.026045,0.0,0.0,0.0,12074738,100.0,100.0,7.473256,vmlinux,native_write_msr,[Unknown],0xffffffff81077a90 Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_th -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.1.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fe87b500010 Offs of buf1 = 0x7fe87b500180 Addr of buf2 = 0x7fe8794ff010 Offs of buf2 = 0x7fe8794ff1c0 Addr of buf3 = 0x7fe8774fe010 Offs of buf3 = 0x7fe8774fe100 Addr of buf4 = 0x7fe8754fd010 Offs of buf4 = 0x7fe8754fd140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 19.983 seconds Stderr: vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_th -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_th' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with context switches (Intel driver) Example of analysis types: Threading with knob sampling-and-waits=hw Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -finalize -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/result_th Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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-7733-shliclel570.sc' fil vtune: Executing actions 25 % Loading 'systemcollector-7733-shliclel570.sc' fil vtune: Executing actions 25 % Loading '7733-7739.0.vtss' file vtune: Executing actions 25 % Loading '7733-7739.1.vtss' 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-2.31.so' vtune: Executing actions 40 % Resolving information for `libc-2.31.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libc-2.31.so'. vtune: Executing actions 42 % Resolving information for `libc-2.31.so' vtune: Warning: Cannot locate file `vtsspp.ko'. vtune: Executing actions 42 % Resolving information for `vtsspp' vtune: Executing actions 43 % Resolving information for `vtsspp' 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 46 % Resolving thread name information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 48 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information 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 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 69 % 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 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: /opt/intel/oneapi/vtune/2021.1.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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,156.748331,156.748331,0.0,0.563555,5.330842,150.853933,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,matrix,multiply1,multiply.c,0x401550 native_write_msr,0.038057,0.038057,0.0,0.0,0.003005,0.035052,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,native_write_msr,[Unknown],0xffffffff81077a90 apic_timer_interrupt,0.019033,0.019033,0.0,0.0,0.0,0.019033,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,apic_timer_interrupt,[Unknown],0xffffffff81c01c60 smp_call_function_many,0.019029,0.019029,0.0,0.0,0.0,0.019029,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,smp_call_function_many,[Unknown],0xffffffff8114cc40 call_function_interrupt,0.016030,0.016030,0.0,0.0,0.001002,0.015028,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,call_function_interrupt,[Unknown],0xffffffff81c01d20 Stderr: vtune: Using result path `/tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/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 check observed a product failure on your system. Review errors in the output above to fix a problem or contact Intel technical support. Log location: /tmp/vtune-tmp-linliu/self-checker-2021.01.08_16.11.52/log.txt