Intel(R) VTune(TM) Profiler Self Check Utility Copyright (C) 2009-2020 Intel Corporation. All rights reserved. Build Number: 619561 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.7.1/bin64/amplxe-runss --context-value-list Stdout: targetOS: Linux OS: Linux OSBuildNumber: 12 OSBitness: 64 RootPrivileges: true isPtraceScopeLimited: false isCATSupportedByCPU: false isL3MonitoringSupportedByCPU: false isTSXAvailable: false isPTAvailable: true isHTEnabled: false fpgaOnBoard: None omniPathOnBoard: None genArchOnBoard: 7 pciClassParts: tidValuesForIO: populatedIoParts: populatedIoUnits: populatedTidValuesForIO: isSGXAvailable: true LinuxRelease: 5.11.12-300.fc34.x86_64 is3DXPPresent: false is3DXP2LMMode: false is3DXPAppDirectMode: false IsNUMANodeWithoutCPUsPresent: false Hypervisor: None PerfmonVersion: 4 isMaxDRAMBandwidthMeasurementSupported: true preferedGpuAdapter: 0:0:2.0 gpuAdapterNameList: 0:0:2.0|CoffeeLake-S GT2 [UHD Graphics 630]; gpuAdapterTileNameList: 0:0:2.0|CoffeeLake-S GT2 [UHD Graphics 630]|0,; isPtraceAvailable: true areGpuHardwareMetricsAvailableList: 0:0:2.0|true; gpuPlatformIndexList: 0:0:2.0|18; i915Status: KernelNotPatched isFtraceAvailable: yes isMdfEtwAvailable: false isCSwitchAvailable: yes isGpuBusynessAvailable: i915TracepointsConfigOff,notAccessible isGpuWaitAvailable: yes isFunctionTracingAvailable: yes isIowaitTracingAvailable: yes isVSyncAvailable: yes HypervisorType: None isDeviceOrCredentialGuardEnabled: false isSEPDriverAvailable: true SEPDriverVersion: 5.28 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: 3000000000 isPStateAvailable: true isVTSSPPDriverAvailable: true isNMIWatchDogTimerRunning: true LinuxPerfCredentials: Unlimited LinuxPerfCapabilities: breakpoint:raw;cpu:raw,format,events,ldlat,frontend;cstate_core:raw,format,events;cstate_pkg:raw,format,events;i915:raw,format,events;intel_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: no LinuxPerfMuxIntervalMs: 1 isPerfPCIeMappingAvailable: false isAOCLAvailable: false isTPSSAvailable: true isPytraceAvailable: true isGENDebugInfoAvailableList: 0:0:2.0|true; isGTPinCollectionAvailableList: 0:0:2.0|true; forceShowInlines: false isSTTAvailable: no isEnergyCollectionSupported: true isSocwatchDriverLoaded: true isCPUSupportedBySocwatch: true isIPMWatchReady: true isNvdimmAvailable: true isOsCountersCollectorAvailable: false Getting context values: OK ================================================================================ Check driver: isSEPDriverAvailable: true isPAXDriverLoaded: true Command line: lsmod Stdout: sep5 2220032 0 socperf3 602112 1 sep5 Is SEP in lsmod: True Ok ================================================================================ SEP version: Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/sep -version Stdout: Sampling Enabling Product Version: 5.28 built on Aug 30 2021 13:28:55 SEP Driver Version: 5.28 (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 ================================================================================ HW event-based analysis (counting mode)... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -collect performance-snapshot -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ps -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7efc48391010 Offs of buf1 = 0x7efc48391180 Addr of buf2 = 0x7efc46390010 Offs of buf2 = 0x7efc463901c0 Addr of buf3 = 0x7efc4438f010 Offs of buf3 = 0x7efc4438f100 Addr of buf4 = 0x7efc4238e010 Offs of buf4 = 0x7efc4238e140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 16.777 seconds Stderr: vtune: Peak bandwidth measurement started. vtune: Peak bandwidth measurement finished. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ps -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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 -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ps Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ps' 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-18673-fedora.sc' file vtune: Executing actions 25 % Loading 'systemcollector-18673-fedora.sc' file vtune: Executing actions 25 % Loading 'gen_metrics0_0_2_0_0.0.vtss' file vtune: Executing actions 25 % Loading '/tmp/vtune-tmp-root/self-checker-2021.11 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 64 % Processing profile metrics and debug information vtune: Executing actions 65 % Processing profile metrics and debug information vtune: Executing actions 67 % Processing profile metrics and debug information vtune: Executing actions 67 % Preparing output tree vtune: Executing actions 67 % Parsing columns in input tree vtune: Executing actions 67 % Creating top-level columns vtune: Executing actions 69 % Creating top-level columns vtune: Executing actions 69 % Creating top-level rows vtune: Executing actions 70 % Creating top-level rows vtune: Executing actions 71 % Creating top-level rows vtune: Executing actions 72 % Creating top-level rows vtune: Executing actions 73 % Creating top-level rows vtune: Executing actions 74 % Creating top-level rows vtune: Executing actions 74 % Preparing output tree vtune: Executing actions 74 % Parsing columns in input tree vtune: Executing actions 74 % Creating top-level columns vtune: Executing actions 76 % Creating top-level columns vtune: Executing actions 76 % Creating top-level rows vtune: Executing actions 77 % Creating top-level rows vtune: Executing actions 78 % Creating top-level rows vtune: Executing actions 78 % Setting data model parameters vtune: Executing actions 78 % Precomputing frequently used data vtune: Executing actions 78 % Precomputing frequently used data vtune: Executing actions 79 % Precomputing frequently used data vtune: Executing actions 80 % Precomputing frequently used data vtune: Executing actions 81 % Precomputing frequently used data vtune: Executing actions 82 % Precomputing frequently used data vtune: Executing actions 83 % Precomputing frequently used data vtune: Executing actions 84 % Precomputing frequently used data vtune: Executing actions 85 % Precomputing frequently used data vtune: Executing actions 86 % Precomputing frequently used data vtune: Executing actions 87 % Precomputing frequently used data vtune: Executing actions 88 % Precomputing frequently used data vtune: Executing actions 89 % Precomputing frequently used data vtune: Executing actions 90 % Precomputing frequently used data vtune: Executing actions 90 % Updating precomputed scalar metrics vtune: Executing actions 92 % Updating precomputed scalar metrics vtune: Executing actions 92 % Discarding redundant overtime data vtune: Executing actions 96 % Discarding redundant overtime data vtune: Executing actions 96 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok -------------------------------------------------------------------------------- Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -R summary -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ps Stdout: Elapsed Time: 16.802s CPU IPC: 0.133 | 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.016 DP GFLOPS: 1.022 x87 GFLOPS: 0.001 Average CPU Frequency: 4.459 GHz GPU Time: 2.5% (0.412s) of Elapsed time | GPU utilization is low. Consider offloading more work to the GPU to | increase overall application performance. | IPC Rate: 1.560 Logical Core Utilization: 97.0% (7.762 out of 8) Physical Core Utilization: 97.0% (7.762 out of 8) Microarchitecture Usage: 3.3% 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: 3.3% of Pipeline Slots Front-End Bound: 1.5% of Pipeline Slots Bad Speculation: 0.2% of Pipeline Slots Back-End Bound: 94.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: 89.1% 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 FB Full: 100.0% of Clockticks L2 Bound: 0.0% of Clockticks L3 Bound: 1.0% of Clockticks Contested Accesses: 0.8% of Clockticks Data Sharing: 9.9% of Clockticks L3 Latency: 7.3% of Clockticks DRAM Bound: 88.7% of Clockticks | This metric shows how often CPU was stalled on the main memory | (DRAM). Caching typically improves the latency and increases | performance. | Memory Bandwidth: 97.3% of Clockticks | Issue: A significant fraction of cycles was stalled due to | approaching bandwidth limits of the main memory (DRAM). | | Tips: Improve data accesses to reduce cacheline transfers | from/to memory using these possible techniques: | - Consume all bytes of each cacheline before it is | evicted (for example, reorder structure elements and | split non-hot ones). | - Merge compute-limited and bandwidth-limited loops. | - Use NUMA optimizations on a multi-socket system. | | Note: software prefetches do not help a bandwidth-limited | application. | Memory Latency: 2.1% of Clockticks Store Bound: 0.0% of Clockticks Core Bound: 5.8% of Pipeline Slots Memory Bound: 89.1% 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. | Cache Bound: 1.0% of Clockticks DRAM Bound: 88.7% of Clockticks | The metric value is high. This indicates that a significant fraction of | cycles could be stalled on the main memory (DRAM) because of demand loads | or stores. | | The code is memory bandwidth bound, which means that there are a | significant fraction of cycles during which the bandwidth limits of the | main memory are being reached and the code could stall. Review the | Bandwidth Utilization Histogram to estimate the scale of the issue. | Improve data accesses to reduce cacheline transfers from/to memory using | these possible techniques: 1) consume all bytes of each cacheline before | it is evicted (for example, reorder structure elements and split non-hot | ones); 2) merge compute-limited and bandwidth-limited loops; 3) use NUMA | optimizations on a multi-socket system. | Average DRAM Bandwidth, GB/s: 26.613 Vectorization: 0.2% of Packed FP Operations | A significant fraction of floating point arithmetic instructions are scalar. | This indicates that the code was not fully vectorized. Use Intel Advisor to | see possible reasons why the code was not vectorized. | Instruction Mix SP FLOPs: 0.1% of uOps Packed: 92.4% from SP FP 128-bit: 36.2% from SP FP | A significant fraction of floating point arithmetic vector | instructions is executed with a partial vector load. Make | sure you compile the code with the latest instruction set or | use Intel Advisor for vectorization help. | 256-bit: 56.1% from SP FP Scalar: 7.6% from SP FP DP FLOPs: 22.0% 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 | A significant fraction of floating point arithmetic instructions | are scalar. This indicates that the code was not fully | vectorized. Use Intel Advisor to see possible reasons why the | code was not vectorized. | x87 FLOPs: 0.0% of uOps Non-FP: 77.9% of uOps FP Arith/Mem Rd Instr. Ratio: 0.892 FP Arith/Mem Wr Instr. Ratio: 1.788 GPU Active Time: 2.5% | GPU utilization is low. Consider offloading more work to the GPU to increase | overall application performance. | GPU Utilization when Busy: 48.3% | The percentage of time when the EUs were stalled or idle is high, which | has a negative impact on compute-bound applications. | IPC Rate: 1.560 EU State: 48.3% Active: 48.3% Stalled: 46.5% | A significant portion of GPU time is lost due to stalls. Use GPU | Compute/Media Hotspots (preview) analysis to analyze HW usage | efficiency. | Idle: 5.3% | A significant portion of GPU time is spent idle. This is usually | caused by imbalance or thread scheduling problems. | Occupancy: 84.4% of peak value | Several factors including shared local memory, use of memory barriers, | and inefficient work scheduling can cause a low value of the occupancy | metric. | Collection and Platform Info Application Command Line: /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/matrix Operating System: 5.11.12-300.fc34.x86_64 Computer Name: fedora Result Size: 3.7 MB Collection start time: 07:06:36 09/11/2021 UTC Collection stop time: 07:06:53 09/11/2021 UTC Collector Type: Event-based sampling driver,Event-based counting driver CPU Name: Intel(R) microarchitecture code named Coffeelake Frequency: 3.000 GHz Logical CPU Count: 8 Max DRAM Single-Package Bandwidth: 37.000 GB/s Cache Allocation Technology Level 2 capability: not detected Level 3 capability: not detected GPU Name: CoffeeLake-S GT2 [UHD Graphics 630] Vendor: Intel Corporation EU Count: 24 Max EU Thread Count: 7 Max Core Frequency: 1.200 GHz 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 (89.1%). 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. HPC Performance Characterization: Vectorization (0.2%) is low. A significant fraction of floating point arithmetic instructions are scalar. This indicates that the code was not fully vectorized. Use Intel Advisor to see possible reasons why the code was not vectorized. | Use HPC Performance Characterization analysis to examine the performance | of compute-intensive applications. Understand CPU/GPU utilization and get | information about OpenMP efficiency, memory access, and vectorization. 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-root/self-checker-2021.11.09_13.06.31/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 ================================================================================ Instrumentation based analysis check... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -collect hotspots -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_tpss -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f1a17096010 Offs of buf1 = 0x7f1a17096180 Addr of buf2 = 0x7f1a15095010 Offs of buf2 = 0x7f1a150951c0 Addr of buf3 = 0x7f1a13094010 Offs of buf3 = 0x7f1a13094100 Addr of buf4 = 0x7f1a11093010 Offs of buf4 = 0x7f1a11093140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 7.640 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_tpss -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_tpss' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done Instrumentation based analysis check Example of analysis types: Hotspots and Threading with user-mode sampling Collection: Ok -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_tpss Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_tpss' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-18778-fedora.sc' file vtune: Executing actions 25 % Loading 'systemcollector-18778-fedora.sc' file vtune: Executing actions 25 % Loading '18778-18783.0.trace' file vtune: Executing actions 25 % Loading '/tmp/vtune-tmp-root/self-checker-2021.11 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 `libpthread.so.0' vtune: Executing actions 39 % Resolving information for `libc.so.6' vtune: Warning: Cannot locate debugging information for file `/lib64/libpthread.so.0'. vtune: Executing actions 41 % Resolving information for `libc.so.6' vtune: Executing actions 43 % Resolving information for `libc.so.6' vtune: Warning: Cannot locate debugging information for file `/lib64/libc.so.6'. vtune: Executing actions 45 % Resolving information for `libc.so.6' 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 49 % Resolving call target names for dynamic code vtune: Executing actions 49 % 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 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 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 73 % 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 -------------------------------------------------------------------------------- Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_tpss Stdout: Function,CPU Time,CPU Time:Effective Time,CPU Time:Effective Time:Idle,CPU Time:Effective Time:Poor,CPU Time:Effective Time:Ok,CPU Time:Effective Time:Ideal,CPU Time:Effective Time:Over,CPU Time:Spin Time,CPU Time:Overhead Time,Module,Function (Full),Source File,Start Address multiply1,59.980000,59.980000,0.0,0.240019,2.620708,57.119273,0.0,0.0,0.0,matrix,multiply1,multiply.c,0x401550 init_arr,0.010000,0.010000,0.0,0.010000,0.0,0.0,0.0,0.0,0.0,matrix,init_arr,matrix.c,0x400d4f Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_tpss' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ HW event-based analysis check... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -collect hotspots -knob sampling-mode=hw -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ah -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f30134d0010 Offs of buf1 = 0x7f30134d0180 Addr of buf2 = 0x7f30114cf010 Offs of buf2 = 0x7f30114cf1c0 Addr of buf3 = 0x7f300f4ce010 Offs of buf3 = 0x7f300f4ce100 Addr of buf4 = 0x7f300d4cd010 Offs of buf4 = 0x7f300d4cd140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 7.918 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-root/self-checker-2021.11.09_13.06.31/result_ah -command stop. /etc/redhat-release is a symlink. Please provide the file with actual path vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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 HW event-based sampling, 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.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ah Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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-18871-fedora.sc' file vtune: Executing actions 25 % Loading 'systemcollector-18871-fedora.sc' file vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.t vtune: Executing actions 25 % Loading 'sep7ff6c2c1c640.20211109T130711.168063.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 40 % Resolving information for `matrix' vtune: Warning: Cannot locate file `drm.ko'. vtune: Warning: Cannot locate file `nf_tables.ko'. vtune: Executing actions 40 % Resolving information for `drm' vtune: Executing actions 40 % Resolving information for `nf_tables' vtune: Executing actions 42 % Resolving information for `nf_tables' vtune: Executing actions 43 % Resolving information for `nf_tables' 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 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.7.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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,62.191040,62.191040,0.001000,0.259000,6.447004,55.484036,0.0,0.0,0.0,68748000000,6.3,6.3,3.997539,matrix,multiply1,multiply.c,0x401550 update_cfs_group,0.016000,0.016000,0.0,0.0,0.002000,0.014000,0.0,0.0,0.0,27000000,7.1,7.1,2.617761,vmlinux,update_cfs_group,[Unknown],0xffffffffa7118f50 update_curr,0.015000,0.015000,0.0,0.0,0.0,0.015000,0.0,0.0,0.0,36000000,16.6,16.6,1.844342,vmlinux,update_curr,[Unknown],0xffffffffa7118c40 smp_call_function_many_cond,0.012000,0.012000,0.0,0.0,0.0,0.012000,0.0,0.0,0.0,9000000,1.9,1.9,5.915266,vmlinux,smp_call_function_many_cond,[Unknown],0xffffffffa7181b40 sync_regs,0.012000,0.012000,0.0,0.001000,0.001000,0.010000,0.0,0.0,0.0,0,9.4,9.4,,vmlinux,sync_regs,[Unknown],0xffffffffa7bc7730 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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 ================================================================================ HW event-based analysis check... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -collect uarch-exploration -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ge -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fceeb30c010 Offs of buf1 = 0x7fceeb30c180 Addr of buf2 = 0x7fcee930b010 Offs of buf2 = 0x7fcee930b1c0 Addr of buf3 = 0x7fcee730a010 Offs of buf3 = 0x7fcee730a100 Addr of buf4 = 0x7fcee5309010 Offs of buf4 = 0x7fcee5309140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 8.691 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-root/self-checker-2021.11.09_13.06.31/result_ge -command stop. /etc/redhat-release is a symlink. Please provide the file with actual path vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ge Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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-18970-fedora.sc' file vtune: Executing actions 25 % Loading 'systemcollector-18970-fedora.sc' file vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.t vtune: Executing actions 25 % Loading 'sep7f4c78780640.20211109T130727.903834.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: Warning: Cannot locate file `i915.ko'. vtune: Warning: Cannot locate file `e1000e.ko'. vtune: Warning: Cannot locate file `drm.ko'. vtune: Warning: Cannot locate file `nouveau.ko'. vtune: Warning: Cannot locate file `sep5.ko'. vtune: Warning: Cannot locate file `nf_conntrack.ko'. vtune: Executing actions 39 % Resolving information for `i915' vtune: Executing actions 39 % Resolving information for `e1000e' vtune: Executing actions 39 % Resolving information for `drm' vtune: Executing actions 39 % Resolving information for `nouveau' vtune: Executing actions 39 % Resolving information for `sep5' vtune: Executing actions 39 % Resolving information for `nf_conntrack' vtune: Warning: Cannot locate file `ip_tables.ko'. vtune: Executing actions 39 % Resolving information for `ip_tables' vtune: Executing actions 40 % Resolving information for `ip_tables' vtune: Executing actions 41 % Resolving information for `ip_tables' vtune: Executing actions 42 % Resolving information for `ip_tables' vtune: Executing actions 43 % Resolving information for `ip_tables' vtune: Executing actions 43 % Resolving information for `matrix' vtune: Executing actions 44 % Resolving information for `matrix' vtune: Executing actions 44 % Resolving information for `vmlinux' vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions. vtune: Executing actions 45 % Resolving information for `vmlinux' vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 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.7.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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,66.928044,295386000000,69075000000,4.276308,6.1,5.8,23.7,0.0,23.7,0.0,76.3,0.2,0.1,0.0,0.5,0.2,0.2,0.1,0.1,0.0,0.0,0.0,0.1,0.0,0.0,0.3,0.0,0.0,0.0,96.9,0.0,0.2,0.0,0.2,93.3,83.8,1.1,0.0,0.0,76.9,0.0,0.0,0.0,0.1,100.0,0.0,12.2,1.2,39.4,42.3,0.0,69.4,97.9,1.9,0.1,0.6,0.0,0.0,0.1,0.0,0.1,9.4,0.0,9.3,1.2,0.2,0.0,0.0,7.8,5.7,3.3,10.7,15.9,15.1,4.5,7.2,3.0,4.4,4.4,2.9,2.9,0.0,25.0,4413486253.871325,matrix,multiply1,multiply.c,0x401550 update_curr,0.022000,99000000,24000000,4.125000,8.6,6.1,0.0,0.0,0.0,0.0,100.0,2.5,0.0,0.0,34.3,34.3,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,8.6,0.0,8.6,48.5,32.3,0.0,100.0,100.0,20.6,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,25.1,0.0,0.0,0.0,34.3,0.0,0.0,0.0,0.0,0.0,0.0,0.0,16.2,0.0,34.3,34.3,0.0,0.0,0.0,0.0,0.0,0.0,34.3,34.3,0.0,34.3,68.7,17.2,34.3,0.0,0.0,0.0,0.0,0.0,4499997075.000000,vmlinux,update_curr,[Unknown],0xffffffffa7118c40 asm_sysvec_apic_timer_interrupt,0.021000,111000000,0,,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,23.0,30.6,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,7.7,0.0,7.7,69.4,34.7,0.0,0.0,0.0,3.1,0.0,0.0,0.0,0.0,0.0,30.6,30.6,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,34.7,0.0,30.6,30.6,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,5285710850.000000,vmlinux,asm_sysvec_apic_timer_interrupt,[Unknown],0xffffffffa7c00d30 update_load_avg,0.020000,69000000,27000000,2.555556,24.6,9.8,0.0,0.0,0.0,0.0,100.0,14.9,0.0,0.0,37.0,0.0,0.0,4.9,0.0,0.0,0.0,0.0,0.0,0.0,0.0,37.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,38.4,,0.0,0.0,0.0,7.4,0.0,0.0,0.0,0.0,0.0,49.3,0.0,0.0,0.0,0.0,0.0,49.3,49.3,49.3,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,12.3,0.0,0.0,0.0,49.3,0.0,0.0,49.3,49.3,49.3,0.0,0.0,3449997757.500000,vmlinux,update_load_avg,[Unknown],0xffffffffa71178a0 smp_call_function_many_cond,0.018000,63000000,3000000,21.000000,0.0,1.2,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,5.4,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,27.0,0.0,0.0,0.0,0.0,13.5,0.0,13.5,86.5,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,2.7,0.0,2.7,86.5,0.0,100.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,0.0,0.0,0.0,0.0,0.0,0.0,0.0,3499997725.000000,vmlinux,smp_call_function_many_cond,[Unknown],0xffffffffa7181b40 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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 ================================================================================ HW event-based analysis with uncore events... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -collect memory-access -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ma -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f88eed67010 Offs of buf1 = 0x7f88eed67180 Addr of buf2 = 0x7f88ecd66010 Offs of buf2 = 0x7f88ecd661c0 Addr of buf3 = 0x7f88ead65010 Offs of buf3 = 0x7f88ead65100 Addr of buf4 = 0x7f88e8d64010 Offs of buf4 = 0x7f88e8d64140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 8.160 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-root/self-checker-2021.11.09_13.06.31/result_ma -command stop. /etc/redhat-release is a symlink. Please provide the file with actual path vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ma Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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-19061-fedora.sc' file vtune: Executing actions 25 % Loading 'systemcollector-19061-fedora.sc' file vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.t vtune: Executing actions 25 % Loading 'sep7f125a62f640.20211109T130750.317453.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 `libc-2.33.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib64/libc-2.33.so'. vtune: Executing actions 39 % Resolving information for dangling locations vtune: Executing actions 40 % Resolving information for dangling locations vtune: Warning: Cannot locate file `drm.ko'. vtune: Executing actions 40 % Resolving information for `drm' vtune: Warning: Cannot locate file `drm_kms_helper.ko'. vtune: Executing actions 40 % Resolving information for `drm_kms_helper' vtune: Warning: Cannot locate file `nf_defrag_ipv4.ko'. vtune: Warning: Cannot locate file `sep5.ko'. vtune: Executing actions 40 % Resolving information for `sep5' vtune: Executing actions 40 % Resolving information for `nf_defrag_ipv4' vtune: Warning: Cannot locate file `nf_tables.ko'. vtune: Executing actions 40 % Resolving information for `nf_tables' vtune: Executing actions 41 % Resolving information for `nf_tables' vtune: Executing actions 41 % Resolving information for `libgcc_s-11-20210728.s vtune: Executing actions 42 % Resolving information for `libgcc_s-11-20210728.s vtune: Warning: Cannot locate debugging information for file `/usr/lib64/libgcc_s-11-20210728.so.1'. vtune: Executing actions 43 % Resolving information for `libgcc_s-11-20210728.s vtune: Warning: Cannot locate file `i915.ko'. vtune: Executing actions 43 % Resolving information for `i915' vtune: Executing actions 44 % Resolving information for `i915' vtune: Warning: Cannot locate file `e1000e.ko'. vtune: Executing actions 44 % Resolving information for `e1000e' vtune: Warning: Cannot locate file `iptable_raw.ko'. vtune: Executing actions 44 % Resolving information for `iptable_raw' vtune: Executing actions 45 % Resolving information for `iptable_raw' vtune: Executing actions 45 % 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 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.7.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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,55.171036,79.4,0.0,0.0,18.7,61.4,0.0,17065811959,8534656032,1701819119,163.695149,matrix,multiply1,multiply.c,0x401550 update_curr,0.050000,90.5,13.9,34.8,0.0,55.7,0.0,4900147,7700231,0,0.0,vmlinux,update_curr,[Unknown],0xffffffffa7118c40 update_load_avg,0.036000,,0.0,8.0,32.2,32.2,0.0,14000420,0,0,7.666667,vmlinux,update_load_avg,[Unknown],0xffffffffa71178a0 [i915],0.023000,18.5,31.1,0.0,46.7,77.8,0.0,700021,700021,0,0.0,i915,[i915],[Unknown],0x0 asm_sysvec_apic_timer_interrupt,0.021000,18.0,0.0,20.3,40.6,40.6,0.0,0,0,0,0.0,vmlinux,asm_sysvec_apic_timer_interrupt,[Unknown],0xffffffffa7c00d30 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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 ================================================================================ HW event-based analysis with stacks... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f83e5e1f010 Offs of buf1 = 0x7f83e5e1f180 Addr of buf2 = 0x7f83e3e1e010 Offs of buf2 = 0x7f83e3e1e1c0 Addr of buf3 = 0x7f83e1e1d010 Offs of buf3 = 0x7f83e1e1d100 Addr of buf4 = 0x7f83dfe1c010 Offs of buf4 = 0x7f83dfe1c140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 17.954 seconds Stderr: vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ah_with_stacks -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ah_with_stacks' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with stacks (Perf) Example of analysis types: Hotspots with HW event-based sampling and call stacks Collection: Ok vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_ah_with_stacks Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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-19161-fedora.sc' file vtune: Executing actions 25 % Loading 'systemcollector-19161-fedora.sc' file vtune: Executing actions 25 % Loading '19170.perf' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for dangling locations vtune: Executing actions 39 % Resolving information for `ld-2.33.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib64/ld-2.33.so'. vtune: Executing actions 39 % Resolving information for `libc-2.33.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib64/libc-2.33.so'. vtune: Warning: Cannot locate file `nf_nat.ko'. vtune: Executing actions 39 % Resolving information for `nf_nat' vtune: Warning: Cannot locate file `ip_tables.ko'. vtune: Executing actions 39 % Resolving information for `ip_tables' vtune: Warning: Cannot locate file `nouveau.ko'. vtune: Executing actions 39 % Resolving information for `nouveau' vtune: Warning: Cannot locate file `i915.ko'. vtune: Executing actions 39 % Resolving information for `i915' vtune: Executing actions 40 % Resolving information for `i915' vtune: Warning: Cannot locate file `drm_kms_helper.ko'. vtune: Executing actions 40 % Resolving information for `drm_kms_helper' vtune: Executing actions 40 % Resolving information for `libpthread-2.33.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib64/libpthread-2.33.so'. vtune: Executing actions 40 % Resolving information for `libm-2.33.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib64/libm-2.33.so'. vtune: Executing actions 41 % Resolving information for `libm-2.33.so' vtune: Executing actions 41 % Resolving information for `matrix' vtune: Executing actions 42 % Resolving information for `matrix' vtune: Warning: Cannot locate file `e1000e.ko'. vtune: Warning: Cannot locate file `nft_chain_nat.ko'. vtune: Executing actions 42 % Resolving information for `nft_chain_nat' vtune: Executing actions 42 % Resolving information for `e1000e' vtune: Executing actions 43 % Resolving information for `e1000e' vtune: Warning: Cannot locate file `nf_tables.ko'. vtune: Executing actions 43 % Resolving information for `nf_tables' vtune: Executing actions 44 % Resolving information for `nf_tables' vtune: Warning: Cannot locate file `nvme.ko'. vtune: Executing actions 44 % Resolving information for `nvme' vtune: Warning: Cannot locate file `drm.ko'. vtune: Warning: Cannot locate file `nf_conntrack.ko'. vtune: Executing actions 44 % Resolving information for `drm' vtune: Executing actions 44 % Resolving information for `nf_conntrack' vtune: Executing actions 45 % Resolving information for `nf_conntrack' vtune: Executing actions 45 % 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 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 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.7.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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,124.186081,124.186081,0.001000,14.226009,54.380035,55.579036,0.0,0.0,0.0,69057000000,4.1,4.1,7.936412,matrix,multiply1,multiply.c,0x401550 asm_sysvec_apic_timer_interrupt,0.927001,0.875001,0.0,0.095000,0.404000,0.376000,0.0,0.052000,0.0,1083000000,12.2,12.2,3.680523,vmlinux,asm_sysvec_apic_timer_interrupt,[Unknown],0xffffffffa7c00d30 asm_exc_page_fault,0.133000,0.132000,0.001000,0.021000,0.051000,0.059000,0.0,0.001000,0.0,114000000,6.0,6.0,4.929832,vmlinux,asm_exc_page_fault,[Unknown],0xffffffffa7c00ac0 [i915],0.064000,0.064000,0.0,0.004000,0.028000,0.032000,0.0,0.0,0.0,9000000,1.7,1.7,33.111161,i915,[i915],[Unknown],0x0 asm_sysvec_reschedule_ipi,0.056000,0.006000,0.0,0.002000,0.004000,0.0,0.0,0.050000,0.0,69000000,12.3,12.3,4.376818,vmlinux,asm_sysvec_reschedule_ipi,[Unknown],0xffffffffa7c00d70 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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 ================================================================================ HW event-based analysis with context switches... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_th -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fe68e906010 Offs of buf1 = 0x7fe68e906180 Addr of buf2 = 0x7fe68c905010 Offs of buf2 = 0x7fe68c9051c0 Addr of buf3 = 0x7fe68a904010 Offs of buf3 = 0x7fe68a904100 Addr of buf4 = 0x7fe688903010 Offs of buf4 = 0x7fe688903140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 18.070 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-root/self-checker-2021.11.09_13.06.31/result_th -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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 HW event-based sampling 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.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/result_th Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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-19252-fedora.sc' file vtune: Executing actions 25 % Loading 'systemcollector-19252-fedora.sc' file vtune: Executing actions 25 % Loading '19252-19258.0.vtss' file vtune: Executing actions 25 % Loading '19252-19258.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.33.so' vtune: Executing actions 39 % Resolving information for `ld-2.33.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib64/ld-2.33.so'. vtune: Warning: Cannot locate debugging information for file `/usr/lib64/libc-2.33.so'. vtune: Executing actions 40 % Resolving information for `ld-2.33.so' vtune: Warning: Cannot locate file `nf_tables.ko'. vtune: Executing actions 40 % Resolving information for `nf_tables' vtune: Executing actions 41 % Resolving information for `nf_tables' vtune: Warning: Cannot locate file `drm.ko'. vtune: Executing actions 41 % Resolving information for `drm' vtune: Executing actions 42 % Resolving information for `drm' vtune: Warning: Cannot locate file `ip_tables.ko'. vtune: Executing actions 42 % Resolving information for `ip_tables' vtune: Executing actions 43 % Resolving information for `ip_tables' vtune: Warning: Cannot locate file `i915.ko'. vtune: Executing actions 43 % Resolving information for `i915' vtune: Warning: Cannot locate file `vtsspp.ko'. vtune: Executing actions 43 % Resolving information for `vtsspp' vtune: Executing actions 44 % Resolving information for `vtsspp' vtune: Warning: Cannot locate file `e1000e.ko'. vtune: Executing actions 44 % Resolving information for `e1000e' vtune: Executing actions 45 % Resolving information for `e1000e' vtune: Executing actions 45 % 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 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 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 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.7.1/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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,130.751285,130.751285,0.0,8.793792,50.665099,71.292395,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,matrix,multiply1,multiply.c,0x401550 [vtsspp],0.088001,0.088001,0.0,0.014023,0.051427,0.022551,0.0,0.0,0.0,8.956622,0.411171,0.000471,0.410700,0.0,0.0,0.0,8.545451,0.000724,1.904825,5.794380,0.845522,0.0,49569,2,0,2,0,0,0,49567,3,6319,27141,16104,0,vtsspp,[vtsspp],[Unknown],0x0 [i915],0.078111,0.078111,0.0,0.003004,0.027041,0.048066,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,i915,[i915],[Unknown],0x0 update_load_avg,0.072094,0.072094,0.0,0.009010,0.034045,0.029039,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,update_load_avg,[Unknown],0xffffffffa71178a0 update_curr,0.071086,0.071086,0.0,0.007009,0.036042,0.028035,0.0,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,update_curr,[Unknown],0xffffffffa7118c40 Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/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 Checking DPC++ application as prerequisite for GPU analyses... Setting envirnoment variable: SYCL_DEVICE_FILTER=gpu:level_zero Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stderr: /opt/intel/oneapi/vtune/2021.7.1/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libimf.so: cannot open shared object file: No such file or directory Checking DPC++ application as prerequisite for GPU analyses: Fail Unable to run DPC++ application on GPU connected to this system. If you are using an Intel GPU and want to verify profiling support for DPC++ applications, check these requirements: * Install Intel(R) GPU driver. * Install Intel(R) Level Zero GPU runtime. * Install Intel(R) oneAPI DPC++ Runtime and set the environment. The system is ready to be used for performance analysis with Intel VTune Profiler. Review warnings in the output above to find product limitations, if any. The system is ready for the following analyses: * Performance Snapshot * Hotspots and Threading with user-mode sampling * Hotspots with HW event-based sampling, HPC Performance Characterization, etc. * Microarchitecture Exploration * Memory Access * Hotspots with HW event-based sampling and call stacks * Threading with HW event-based sampling The following analyses have failed on the system: * GPU Compute/Media Hotspots (characterization mode) * GPU Compute/Media Hotspots (source analysis mode) Log location: /tmp/vtune-tmp-root/self-checker-2021.11.09_13.06.31/log.txt