Intel(R) VTune(TM) Profiler Self Check Utility Copyright (C) 2009 Intel Corporation. All rights reserved. Build Number: 624757 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/2023.0.0/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: false LinuxRelease: 5.19.0-28-generic is3DXPPresent: false is3DXP2LMMode: false is3DXPAppDirectMode: false IsNUMANodeWithoutCPUsPresent: false Hypervisor: None PerfmonVersion: 5 isMaxDRAMBandwidthMeasurementSupported: true preferedGpuAdapter: none isEHFIAvailable: true 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.38 isPAXDriverLoaded: true PAXDriverVersion: 1.0 platformType: 151 CPU_NAME: Intel(R) microarchitecture code named Raptorlake-DT PMU: alderlake availablePmuTypes: bigcore,smallcore,cbo,ncu,imc,power referenceFrequency: 3000000000 isPStateAvailable: true isVTSSPPDriverAvailable: true isNMIWatchDogTimerRunning: true LinuxPerfCredentials: Restricted LinuxPerfCapabilities: NotAvailable LinuxPerfStackCapabilities: NotAvailable areKernelPtrsRestricted: no isPerfPCIeMappingAvailable: false isAOCLAvailable: true isTPSSAvailable: true isPytraceAvailable: true forceShowInlines: false isEnergyCollectionSupported: true isSocwatchDriverLoaded: true isCPUSupportedBySocwatch: false isCpuThrottlingAvailable: false isIPMWatchReady: false osCountersCollectorAvailability: dstatNotAvailable l0LoaderStatus: LibNotFound l0DevicesAvailable: false l0VPUDevicesAvailable: false l0GPUDevicesAvailable: false Getting context values: OK ================================================================================ Check driver: isSEPDriverAvailable: true isPAXDriverLoaded: true Command line: lsmod Stdout: sep5 2805760 0 socperf3 610304 1 sep5 Is SEP in lsmod: True Ok ================================================================================ SEP version: Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/sep -version Stdout: Sampling Enabling Product Version: 5.38 Beta built on Dec 6 2022 03:53:32 SEP Driver Version: 5.38 Beta (public) PAX Driver Version: 1.0 Platform type: 151 CPU name: Intel(R) microarchitecture code named Raptorlake-DT PMU: alderlake Driver configs: Non-Maskable Interrupt, REGISTER CHECK ON Copyright(C) 2007-2022 Intel Corporation. All rights reserved. Check driver with sep -version: Ok ================================================================================ HW event-based analysis (counting mode)... Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -collect performance-snapshot -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ps -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fc2415ff010 Offs of buf1 = 0x7fc2415ff180 Addr of buf2 = 0x7fc23f5fe010 Offs of buf2 = 0x7fc23f5fe1c0 Addr of buf3 = 0x7fc23d5fd010 Offs of buf3 = 0x7fc23d5fd100 Addr of buf4 = 0x7fc23b5fc010 Offs of buf4 = 0x7fc23b5fc140 Threads #: 16 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 3.050 seconds Stderr: vtune: Peak bandwidth measurement started. vtune: Peak bandwidth measurement finished. vtune: Warning: EMON Collector Message: Event TOPDOWN.SLOTS:perf_metrics discarded since the event is invalid or the device does not exist. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ps -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ps' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis (counting mode) (Intel driver) Example of analysis types: Performance Snapshot Collection: Ok vtune: Warning: EMON Collector Message: Event TOPDOWN.SLOTS:perf_metrics discarded since the event is invalid or the device does not exist. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -finalize -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ps Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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-436670-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'systemcollector-436670-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'emon.0.bwhist' file vtune: Executing actions 25 % Loading '/tmp/vtune-tmp-hakostra/self-checker-202 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 % 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 65 % 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 73 % Precomputing frequently used data vtune: Executing actions 74 % Precomputing frequently used data vtune: Executing actions 75 % Precomputing frequently used data vtune: Executing actions 76 % Precomputing frequently used data vtune: Executing actions 76 % Updating precomputed scalar metrics vtune: Executing actions 78 % Updating precomputed scalar metrics vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 82 % Discarding redundant overtime data vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 89 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok -------------------------------------------------------------------------------- Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -R summary -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ps Stdout: Elapsed Time: 3.068s IPC: 0.342 | 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. | P-Core: 0.342 | 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. | E-Core: 0.341 | The IPC may be too low. This could be caused by issues such as memory | stalls, instruction starvation, branch misprediction or long latency | instructions. Explore the other hardware-related metrics to identify | what is causing low IPC. | SP GFLOPS: 0.000 DP GFLOPS: 3.472 x87 GFLOPS: 0.000 Average CPU Frequency: 4.925 GHz Logical Core Utilization: 44.0% (14.081 out of 32) | The metric value is low, which may signal a poor logical CPU cores | utilization. Consider improving physical core utilization as the first step | and then look at opportunities to utilize logical cores, which in some cases | can improve processor throughput and overall performance of multi-threaded | applications. | Physical Core Utilization: 45.9% (11.007 out of 24) | The metric value is low, which may signal a poor physical CPU cores | utilization caused by: | - load imbalance | - threading runtime overhead | - contended synchronization | - thread/process underutilization | - incorrect affinity that utilizes logical cores instead of physical | cores | Run the HPC Performance Characterization analysis to estimate the | efficiency of MPI and OpenMP parallelism or run the Locks and Waits | analysis to identify parallel bottlenecks for other parallel runtimes. | Microarchitecture Usage: 2.6% 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. | P-Core Retiring: 0.0% of Pipeline Slots Light Operations: 0.0% of Pipeline Slots FP Arithmetic FP x87: 0.0% of uOps FP Scalar FP Vector 128-bit FP Vector 256-bit FP Vector: 0.0% of uOps Heavy Operations: 0.0% of Pipeline Slots Front-End Bound: 0.0% of Pipeline Slots Front-End Latency: 0.0% of Pipeline Slots Front-End Bandwidth: 0.0% of Pipeline Slots Bad Speculation: 100.0% of Pipeline Slots | A significant proportion of pipeline slots containing useful work are | being cancelled. This can be caused by mispredicting branches or by | machine clears. Note that this metric value may be highlighted due to | Branch Resteers issue. | Branch Mispredict: 0.0% of Pipeline Slots Machine Clears: 100.0% of Pipeline Slots | Issue: A significant portion of execution time is spent handling | machine clears. | | Tips: See the "Memory Disambiguation" section in the Intel 64 and | IA-32 Architectures Optimization Reference Manual. | Back-End Bound: 0.0% of Pipeline Slots Memory Bound: 0.0% of Pipeline Slots L1 Bound: 0.4% of Clockticks L2 Bound: 0.1% of Clockticks L3 Bound: 23.6% of Clockticks DRAM Bound: 55.9% of Clockticks Memory Bandwidth: 98.6% of Clockticks Memory Latency: 1.4% of Clockticks Core Bound: 0.0% of Pipeline Slots E-Core Retiring: 7.1% of Pipeline Slots Front-End Bound: 15.8% of Pipeline Slots Bad Speculation: 13.3% of Pipeline Slots Back-End Bound: 63.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). | Resource Bound: 63.7% of Pipeline Slots | Resource Bound | Alternative Back-End Bound: 63.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). | Core Bound: 3.2% Memory Bound: 60.5% | 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. | L2 Bound: 18.5% | This metric shows how often machine was stalled on L2 cache. | Avoiding cache misses (L1 misses/L2 hits) will improve the | latency and increase performance. | L3 Bound: 17.1% | 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. | DRAM Bound: 24.9% | This metric shows how often CPU was stalled on the main | memory (DRAM). Caching typically improves the latency and | increases performance. | Memory Bound: 0.0% of Pipeline Slots P-Core Memory Bound: 0.0% of Pipeline Slots Cache Bound: 24.0% 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: 55.9% of Clockticks E-Core Memory Bound: 60.5% | 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: 35.6% 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: 24.9% | This metric shows how often CPU was stalled on the main memory | (DRAM). Caching typically improves the latency and increases | performance. | Vectorization: 0.0% 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.0% of uOps Packed: 78.2% from SP FP 128-bit: 78.2% from SP FP | Using the latest vector instruction set can improve | parallelism for this code. Consider either recompiling the | code with the latest instruction set or using Intel Advisor | to get vectorization help. | 256-bit: 0.0% from SP FP Scalar: 21.8% from SP FP DP FLOPs: 24.4% 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: 75.6% of uOps Collection and Platform Info Application Command Line: /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/matrix Operating System: 5.19.0-28-generic DISTRIB_ID=LinuxMint DISTRIB_RELEASE=21.1 DISTRIB_CODENAME=vera DISTRIB_DESCRIPTION="Linux Mint 21.1 Vera" Computer Name: kmt-trd2 Result Size: 3,9 MB Collection start time: 14:51:46 06/02/2023 UTC Collection stop time: 14:51:49 06/02/2023 UTC Collector Type: Event-based counting driver CPU Name: Intel(R) microarchitecture code named Raptorlake-DT Frequency: 2.995 GHz Logical CPU Count: 32 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. HPC Performance Characterization: Vectorization (0.0%) 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. Microarchitecture Exploration: There is low microarchitecture usage (2.6%) of available hardware resources. | Run Microarchitecture Exploration analysis to analyze CPU | microarchitecture bottlenecks that can affect application performance. Threading: There is poor utilization of logical CPU cores (44.0%) in your application. | Use Threading to explore more opportunities to increase parallelism in | your application. 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-hakostra/self-checker-2023.02.06_15.51.41/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/2023.0.0/bin64/vtune -collect hotspots -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_tpss -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fd8747e1010 Offs of buf1 = 0x7fd8747e1180 Addr of buf2 = 0x7fd8727e0010 Offs of buf2 = 0x7fd8727e01c0 Addr of buf3 = 0x7fd8707df010 Offs of buf3 = 0x7fd8707df100 Addr of buf4 = 0x7fd86e7de010 Offs of buf4 = 0x7fd86e7de140 Threads #: 16 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 3.027 seconds Stderr: vtune: Warning: EMON Collector Message: Event TOPDOWN.SLOTS:perf_metrics discarded since the event is invalid or the device does not exist. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_tpss -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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 vtune: Warning: EMON Collector Message: Event TOPDOWN.SLOTS:perf_metrics discarded since the event is invalid or the device does not exist. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -finalize -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_tpss Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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-436831-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'systemcollector-436831-kmt-trd2.sc' file vtune: Executing actions 25 % Loading '436831-436838.0.trace' file vtune: Executing actions 25 % Loading 'emon.0.bwhist' file vtune: Executing actions 25 % Loading '/tmp/vtune-tmp-hakostra/self-checker-202 vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 39 % Resolving information for `libc.so.6' vtune: Executing actions 41 % Resolving information for `libc.so.6' vtune: Executing actions 44 % Resolving information for `libc.so.6' vtune: Executing actions 44 % Resolving bottom user stack information vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving thread name information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 48 % Resolving call target names for dynamic code vtune: Executing actions 49 % Resolving call target names for dynamic code vtune: Executing actions 49 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 62 % Processing profile metrics and debug information vtune: Executing actions 63 % Processing profile metrics and debug information vtune: Executing actions 63 % Setting data model parameters vtune: Executing actions 64 % Setting data model parameters vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 67 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 74 % Precomputing frequently used data vtune: Executing actions 76 % Precomputing frequently used data vtune: Executing actions 76 % Updating precomputed scalar metrics vtune: Executing actions 78 % Updating precomputed scalar metrics vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 82 % Discarding redundant overtime data vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 89 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok -------------------------------------------------------------------------------- Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_tpss Stdout: Function,CPU Time,CPU Time:Effective Time,CPU Time:Spin Time,CPU Time:Overhead Time,Module,Function (Full),Source File,Start Address multiply1,41.019282,41.019282,0.0,0.0,matrix,multiply1,multiply.c,0x401550 Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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/2023.0.0/bin64/vtune -collect hotspots -knob sampling-mode=hw -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fbd561ff010 Offs of buf1 = 0x7fbd561ff180 Addr of buf2 = 0x7fbd541fe010 Offs of buf2 = 0x7fbd541fe1c0 Addr of buf3 = 0x7fbd521fd010 Offs of buf3 = 0x7fbd521fd100 Addr of buf4 = 0x7fbd501fc010 Offs of buf4 = 0x7fbd501fc140 Threads #: 16 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 2.678 seconds Stderr: vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis check (Intel driver) Example of analysis types: Hotspots with HW event-based sampling, HPC Performance Characterization, etc. Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -finalize -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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-436980-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'systemcollector-436980-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.t vtune: Executing actions 25 % Loading 'sep7fe0363fe640.20230206T155158.779416.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 `libgcc_s.so.1' vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libgcc_s.so.1'. vtune: Executing actions 39 % Resolving information for `libc.so.6' vtune: Executing actions 40 % Resolving information for `libc.so.6' vtune: Executing actions 40 % Resolving information for `ld-linux-x86-64.so.2' vtune: Executing actions 40 % Resolving information for `nf_conntrack' vtune: Executing actions 40 % Resolving information for `i40e' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.19.0-28-generic/kernel/net/netfilter/nf_conntrack.ko'. vtune: Executing actions 40 % Resolving information for `kvm' 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 debugging information for file `/lib/modules/5.19.0-28-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/i40e/sections'. This may affect the correctness of symbol resolution for `i40e'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 41 % Resolving information for `kvm' vtune: Warning: Cannot locate file `sep5.ko'. vtune: Executing actions 41 % Resolving information for `sep5' vtune: Executing actions 42 % Resolving information for `sep5' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.19.0-28-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 43 % Resolving information for `sep5' vtune: Executing actions 43 % Resolving information for `amdgpu' vtune: Warning: Cannot locate file `vmlinux'. vtune: Executing actions 43 % 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 44 % Resolving information for `vmlinux' vtune: Executing actions 45 % Resolving information for `vmlinux' vtune: Warning: Cannot locate debugging information for file `/lib/modules/5.19.0-28-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko'. vtune: Warning: Cannot read load addresses of sections from `/sys/module/amdgpu/sections'. This may affect the correctness of symbol resolution for `amdgpu'. Make sure this directory exists and all files in this directory have read permissions. vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 48 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 60 % Setting data model parameters vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 62 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 65 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 67 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 72 % Updating precomputed scalar metrics vtune: Executing actions 75 % Updating precomputed scalar metrics vtune: Executing actions 75 % Discarding redundant overtime data vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 78 % Saving the result vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: Cannot 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/i40e/sections'. This may affect the correctness of symbol resolution for `i40e'. 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. vtune: Warning: Cannot read load addresses of sections from `/sys/module/amdgpu/sections'. This may affect the correctness of symbol resolution for `amdgpu'. Make sure this directory exists and all files in this directory have read permissions. -------------------------------------------------------------------------------- Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah Stdout: Function,CPU Time,CPU Time:Effective Time,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,35.091148,35.091148,0.0,0.0,68775000000,7.1,7.1,2.516074,matrix,multiply1,multiply.c,0x401550 [vmlinux],0.212340,0.212340,0.0,0.0,408000000,18.3,18.3,2.294118,vmlinux,[vmlinux],[Unknown],0x0 [sep5],0.044071,0.044071,0.0,0.0,222000000,56.4,56.4,0.770270,sep5,[sep5],[Unknown],0x0 init_arr,0.005008,0.005008,0.0,0.0,9000000,5.6,5.6,0.666667,matrix,init_arr,matrix.c,0x400bab init_arr,0.001002,0.001002,0.0,0.0,21000000,0.0,0.0,0.714286,matrix,init_arr,matrix.c,0x400d4f Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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/2023.0.0/bin64/vtune -collect uarch-exploration -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ge -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f3c69dff010 Offs of buf1 = 0x7f3c69dff180 Addr of buf2 = 0x7f3c67dfe010 Offs of buf2 = 0x7f3c67dfe1c0 Addr of buf3 = 0x7f3c65dfd010 Offs of buf3 = 0x7f3c65dfd100 Addr of buf4 = 0x7f3c63dfc010 Offs of buf4 = 0x7f3c63dfc140 Threads #: 16 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 2.196 seconds Stderr: vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ge -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ge' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis check (Intel driver) Example of analysis types: Microarchitecture Exploration Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -finalize -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ge Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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-437129-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'systemcollector-437129-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Loading 'sep7f52eddfe640.20230206T155208.319264.t vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 39 % Resolving information for `ld-linux-x86-64.so.2' vtune: Executing actions 40 % Resolving information for `ld-linux-x86-64.so.2' vtune: Executing actions 42 % Resolving information for `ld-linux-x86-64.so.2' vtune: Warning: Cannot locate file `sep5.ko'. vtune: Executing actions 42 % Resolving information for `sep5' vtune: Executing actions 43 % Resolving information for `sep5' vtune: Warning: Cannot locate file `vmlinux'. vtune: Executing actions 43 % 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 46 % Resolving thread name information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 48 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 60 % Setting data model parameters vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 62 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 67 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 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: 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/2023.0.0/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ge Stdout: Function,CPU Time,Clockticks,Clockticks:P-Core,Clockticks:E-Core,Instructions Retired,Instructions Retired:P-Core,Instructions Retired:E-Core,CPI Rate,CPI Rate:P-Core,CPI Rate:E-Core,P-Core:Retiring(%),P-Core:Retiring:Light Operations(%),P-Core:Retiring:Light Operations:FP Arithmetic(%),P-Core:Retiring:Light Operations:FP Arithmetic:FP x87(%),P-Core:Retiring:Light Operations:FP Arithmetic:FP Scalar(%),P-Core:Retiring:Light Operations:FP Arithmetic:FP Vector(%),P-Core:Retiring:Light Operations:FP Arithmetic:FP Vector:128-bit FP Vector(%),P-Core:Retiring:Light Operations:FP Arithmetic:FP Vector:256-bit FP Vector(%),P-Core:Retiring:Light Operations:Integer Operations(%),P-Core:Retiring:Light Operations:Integer Operations:128-bit Integer Vector Operations(%),P-Core:Retiring:Light Operations:Integer Operations:256-bit Vector Operations(%),P-Core:Retiring:Light Operations:Integer Operations:Shuffles(%),P-Core:Retiring:Light Operations:Memory Operations(%),P-Core:Retiring:Light Operations:Fused Instructions(%),P-Core:Retiring:Light Operations:Non Fused Branches(%),P-Core:Retiring:Light Operations:Nop Instructions(%),P-Core:Retiring:Light Operations:Other(%),P-Core:Retiring:Heavy Operations(%),P-Core:Retiring:Heavy Operations:Few Uops Instructions(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer:Assists(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer:Assists:Page Faults(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer:Assists:FP Assists(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer:Assists:AVX Assists(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer:CISC(%),P-Core:Front-End Bound(%),P-Core:Front-End Bound:Front-End Latency(%),P-Core:Front-End Bound:Front-End Latency:ICache Misses(%),P-Core:Front-End Bound:Front-End Latency:ITLB Overhead(%),P-Core:Front-End Bound:Front-End Latency:Branch Resteers(%),P-Core:Front-End Bound:Front-End Latency:Branch Resteers:Mispredicts Resteers(%),P-Core:Front-End Bound:Front-End Latency:Branch Resteers:Clears Resteers(%),P-Core:Front-End Bound:Front-End Latency:Branch Resteers:Unknown Branches(%),P-Core:Front-End Bound:Front-End Latency:DSB Switches(%),P-Core:Front-End Bound:Front-End Latency:Length Changing Prefixes(%),P-Core:Front-End Bound:Front-End Latency:MS Switches(%),P-Core:Front-End Bound:Front-End Bandwidth(%),P-Core:Front-End Bound:Front-End Bandwidth:Front-End Bandwidth MITE(%),P-Core:Front-End Bound:Front-End Bandwidth:Front-End Bandwidth MITE:Decoder-0 Alone(%),P-Core:Front-End Bound:Front-End Bandwidth:Front-End Bandwidth DSB(%),P-Core:Front-End Bound:Front-End Bandwidth:Front-End Bandwidth LSD(%),P-Core:Front-End Bound:Front-End Bandwidth:(Info) DSB Coverage(%),P-Core:Front-End Bound:Front-End Bandwidth:(Info) LSD Coverage(%),P-Core:Front-End Bound:Front-End Bandwidth:(Info) DSB Misses(%),P-Core:Bad Speculation(%),P-Core:Bad Speculation:Branch Mispredict(%),P-Core:Bad Speculation:Machine Clears(%),P-Core:Back-End Bound(%),P-Core:Back-End Bound:Memory Bound(%),P-Core:Back-End Bound:Memory Bound:L1 Bound(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead:Load STLB Hit(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead:Load STLB Miss(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:Loads Blocked by Store Forwarding(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:Lock Latency(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:Split Loads(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:FB Full(%),P-Core:Back-End Bound:Memory Bound:L2 Bound(%),P-Core:Back-End Bound:Memory Bound:L3 Bound(%),P-Core:Back-End Bound:Memory Bound:L3 Bound:Contested Accesses(%),P-Core:Back-End Bound:Memory Bound:L3 Bound:Data Sharing(%),P-Core:Back-End Bound:Memory Bound:L3 Bound:L3 Latency(%),P-Core:Back-End Bound:Memory Bound:L3 Bound:SQ Full(%),P-Core:Back-End Bound:Memory Bound:DRAM Bound(%),P-Core:Back-End Bound:Memory Bound:DRAM Bound:Memory Bandwidth(%),P-Core:Back-End Bound:Memory Bound:DRAM Bound:Memory Latency(%),P-Core:Back-End Bound:Memory Bound:Store Bound(%),P-Core:Back-End Bound:Memory Bound:Store Bound:Store Latency(%),P-Core:Back-End Bound:Memory Bound:Store Bound:False Sharing(%),P-Core:Back-End Bound:Memory Bound:Store Bound:Split Stores(%),P-Core:Back-End Bound:Memory Bound:Store Bound:Streaming Stores(%),P-Core:Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead(%),P-Core:Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead:Store STLB Hit(%),P-Core:Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead:Store STLB Hit(%),P-Core:Back-End Bound:Core Bound(%),P-Core:Back-End Bound:Core Bound:Divider(%),P-Core:Back-End Bound:Core Bound:Port Utilization(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Serializing Operations(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Serializing Operations:Slow Pause(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Serializing Operations:Memory Fence(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Mixing Vectors(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 1 Port Utilized(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 2 Ports Utilized(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 0(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 1(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 6(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Load Operation Utilization(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Store Operation Utilization(%),E-Core:Retiring(%),E-Core:Retiring:General Retirement(%),E-Core:Retiring:General Retirement:FP Arithmetic(%),E-Core:Retiring:General Retirement:Other(%),E-Core:Retiring:Microcode Sequencer(%),E-Core:Front-End Bound(%),E-Core:Front-End Bound:Front-End Latency(%),E-Core:Front-End Bound:Front-End Latency:ICache Misses(%),E-Core:Front-End Bound:Front-End Latency:ITLB Overhead(%),E-Core:Front-End Bound:Front-End Latency:BACLEARS(%),E-Core:Front-End Bound:Front-End Latency:Branch Resteers(%),E-Core:Front-End Bound:Front-End Bandwidth(%),E-Core:Front-End Bound:Front-End Bandwidth:Cisc(%),E-Core:Front-End Bound:Front-End Bandwidth:Decode(%),E-Core:Front-End Bound:Front-End Bandwidth:Pre-Decode Wrong(%),E-Core:Front-End Bound:Front-End Bandwidth:Front-End Other(%),E-Core:Bad Speculation(%),E-Core:Bad Speculation:Branch Mispredict(%),E-Core:Bad Speculation:Machine Clears(%),E-Core:Bad Speculation:Machine Clears:Machine Clear(%),E-Core:Bad Speculation:Machine Clears:MO Machine Clear Overhead(%),E-Core:Back-End Bound(%),E-Core:Back-End Bound:Resource Bound(%),E-Core:Back-End Bound:Resource Bound:Memory Scheduler(%),E-Core:Back-End Bound:Resource Bound:Non-memory Scheduler(%),E-Core:Back-End Bound:Resource Bound:Register(%),E-Core:Back-End Bound:Resource Bound:Full Re-order Buffer (ROB)(%),E-Core:Back-End Bound:Resource Bound:Allocation Restriction(%),E-Core:Back-End Bound:Resource Bound:Serializing Operations(%),E-Core:Alternative Back-End Bound(%),E-Core:Alternative Back-End Bound:Core Bound(%),E-Core:Alternative Back-End Bound:Memory Bound(%),E-Core:Alternative Back-End Bound:Memory Bound:L2 Bound(%),E-Core:Alternative Back-End Bound:Memory Bound:L3 Bound(%),E-Core:Alternative Back-End Bound:Memory Bound:DRAM Bound(%),Average CPU Frequency,Module,Function (Full),Source File,Start Address multiply1,27.931693,138387000000,84897000000,53490000000,68757000000,44670000000,24087000000,2.012697,1.900537,2.220700,8.8,8.8,25.1,0.0,25.1,0.0,0.0,0.0,0.0,0.0,0.0,0.0,3.2,0.0,1.1,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.2,0.0,0.0,0.2,0.2,26.5,73.5,2.2,0.5,0.0,0.5,90.4,70.4,0.0,0.0,0.0,34.0,0.0,0.0,0.0,72.5,0.0,53.9,0.0,9.9,100.0,0.1,18.1,93.9,5.8,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,20.0,0.0,13.7,0.0,0.0,0.0,0.0,0.0,13.7,4.1,10.3,20.9,46.7,32.2,13.5,4.4,3.2,9.1,9.1,0.0,9.1,0.0,10.1,0.0,0.0,0.0,0.0,0.0,11.8,0.0,10.1,0.0,1.7,9.5,0.2,10.9,0.0,10.9,71.0,71.0,26.1,0.0,0.0,43.5,0.0,0.0,71.0,1.8,69.2,15.7,39.6,13.9,4954479533.254849,matrix,multiply1,multiply.c,0x401550 [vmlinux],0.170272,876000000,642000000,234000000,390000000,237000000,153000000,2.246154,2.708861,1.529412,5.3,4.3,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.9,0.0,0.9,0.0,2.6,1.1,1.1,0.0,0.0,0.0,0.0,0.0,0.0,19.2,6.4,0.0,0.0,1.5,0.0,1.5,0.0,0.0,0.0,0.9,12.8,0.0,0.0,4.2,0.0,50.0,0.0,0.0,22.1,0.0,22.1,53.4,5.3,0.0,5.3,0.0,5.3,0.0,0.0,0.0,0.0,5.9,11.8,0.0,0.0,0.0,0.0,8.9,11.8,8.9,0.0,17.8,0.0,0.0,0.0,2.1,0.0,2.1,48.0,0.0,0.0,37.5,55.0,0.0,0.0,0.0,0.0,0.0,11.8,6.7,0.0,16.7,8.3,5.6,4.2,30.3,28.2,0.0,28.2,2.1,39.5,4.6,4.1,0.0,0.0,0.5,15.4,12.8,1.0,0.0,1.5,3.1,2.1,1.5,0.0,1.5,63.1,63.1,2.1,1.5,0.0,11.8,1.5,54.4,63.1,28.2,34.9,11.8,13.3,9.7,5144696096.141176,vmlinux,[vmlinux],[Unknown],0x0 [sep5],0.039063,138000000,66000000,72000000,156000000,81000000,75000000,0.884615,0.814815,0.960000,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,20.7,0.0,0.0,0.0,0.0,0.0,0.0,0.0,5.8,0.0,0.0,20.7,0.0,0.0,0.0,0.0,80.0,0.0,0.0,44.7,0.0,44.7,34.5,0.0,100.0,2.9,0.0,2.9,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,28.8,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,34.5,0.0,0.0,0.0,69.1,0.0,0.0,0.0,0.0,57.6,0.0,0.0,0.0,0.0,0.0,,,36.7,36.7,0.0,36.7,0.0,31.7,0.0,0.0,0.0,0.0,0.0,16.7,10.0,5.0,0.0,1.7,0.0,0.0,0.0,0.0,0.0,46.7,46.7,11.7,1.7,0.0,0.0,0.0,41.7,46.7,28.3,18.3,1.7,16.7,0.0,3532799742.871795,sep5,[sep5],[Unknown],0x0 init_arr,0.004006,9000000,9000000,0,18000000,18000000,0,0.500000,0.500000,0.0,0.0,0.0,,0.0,0.0,,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,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,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,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,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,2246399836.500000,matrix,init_arr,matrix.c,0x400bab init_arr,0.002003,3000000,3000000,0,21000000,21000000,0,0.142857,0.142857,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,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,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,0.0,0.0,0.0,0.0,0.0,100.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,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,1497599891.000000,matrix,init_arr,matrix.c,0x400d4f Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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/2023.0.0/bin64/vtune -collect memory-access -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ma -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f9b785ff010 Offs of buf1 = 0x7f9b785ff180 Addr of buf2 = 0x7f9b765fe010 Offs of buf2 = 0x7f9b765fe1c0 Addr of buf3 = 0x7f9b745fd010 Offs of buf3 = 0x7f9b745fd100 Addr of buf4 = 0x7f9b725fc010 Offs of buf4 = 0x7f9b725fc140 Threads #: 16 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 1.822 seconds Stderr: vtune: Peak bandwidth measurement started. vtune: Peak bandwidth measurement finished. vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ma -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ma' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with uncore events (Intel driver) Example of analysis types: Memory Access Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -finalize -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ma Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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-437325-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'systemcollector-437325-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.t vtune: Executing actions 25 % Loading 'sep7f9d959fe640.20230206T155222.029007.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 40 % Resolving information for `matrix' vtune: Executing actions 40 % Resolving information for `libc.so.6' vtune: Executing actions 41 % Resolving information for `libc.so.6' vtune: Warning: Cannot locate file `sep5.ko'. vtune: Executing actions 41 % Resolving information for `sep5' vtune: Executing actions 42 % Resolving information for `sep5' vtune: Warning: Cannot locate file `vmlinux'. vtune: Executing actions 42 % 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 44 % Resolving information for `vmlinux' vtune: Executing actions 45 % Resolving information for `vmlinux' vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving bottom user stack information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 48 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 54 % Processing profile metrics and debug information vtune: Executing actions 55 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 62 % Processing profile metrics and debug information vtune: Executing actions 63 % Processing profile metrics and debug information vtune: Executing actions 63 % Preparing output tree vtune: Executing actions 63 % Parsing columns in input tree vtune: Executing actions 64 % Parsing columns in input tree vtune: Executing actions 64 % Creating top-level columns vtune: Executing actions 65 % Creating top-level columns vtune: Executing actions 65 % Creating top-level rows vtune: Executing actions 67 % Creating top-level rows vtune: Executing actions 67 % Setting data model parameters vtune: Executing actions 68 % Setting data model parameters vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 73 % Precomputing frequently used data vtune: Executing actions 74 % Precomputing frequently used data vtune: Executing actions 75 % Precomputing frequently used data vtune: Executing actions 76 % Precomputing frequently used data vtune: Executing actions 77 % Precomputing frequently used data vtune: Executing actions 78 % Precomputing frequently used data vtune: Executing actions 79 % Precomputing frequently used data vtune: Executing actions 79 % Updating precomputed scalar metrics vtune: Executing actions 82 % Updating precomputed scalar metrics vtune: Executing actions 82 % Discarding redundant overtime data vtune: Executing actions 85 % Discarding redundant overtime data vtune: Executing actions 85 % Saving the result vtune: Executing actions 89 % Saving the result vtune: Executing actions 92 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: 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/2023.0.0/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ma Stdout: Function,CPU Time,P-Core:Memory Bound(%),P-Core:Memory Bound:L1 Bound(%),P-Core:Memory Bound:L2 Bound(%),P-Core:Memory Bound:L3 Bound(%),P-Core:Memory Bound:DRAM Bound(%),P-Core:Memory Bound:Store Bound(%),E-Core:Memory Bound(%),E-Core:Memory Bound:L2 Bound(%),E-Core:Memory Bound:L3 Bound(%),E-Core:Memory Bound:DRAM Bound(%),Loads,Stores,LLC Miss Count,Average Latency (cycles),Module,Function (Full),Source File,Start Address multiply1,22.635218,62.1,0.0,0.2,56.5,7.8,0.0,76.6,16.2,57.5,2.8,17291918742,8635159047,37811664,34.071558,matrix,multiply1,multiply.c,0x401550 [vmlinux],0.176282,30.4,11.8,0.0,8.4,8.4,0.0,21.7,8.9,10.0,2.8,143804314,51001530,0,5.579370,vmlinux,[vmlinux],[Unknown],0x0 [sep5],0.048077,100.0,27.8,0.0,27.8,0.0,0.0,7.4,2.2,5.2,0.0,72902187,82202466,0,2.800403,sep5,[sep5],[Unknown],0x0 init_arr,0.002003,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0,0,0.0,matrix,init_arr,matrix.c,0x400d4f init_arr,0.002003,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0,0,0,0.0,matrix,init_arr,matrix.c,0x400bab Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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/2023.0.0/bin64/vtune -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fd484fff010 Offs of buf1 = 0x7fd484fff180 Addr of buf2 = 0x7fd482ffe010 Offs of buf2 = 0x7fd482ffe1c0 Addr of buf3 = 0x7fd480ffd010 Offs of buf3 = 0x7fd480ffd100 Addr of buf4 = 0x7fd47effc010 Offs of buf4 = 0x7fd47effc140 Threads #: 16 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 1.843 seconds Stderr: vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah_with_stacks -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah_with_stacks' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with stacks (Intel driver) Example of analysis types: Hotspots with HW event-based sampling and call stacks Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -finalize -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah_with_stacks Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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-437506-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'systemcollector-437506-kmt-trd2.sc' file vtune: Executing actions 25 % Loading '437506-437512.0.vtss' file vtune: Executing actions 25 % Loading '437506-437512.1.vtss' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 39 % Resolving information for `libc.so.6' vtune: Executing actions 39 % Resolving information for `ld-linux-x86-64.so.2' vtune: Executing actions 40 % Resolving information for `ld-linux-x86-64.so.2' vtune: Executing actions 41 % Resolving information for `ld-linux-x86-64.so.2' vtune: Warning: Cannot locate file `vtsspp.ko'. vtune: Warning: Cannot locate file `vmlinux'. vtune: Executing actions 41 % Resolving information for `vtsspp' vtune: Executing actions 41 % Resolving information for `vmlinux' vtune: Executing actions 42 % 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 44 % Resolving information for `vmlinux' 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 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 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok 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/2023.0.0/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_ah_with_stacks Stdout: Function,CPU Time,CPU Time:Effective Time,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,22.775457,22.775457,0.0,0.0,68452308071,11.0,11.0,1.661577,matrix,multiply1,multiply.c,0x401550 [vmlinux],0.115268,0.115268,0.0,0.0,382618218,12.9,12.9,1.660262,vmlinux,[vmlinux],[Unknown],0x0 __libc_start_main_impl,0.006016,0.006016,0.0,0.0,34738534,48.4,48.4,0.844798,libc.so.6,__libc_start_main_impl,libc-start.c,0x29dc0 __GI_,0.003007,0.003007,0.0,0.0,20882834,50.4,50.4,0.591261,libc.so.6,"__GI_(long, int, bool, char)",malloc.c,0xa5460 init_arr,0.001003,0.001003,0.0,0.0,6465463,47.8,47.8,0.851322,matrix,init_arr,matrix.c,0x400bab Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/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/2023.0.0/bin64/vtune -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_th -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2023.0.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f32c17ff010 Offs of buf1 = 0x7f32c17ff180 Addr of buf2 = 0x7f32bf7fe010 Offs of buf2 = 0x7f32bf7fe1c0 Addr of buf3 = 0x7f32bd7fd010 Offs of buf3 = 0x7f32bd7fd100 Addr of buf4 = 0x7f32bb7fc010 Offs of buf4 = 0x7f32bb7fc140 Threads #: 16 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 1.858 seconds Stderr: vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_th -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_th' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done HW event-based analysis with context switches (Intel driver) Example of analysis types: Threading with HW event-based sampling Collection: Ok vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/vtune -finalize -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_th Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_th' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-437614-kmt-trd2.sc' file vtune: Executing actions 25 % Loading 'systemcollector-437614-kmt-trd2.sc' file vtune: Executing actions 25 % Loading '437614-437620.0.vtss' file vtune: Executing actions 25 % Loading '437614-437620.1.vtss' file vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for `matrix' vtune: Executing actions 39 % Resolving information for `ld-linux-x86-64.so.2' vtune: Executing actions 39 % Resolving information for `libc.so.6' vtune: Executing actions 40 % Resolving information for `libc.so.6' vtune: Executing actions 41 % Resolving information for `libc.so.6' vtune: Warning: Cannot locate file `vtsspp.ko'. vtune: Executing actions 41 % Resolving information for `vtsspp' vtune: Warning: Cannot locate file `vmlinux'. vtune: Executing actions 41 % Resolving information for `vmlinux' vtune: Executing actions 42 % Resolving information for `vmlinux' 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 62 % Processing profile metrics and debug information vtune: Executing actions 63 % Processing profile metrics and debug information vtune: Executing actions 63 % Setting data model parameters vtune: Executing actions 64 % Setting data model parameters vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 67 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 73 % Precomputing frequently used data vtune: Executing actions 74 % Precomputing frequently used data vtune: Executing actions 76 % Precomputing frequently used data vtune: Executing actions 76 % Updating precomputed scalar metrics vtune: Executing actions 78 % Updating precomputed scalar metrics vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 82 % Discarding redundant overtime data vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 89 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: 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/2023.0.0/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_th Stdout: Function,CPU Time,CPU Time:Effective Time,CPU Time:Spin Time,CPU Time:Overhead Time,Inactive Wait Time,Inactive Wait Time:Inactive Sync Wait Time,Inactive Wait Time:Inactive Sync Wait Time:Idle,Inactive Wait Time:Inactive Sync Wait Time:Poor,Inactive Wait Time:Inactive Sync Wait Time:Ok,Inactive Wait Time:Inactive Sync Wait Time:Ideal,Inactive Wait Time:Inactive Sync Wait Time:Over,Inactive Wait Time:Preemption Wait Time,Inactive Wait Time:Preemption Wait Time:Idle,Inactive Wait Time:Preemption Wait Time:Poor,Inactive Wait Time:Preemption Wait Time:Ok,Inactive Wait Time:Preemption Wait Time:Ideal,Inactive Wait Time:Preemption Wait Time:Over,Inactive Wait Count,Inactive Wait Count:Inactive Sync Wait Count,Inactive Wait Count:Inactive Sync Wait Count:Idle,Inactive Wait Count:Inactive Sync Wait Count:Poor,Inactive Wait Count:Inactive Sync Wait Count:Ok,Inactive Wait Count:Inactive Sync Wait Count:Ideal,Inactive Wait Count:Inactive Sync Wait Count:Over,Inactive Wait Count:Preemption Wait Count,Inactive Wait Count:Preemption Wait Count:Idle,Inactive Wait Count:Preemption Wait Count:Poor,Inactive Wait Count:Preemption Wait Count:Ok,Inactive Wait Count:Preemption Wait Count:Ideal,Inactive Wait Count:Preemption Wait Count:Over,Module,Function (Full),Source File,Start Address multiply1,23.457918,23.457918,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,matrix,multiply1,multiply.c,0x401550 [vmlinux],0.146338,0.146338,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,vmlinux,[vmlinux],[Unknown],0x0 init_arr,0.002006,0.002006,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,matrix,init_arr,matrix.c,0x400bab [vtsspp],0.002004,0.002004,0.0,0.0,0.623940,0.618008,0.000590,0.617418,0.0,0.0,0.0,0.005932,0.0,0.005932,0.0,0.0,0.0,88,6,0,6,0,0,0,82,0,82,0,0,0,vtsspp,[vtsspp],[Unknown],0x0 init_arr,0.001003,0.001003,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,matrix,init_arr,matrix.c,0x400d4f Stderr: vtune: Using result path `/tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/result_th' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok Getting available devices: Command line: sycl-ls Stdout: [opencl:acc:0] Intel(R) FPGA Emulation Platform for OpenCL(TM), Intel(R) FPGA Emulation Device 1.2 [2022.15.12.0.01_081451] [opencl:cpu:1] Intel(R) OpenCL, 13th Gen Intel(R) Core(TM) i9-13900K 3.0 [2022.15.12.0.01_081451] Checking DPC++ application as prerequisite for GPU analyses... Setting envirnoment variable: SYCL_DEVICE_FILTER=opencl:gpu Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stderr: /opt/intel/oneapi/vtune/2023.0.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libsycl.so.5: cannot open shared object file: No such file or directory Setting envirnoment variable: SYCL_DEVICE_FILTER=level_zero:gpu Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stderr: /opt/intel/oneapi/vtune/2023.0.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libsycl.so.5: cannot open shared object file: No such file or directory Setting envirnoment variable: ZES_ENABLE_SYSMAN=1 Command line: /opt/intel/oneapi/vtune/2023.0.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stderr: /opt/intel/oneapi/vtune/2023.0.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libsycl.so.5: cannot open shared object file: No such file or directory Checking DPC++ application as prerequisite for GPU analyses: Fail Unable to run DPC++ application on GPU connected to this system. If you are using an Intel GPU and want to verify profiling support for DPC++ applications, check these requirements: * Install Intel(R) GPU driver. * Install Intel(R) Level Zero GPU runtime. * Install Intel(R) oneAPI DPC++ Runtime and set the environment. The system is ready to be used for performance analysis with Intel VTune Profiler. Review warnings in the output above to find product limitations, if any. The system is ready for the following analyses: * Performance Snapshot * Hotspots and Threading with user-mode sampling * Hotspots with HW event-based sampling, HPC Performance Characterization, etc. * Microarchitecture Exploration * Memory Access * Hotspots with HW event-based sampling and call stacks * Threading with HW event-based sampling The following analyses have failed on the system: * GPU Compute/Media Hotspots (characterization mode) * GPU Compute/Media Hotspots (source analysis mode) Log location: /tmp/vtune-tmp-hakostra/self-checker-2023.02.06_15.51.41/log.txt