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: 0 OSBitness: 64 RootPrivileges: false isPtraceScopeLimited: false isCATSupportedByCPU: false isL3MonitoringSupportedByCPU: false isTSXAvailable: false isPTAvailable: true isHTEnabled: true fpgaOnBoard: None omniPathOnBoard: None genArchOnBoard: 0 pciClassParts: tidValuesForIO: populatedIoParts: populatedIoUnits: populatedTidValuesForIO: isSGXAvailable: true LinuxRelease: 5.11.0-36-generic is3DXPPresent: false is3DXP2LMMode: false is3DXPAppDirectMode: false IsNUMANodeWithoutCPUsPresent: false Hypervisor: None PerfmonVersion: 4 isMaxDRAMBandwidthMeasurementSupported: true preferedGpuAdapter: none isPtraceAvailable: true i915Status: MissingDriver isFtraceAvailable: ftraceAccessError,debugfsNotAccessible isMdfEtwAvailable: false isCSwitchAvailable: no isGpuBusynessAvailable: unsupportedHardware isGpuWaitAvailable: no isFunctionTracingAvailable: no isIowaitTracingAvailable: no isVSyncAvailable: no HypervisorType: None isDeviceOrCredentialGuardEnabled: false isSEPDriverAvailable: true SEPDriverVersion: 5.28 isPAXDriverLoaded: true PAXDriverVersion: 1.0 platformType: 136 CPU_NAME: Intel(R) microarchitecture code named Cometlake H/S PMU: skylake availablePmuTypes: core,cbo,imc,edram,ncu,gt,power referenceFrequency: 2900000000 isPStateAvailable: true isVTSSPPDriverAvailable: true isNMIWatchDogTimerRunning: false LinuxPerfCredentials: Cpu LinuxPerfCapabilities: breakpoint:raw;cpu:raw,format,events,ldlat,frontend;cstate_core:raw,format,events;cstate_pkg: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:6,raw,format,events;uncore_imc:raw,format,events;uprobe:raw,format LinuxPerfStackCapabilities: fp,dwarf,lbr areKernelPtrsRestricted: yes LinuxPerfMuxIntervalMs: 4 isPerfPCIeMappingAvailable: false isAOCLAvailable: false isTPSSAvailable: true isPytraceAvailable: true forceShowInlines: false isSTTAvailable: no isEnergyCollectionSupported: true isSocwatchDriverLoaded: true isCPUSupportedBySocwatch: true isIPMWatchReady: false isNvdimmAvailable: true isOsCountersCollectorAvailable: false Getting context values: OK ================================================================================ Check driver: isSEPDriverAvailable: true isPAXDriverLoaded: true Command line: lsmod Stdout: sep5 2224128 0 socperf3 602112 1 sep5 pinctrl_sunrisepoint 28672 0 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: 136 CPU name: Intel(R) microarchitecture code named Cometlake H/S 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-jay/self-checker-2021.10.01_12.17.20/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 = 0x7f185245c010 Offs of buf1 = 0x7f185245c180 Addr of buf2 = 0x7f185045b010 Offs of buf2 = 0x7f185045b1c0 Addr of buf3 = 0x7f184e45a010 Offs of buf3 = 0x7f184e45a100 Addr of buf4 = 0x7f184c459010 Offs of buf4 = 0x7f184c459140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 10.401 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-jay/self-checker-2021.10.01_12.17.20/result_ps -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-jay/self-checker-2021.10.01_12.17.20/result_ps Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-36967-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading 'systemcollector-36967-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading '/tmp/vtune-tmp-jay/self-checker-2021.10. 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 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 -------------------------------------------------------------------------------- Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -R summary -r /tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/result_ps Stdout: Elapsed Time: 10.470s IPC: 0.391 | 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.040 DP GFLOPS: 1.615 x87 GFLOPS: 0.004 Average CPU Frequency: 3.991 GHz Logical Core Utilization: 88.7% (10.648 out of 12) Physical Core Utilization: 95.5% (5.729 out of 6) Microarchitecture Usage: 17.7% 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: 17.7% of Pipeline Slots Front-End Bound: 18.0% of Pipeline Slots Bad Speculation: 3.6% of Pipeline Slots Back-End Bound: 60.7% 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: 48.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: 7.7% of Clockticks FB Full: 100.0% of Clockticks L2 Bound: 0.3% of Clockticks L3 Bound: 17.0% of Clockticks | This metric shows how often CPU was stalled on L3 cache, or | contended with a sibling Core. Avoiding cache misses (L2 | misses/L3 hits) improves the latency and increases performance. | Contested Accesses: 1.1% of Clockticks Data Sharing: 2.7% of Clockticks L3 Latency: 39.1% of Clockticks | This metric shows a fraction of cycles with demand load | accesses that hit the L3 cache under unloaded scenarios | (possibly L3 latency limited). Avoiding private cache misses | (i.e. L2 misses/L3 hits) will improve the latency, reduce | contention with sibling physical cores and increase | performance. Note the value of this node may overlap with its | siblings. | DRAM Bound: 45.0% 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: 44.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: 36.2% of Clockticks | Issue: A significant fraction of cycles was stalled due to | the latency of the main memory (DRAM). | | Tips: Improve data accesses or interleave them with compute | using such possible techniques as data layout re-structuring | or software prefetches (through the compiler). | Store Bound: 0.3% of Clockticks Core Bound: 12.6% of Pipeline Slots | This metric represents how much Core non-memory issues were of a | bottleneck. Shortage in hardware compute resources, or dependencies | software's instructions are both categorized under Core Bound. Hence | it may indicate the machine ran out of an OOO resources, certain | execution units are overloaded or dependencies in program's data- or | instruction- flow are limiting the performance (e.g. FP-chained long- | latency arithmetic operations). | Memory Bound: 48.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: 24.9% of Clockticks | A significant proportion of cycles are being spent on data fetches from | caches. Check Memory Access analysis to see if accesses to L2 or L3 | caches are problematic and consider applying the same performance tuning | as you would for a cache-missing workload. This may include reducing the | data working set size, improving data access locality, blocking or | partitioning the working set to fit in the lower cache levels, or | exploiting hardware prefetchers. Consider using software prefetchers, but | note that they can interfere with normal loads, increase latency, and | increase pressure on the memory system. This metric includes coherence | penalties for shared data. Check Microarchitecture Exploration analysis | to see if contested accesses or data sharing are indicated as likely | issues. | DRAM Bound: 45.0% 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. | | The code is latency bound, which means that there are a significant | fraction of cycles during which the code could be stalled due to main | memory latency. Consider optimizing data layout or using software | prefetches through the compiler to improve cache reuse and to reduce the | data fetched from the main memory. | Average DRAM Bandwidth, GB/s: 20.505 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: 17.0% from SP FP 128-bit: 10.3% 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: 6.7% from SP FP Scalar: 83.0% from SP 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. | DP FLOPs: 10.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: 89.9% of uOps FP Arith/Mem Rd Instr. Ratio: 0.367 | The metric value is low. This can be a result of unaligned access to data | for vector operations. Use Intel Advisor to find possible data access | inefficiencies for vector operations. | FP Arith/Mem Wr Instr. Ratio: 0.858 Collection and Platform Info Application Command Line: /opt/intel/oneapi/vtune/2021.7.1/samples/en/C++/matrix/matrix Operating System: 5.11.0-36-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" Computer Name: jay-Legion-T5-28IMB05 Result Size: 3.5 MB Collection start time: 16:17:25 01/10/2021 UTC Collection stop time: 16:17:36 01/10/2021 UTC Collector Type: Event-based counting driver CPU Name: Intel(R) microarchitecture code named Cometlake H/S Frequency: 2.904 GHz Logical CPU Count: 12 Max DRAM Single-Package Bandwidth: 30.000 GB/s Cache Allocation Technology Level 2 capability: not detected Level 3 capability: not detected Recommendations: Hotspots: Start with Hotspots analysis to understand the efficiency of your algorithm. | Use Hotspots analysis to identify the most time consuming functions. | Drill down to see the time spent on every line of code. Memory Access: The Memory Bound metric is high (48.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-jay/self-checker-2021.10.01_12.17.20/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-jay/self-checker-2021.10.01_12.17.20/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 = 0x7f824c2dc010 Offs of buf1 = 0x7f824c2dc180 Addr of buf2 = 0x7f824a2db010 Offs of buf2 = 0x7f824a2db1c0 Addr of buf3 = 0x7f82482da010 Offs of buf3 = 0x7f82482da100 Addr of buf4 = 0x7f82462d9010 Offs of buf4 = 0x7f82462d9140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 10.086 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/result_tpss -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-jay/self-checker-2021.10.01_12.17.20/result_tpss Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-37083-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading 'systemcollector-37083-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading '37083-37088.0.trace' file vtune: Executing actions 25 % Loading '/tmp/vtune-tmp-jay/self-checker-2021.10. 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: Executing actions 41 % Resolving information for `libc.so.6' vtune: Executing actions 43 % Resolving information for `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 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 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-jay/self-checker-2021.10.01_12.17.20/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,74.669944,74.669944,0.0,74.669944,0.0,0.0,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 munmap,0.010000,0.010000,0.010000,0.0,0.0,0.0,0.0,0.0,0.0,libc.so.6,munmap,syscall-template.S,0x11bad0 Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-jay/self-checker-2021.10.01_12.17.20/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 = 0x7f9b26889010 Offs of buf1 = 0x7f9b26889180 Addr of buf2 = 0x7f9b24888010 Offs of buf2 = 0x7f9b248881c0 Addr of buf3 = 0x7f9b22887010 Offs of buf3 = 0x7f9b22887100 Addr of buf4 = 0x7f9b20886010 Offs of buf4 = 0x7f9b20886140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 9.807 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/result_ah -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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 -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/result_ah Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-37183-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading 'systemcollector-37183-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.t vtune: Executing actions 25 % Loading 'sep7f5566d8e700.20211001T121759.668855.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 `hid' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/drivers/hid/hid.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/hid/sections'. This may affect the correctness of symbol resolution for `hid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 39 % Resolving information for `nf_conntrack' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/netfilter/nf_conntrack.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_conntrack/sections'. This may affect the correctness of symbol resolution for `nf_conntrack'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 40 % Resolving information for `nf_conntrack' vtune: Executing actions 41 % Resolving information for `nf_conntrack' vtune: Warning: Cannot locate file `nvidia_uvm.ko'. vtune: Warning: Cannot locate file `nvidia.ko'. vtune: Executing actions 41 % Resolving information for `nvidia' vtune: Executing actions 41 % Resolving information for `nvidia_uvm' vtune: Executing actions 42 % Resolving information for `nvidia_uvm' vtune: Executing actions 43 % Resolving information for `nvidia_uvm' vtune: Executing actions 43 % Resolving information for `kvm' vtune: Warning: Cannot locate file `vmlinux'. vtune: Executing actions 43 % Resolving information for `vmlinux' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/arch/x86/kvm/kvm.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/kvm/sections'. This may affect the correctness of symbol resolution for `kvm'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 44 % Resolving information for `vmlinux' vtune: Warning: Function and source-level analysis for the Linux kernel will not be possible since neither debug version of the kernel nor kernel symbol tables are found. 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 read load addresses of sections from `/sys/module/hid/sections'. This may affect the correctness of symbol resolution for `hid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_conntrack/sections'. This may affect the correctness of symbol resolution for `nf_conntrack'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/kvm/sections'. This may affect the correctness of symbol resolution for `kvm'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Function and source-level analysis for the Linux kernel will not be possible since neither debug version of the kernel nor kernel symbol tables are found. 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-jay/self-checker-2021.10.01_12.17.20/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,69.768788,69.768788,0.001997,69.766791,0.0,0.0,0.0,0.0,0.0,69347700000,11.1,11.1,4.015273,matrix,multiply1,multiply.c,0x401550 [vmlinux],0.373485,0.373485,0.001997,0.371488,0.0,0.0,0.0,0.0,0.0,275500000,9.8,9.8,5.410035,vmlinux,[vmlinux],[Unknown],0x0 [nvidia],0.036949,0.036949,0.0,0.036949,0.0,0.0,0.0,0.0,0.0,31900000,5.6,5.6,4.622240,nvidia,[nvidia],[Unknown],0x0 init_arr,0.002996,0.002996,0.0,0.002996,0.0,0.0,0.0,0.0,0.0,14500000,100.0,100.0,0.824507,matrix,init_arr,matrix.c,0x400d4f __nf_conntrack_find_get,0.000999,0.000999,0.0,0.000999,0.0,0.0,0.0,0.0,0.0,0,0.0,0.0,,nf_conntrack,__nf_conntrack_find_get,[Unknown],0x15e0 Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-jay/self-checker-2021.10.01_12.17.20/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 = 0x7f41ec1da010 Offs of buf1 = 0x7f41ec1da180 Addr of buf2 = 0x7f41ea1d9010 Offs of buf2 = 0x7f41ea1d91c0 Addr of buf3 = 0x7f41e81d8010 Offs of buf3 = 0x7f41e81d8100 Addr of buf4 = 0x7f41e61d7010 Offs of buf4 = 0x7f41e61d7140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 9.204 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/result_ge -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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 -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/result_ge Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-37297-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading 'systemcollector-37297-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.t vtune: Executing actions 25 % Loading 'sep7fb425068700.20211001T121820.891178.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 `r8169' vtune: Executing actions 39 % Resolving information for `uas' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/drivers/net/ethernet/realtek/r8169.ko'. vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/drivers/usb/storage/uas.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/r8169/sections'. This may affect the correctness of symbol resolution for `r8169'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/uas/sections'. This may affect the correctness of symbol resolution for `uas'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 39 % Resolving information for `kvm' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/arch/x86/kvm/kvm.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/kvm/sections'. This may affect the correctness of symbol resolution for `kvm'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 40 % Resolving information for `kvm' vtune: Warning: Cannot locate file `snd_usb_audio.ko'. vtune: Executing actions 40 % Resolving information for `snd_usb_audio' vtune: Executing actions 40 % Resolving information for `hid' vtune: Warning: Cannot locate file `nvidia.ko'. vtune: Executing actions 40 % Resolving information for `nvidia' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/drivers/hid/hid.ko'. vtune: Warning: Cannot locate file `sep5.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/hid/sections'. This may affect the correctness of symbol resolution for `hid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 40 % Resolving information for `sep5' vtune: Executing actions 40 % Resolving information for `ip_tables' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/ipv4/netfilter/ip_tables.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/ip_tables/sections'. This may affect the correctness of symbol resolution for `ip_tables'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot locate file `hid_sony.ko'. vtune: Executing actions 40 % Resolving information for `hid_sony' vtune: Executing actions 41 % Resolving information for `hid_sony' vtune: Executing actions 41 % Resolving information for `usbhid' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/drivers/hid/usbhid/usbhid.ko'. vtune: Executing actions 41 % Resolving information for `nf_nat' vtune: Warning: Cannot read load addresses of sections from `/sys/module/usbhid/sections'. This may affect the correctness of symbol resolution for `usbhid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 42 % Resolving information for `nf_nat' vtune: Executing actions 42 % Resolving information for dangling locations vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/netfilter/nf_nat.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_nat/sections'. This may affect the correctness of symbol resolution for `nf_nat'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 42 % Resolving information for `br_netfilter' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/bridge/br_netfilter.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/br_netfilter/sections'. This may affect the correctness of symbol resolution for `br_netfilter'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 42 % Resolving information for `iptable_filter' vtune: Executing actions 43 % Resolving information for `iptable_filter' vtune: Executing actions 43 % Resolving information for `nf_defrag_ipv4' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/ipv4/netfilter/iptable_filter.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/iptable_filter/sections'. This may affect the correctness of symbol resolution for `iptable_filter'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/ipv4/netfilter/nf_defrag_ipv4.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_defrag_ipv4/sections'. This may affect the correctness of symbol resolution for `nf_defrag_ipv4'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 43 % Resolving information for `ld-2.31.so' vtune: Warning: Cannot locate file `vboxdrv.ko'. vtune: Executing actions 44 % Resolving information for `ld-2.31.so' vtune: Executing actions 44 % Resolving information for `vboxdrv' vtune: Executing actions 44 % Resolving information for `nf_conntrack' vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/ld-2.31.so'. vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/netfilter/nf_conntrack.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_conntrack/sections'. This may affect the correctness of symbol resolution for `nf_conntrack'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot locate file `hid_logitech_hidpp.ko'. vtune: Executing actions 44 % Resolving information for `hid_logitech_hidpp' vtune: Executing actions 45 % Resolving information for `hid_logitech_hidpp' vtune: Warning: Cannot locate file `vmlinux'. vtune: Executing actions 45 % Resolving information for `vmlinux' vtune: Warning: Cannot locate file `nvidia_uvm.ko'. vtune: Executing actions 45 % Resolving information for `nvidia_uvm' vtune: Warning: Function and source-level analysis for the Linux kernel will not be possible since neither debug version of the kernel nor kernel symbol tables are found. 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 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 read load addresses of sections from `/sys/module/r8169/sections'. This may affect the correctness of symbol resolution for `r8169'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/uas/sections'. This may affect the correctness of symbol resolution for `uas'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/kvm/sections'. This may affect the correctness of symbol resolution for `kvm'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/hid/sections'. This may affect the correctness of symbol resolution for `hid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/ip_tables/sections'. This may affect the correctness of symbol resolution for `ip_tables'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/usbhid/sections'. This may affect the correctness of symbol resolution for `usbhid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_nat/sections'. This may affect the correctness of symbol resolution for `nf_nat'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/br_netfilter/sections'. This may affect the correctness of symbol resolution for `br_netfilter'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/iptable_filter/sections'. This may affect the correctness of symbol resolution for `iptable_filter'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_defrag_ipv4/sections'. This may affect the correctness of symbol resolution for `nf_defrag_ipv4'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_conntrack/sections'. This may affect the correctness of symbol resolution for `nf_conntrack'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Function and source-level analysis for the Linux kernel will not be possible since neither debug version of the kernel nor kernel symbol tables are found. 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-jay/self-checker-2021.10.01_12.17.20/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,65.883148,262943000000,69298400000,3.794359,10.9,10.9,24.1,0.0,24.1,0.0,75.9,0.0,0.1,0.0,3.2,3.3,0.0,0.0,0.3,0.3,0.0,0.0,0.1,0.0,0.0,0.0,0.2,0.0,0.0,97.5,0.0,0.2,0.2,0.0,85.6,75.2,5.4,100.0,100.0,64.4,0.0,0.0,0.0,0.1,100.0,0.0,23.9,2.0,4.6,65.7,0.0,49.8,64.7,30.1,0.0,0.7,0.0,0.0,0.2,0.1,0.1,10.5,0.0,11.0,56.7,0.3,0.0,0.0,10.7,7.9,7.6,20.3,30.7,28.8,9.2,12.4,5.6,8.1,8.4,5.3,5.3,0.0,25.0,3991050973.812108,matrix,multiply1,multiply.c,0x401550 [vmlinux],0.379477,1612400000,310300000,5.196262,14.4,9.6,0.0,0.0,0.0,0.0,100.0,4.8,5.2,0.0,59.4,64.7,25.2,10.8,9.7,0.0,0.0,9.7,0.0,0.0,0.0,0.0,7.2,0.0,0.0,26.1,0.0,5.4,0.0,5.4,20.9,17.6,0.0,100.0,100.0,12.2,0.0,0.0,0.0,0.0,0.0,,0.0,,,,0.0,,10.8,39.6,0.0,10.8,0.0,0.0,4.3,0.0,4.3,3.3,0.0,10.8,82.7,3.6,0.0,0.0,25.2,0.0,14.4,9.0,0.0,14.4,21.6,0.0,3.6,7.2,14.4,14.4,14.4,0.0,0.0,4249009186.063158,vmlinux,[vmlinux],[Unknown],0x0 [nvidia],0.039945,113100000,8700000,13.000000,0.0,3.8,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,25.6,100.0,0.0,25.6,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,51.3,0.0,0.0,0.0,0.0,25.6,0.0,25.6,48.7,73.1,100.0,100.0,100.0,10.3,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,51.3,0.0,51.3,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,51.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,2831399106.900000,nvidia,[nvidia],[Unknown],0x0 rtl8169_interrupt,0.010985,34800000,2900000,12.000000,0.0,4.2,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,16.7,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,3167999000.727273,r8169,rtl8169_interrupt,[Unknown],0x1850 init_arr,0.002996,11600000,17400000,0.666667,0.0,75.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,3871998778.666667,matrix,init_arr,matrix.c,0x400bab Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-jay/self-checker-2021.10.01_12.17.20/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 = 0x7f865e626010 Offs of buf1 = 0x7f865e626180 Addr of buf2 = 0x7f865c625010 Offs of buf2 = 0x7f865c6251c0 Addr of buf3 = 0x7f865a624010 Offs of buf3 = 0x7f865a624100 Addr of buf4 = 0x7f8658623010 Offs of buf4 = 0x7f8658623140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 9.704 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-jay/self-checker-2021.10.01_12.17.20/result_ma -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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 -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2021.7.1/bin64/vtune -finalize -r /tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/result_ma Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-37390-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading 'systemcollector-37390-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Loading 'sep7f375e078700.20211001T121844.407108.t vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for dangling locations vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 39 % Resolving information for `usbhid' vtune: Executing actions 39 % Resolving information for `br_netfilter' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/drivers/hid/usbhid/usbhid.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/usbhid/sections'. This may affect the correctness of symbol resolution for `usbhid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/bridge/br_netfilter.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/br_netfilter/sections'. This may affect the correctness of symbol resolution for `br_netfilter'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 39 % Resolving information for `libc-2.31.so' vtune: Executing actions 40 % Resolving information for `libc-2.31.so' vtune: Executing actions 40 % Resolving information for `kvm' vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libc-2.31.so'. vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/arch/x86/kvm/kvm.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/kvm/sections'. This may affect the correctness of symbol resolution for `kvm'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 41 % Resolving information for `kvm' vtune: Executing actions 41 % Resolving information for `r8169' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/drivers/net/ethernet/realtek/r8169.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/r8169/sections'. This may affect the correctness of symbol resolution for `r8169'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot locate file `hid_apple.ko'. vtune: Executing actions 41 % Resolving information for `hid_apple' vtune: Executing actions 42 % Resolving information for `hid_apple' vtune: Warning: Cannot locate file `snd_usb_audio.ko'. vtune: Executing actions 42 % Resolving information for `snd_usb_audio' vtune: Executing actions 42 % Resolving information for `hid' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/drivers/hid/hid.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/hid/sections'. This may affect the correctness of symbol resolution for `hid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 42 % Resolving information for `ip_tables' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/ipv4/netfilter/ip_tables.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/ip_tables/sections'. This may affect the correctness of symbol resolution for `ip_tables'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 43 % Resolving information for `ip_tables' vtune: Warning: Cannot locate file `nvidia.ko'. vtune: Executing actions 43 % Resolving information for `nf_conntrack' vtune: Executing actions 43 % Resolving information for `nvidia' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.11.0-36-generic/kernel/net/netfilter/nf_conntrack.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_conntrack/sections'. This may affect the correctness of symbol resolution for `nf_conntrack'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot locate file `hid_sony.ko'. vtune: Executing actions 43 % Resolving information for `hid_sony' vtune: Warning: Cannot locate file `vboxdrv.ko'. vtune: Executing actions 43 % Resolving information for `vboxdrv' vtune: Executing actions 44 % Resolving information for `vboxdrv' vtune: Warning: Cannot locate file `vmlinux'. vtune: Executing actions 44 % Resolving information for `vmlinux' vtune: Warning: Cannot locate file `sep5.ko'. vtune: Executing actions 44 % Resolving information for `sep5' vtune: Executing actions 45 % Resolving information for `sep5' vtune: Warning: Cannot locate file `nvidia_uvm.ko'. vtune: Executing actions 45 % Resolving information for `nvidia_uvm' vtune: Warning: Function and source-level analysis for the Linux kernel will not be possible since neither debug version of the kernel nor kernel symbol tables are found. 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 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: Cannot read load addresses of sections from `/sys/module/usbhid/sections'. This may affect the correctness of symbol resolution for `usbhid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/br_netfilter/sections'. This may affect the correctness of symbol resolution for `br_netfilter'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/kvm/sections'. This may affect the correctness of symbol resolution for `kvm'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/r8169/sections'. This may affect the correctness of symbol resolution for `r8169'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/hid/sections'. This may affect the correctness of symbol resolution for `hid'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/ip_tables/sections'. This may affect the correctness of symbol resolution for `ip_tables'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Cannot read load addresses of sections from `/sys/module/nf_conntrack/sections'. This may affect the correctness of symbol resolution for `nf_conntrack'. Make sure this directory exists and all files in this directory have read permissions. vtune: Warning: Function and source-level analysis for the Linux kernel will not be possible since neither debug version of the kernel nor kernel symbol tables are found. 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-jay/self-checker-2021.10.01_12.17.20/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,68.971887,74.8,2.6,0.0,24.6,52.6,0.0,15792873772,7900337003,1389797279,137.539743,matrix,multiply1,multiply.c,0x401550 [vmlinux],0.370489,17.5,11.8,1.7,0.0,50.5,0.0,107903237,89702691,1300091,9.526316,vmlinux,[vmlinux],[Unknown],0x0 [nvidia],0.050930,0.0,14.5,0.0,57.8,14.5,14.5,5200156,1300039,0,7.000000,nvidia,[nvidia],[Unknown],0x0 [snd_usb_audio],0.003994,-0.0,0.0,0.0,100.0,0.0,0.0,0,0,0,0.0,snd_usb_audio,[snd_usb_audio],[Unknown],0x0 init_arr,0.002996,0.0,0.0,0.0,0.0,0.0,0.0,1300039,7800234,0,0.0,matrix,init_arr,matrix.c,0x400d4f Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-jay/self-checker-2021.10.01_12.17.20/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 = 0x7fbe2492a010 Offs of buf1 = 0x7fbe2492a180 Addr of buf2 = 0x7fbe22929010 Offs of buf2 = 0x7fbe229291c0 Addr of buf3 = 0x7fbe20928010 Offs of buf3 = 0x7fbe20928100 Addr of buf4 = 0x7fbe1e927010 Offs of buf4 = 0x7fbe1e927140 Threads #: 8 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 9.397 seconds Stderr: vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. 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-jay/self-checker-2021.10.01_12.17.20/result_ah_with_stacks -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. 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-jay/self-checker-2021.10.01_12.17.20/result_ah_with_stacks Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-37498-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading 'systemcollector-37498-jay-Legion-T5-28IM vtune: Executing actions 25 % Loading '37507.perf' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for dangling locations vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 39 % Resolving information for `ld-2.31.so' vtune: Executing actions 39 % Resolving information for `libpthread-2.31.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/ld-2.31.so'. vtune: Executing actions 39 % Resolving information for `libc-2.31.so' vtune: Executing actions 40 % Resolving information for `libc-2.31.so' vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libc-2.31.so'. vtune: Executing actions 41 % Resolving information for `libc-2.31.so' vtune: Executing actions 42 % Resolving information for `libc-2.31.so' vtune: Executing actions 44 % Resolving information for `libc-2.31.so' vtune: Executing actions 45 % Resolving information for `libc-2.31.so' 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 -------------------------------------------------------------------------------- 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-jay/self-checker-2021.10.01_12.17.20/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,66.014964,66.014964,0.000999,66.013966,0.0,0.0,0.0,0.0,0.0,69797200000,12.0,12.0,3.773309,matrix,multiply1,multiply.c,0x401550 [Outside any known module],0.522280,0.522280,0.001997,0.520283,0.0,0.0,0.0,0.0,0.0,414700000,12.2,12.2,5.242352,[Unknown],[Outside any known module],[Unknown],0x0 init_arr,0.000999,0.000999,0.0,0.000999,0.0,0.0,0.0,0.0,0.0,20300000,100.0,100.0,0.197045,matrix,init_arr,matrix.c,0x400bab init_arr,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,8700000,0.0,0.0,0.919542,matrix,init_arr,matrix.c,0x400d4f Stderr: vtune: Using result path `/tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/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-jay/self-checker-2021.10.01_12.17.20/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 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 failed. vtune: Internal Error Cannot find 'runsa.options' by path: /tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/result_th/config/runsa.options HW event-based analysis with context switches Example of analysis types: Threading with HW event-based sampling Collection: Fail 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. 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 check observed a product failure on your system. Review errors in the output above to fix a problem or contact Intel technical support. 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 The following analyses have failed on the system: * Threading with HW event-based sampling * GPU Compute/Media Hotspots (characterization mode) * GPU Compute/Media Hotspots (source analysis mode) Log location: /tmp/vtune-tmp-jay/self-checker-2021.10.01_12.17.20/log.txt