Intel(R) VTune(TM) Profiler Self Check Utility
Copyright (C) 2009-2020 Intel Corporation. All rights reserved.
Build Number: 621966

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:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\amplxe-runss.exe --context-value-list
Stdout:
  targetOS: Windows
  OS: Windows
  OSBuildNumber: 22000
  OSBitness: 64
  AdministratorPrivileges: true
  isPtraceScopeLimited: false
  isCATSupportedByCPU: true
  isL3CATAvailable: false
  isL2CATAvailable: true
  L2CATDetails: COS=8;ways=10
  isL3MonitoringSupportedByCPU: false
  isTSXAvailable: false
  isPTAvailable: true
  isHTEnabled: true
  fpgaOnBoard: None
  omniPathOnBoard: None
  genArchOnBoard: 0
  pciClassParts:
  tidValuesForIO:
  populatedIoParts:
  populatedIoUnits:
  populatedTidValuesForIO:
  isSGXAvailable: false
  Hypervisor: None
  PerfmonVersion: 5
  isMaxDRAMBandwidthMeasurementSupported: true
  preferedGpuAdapter: 0:1:0.0
  isEHFIAvailable: true
  areGpuHardwareMetricsAvailableList:
  gpuPlatformIndexList:
  ETW: OK
  isGpuBusynessAvailable: yes
  isGpuBusynessDetailsAvailable: notAccessible
  isGpuWaitAvailable: no
  isEtwCLRSupported: yes
  isFtraceAvailable:
  isMdfEtwAvailable: false
  isCSwitchAvailable: yes
  isFunctionTracingAvailable: no
  isIowaitTracingAvailable: no
  isVSyncAvailable: na
  HypervisorType: None
  isDeviceOrCredentialGuardEnabled: false
  isSEPDriverAvailable: true
  SEPDriverVersion: 5.31
  isPAXDriverLoaded: true
  PAXDriverVersion: 1.0
  platformType: 145
  CPU_NAME: Intel(R) microarchitecture code named Alderlake-S
  PMU: alderlake
  availablePmuTypes: bigcore,smallcore,cbo,ncu,imc,power
  referenceFrequency: 3700000000
  isPStateAvailable: true
  isVTSSPPDriverAvailable: true
  isNMIWatchDogTimerRunning: false
  isAOCLAvailable: false
  isTPSSAvailable: true
  isPytraceAvailable: true
  isGENDebugInfoAvailableList:
  isGTPinCollectionAvailableList:
  forceShowInlines: false
  isEnergyCollectionSupported: true
  isSocwatchDriverLoaded: true
  isCPUSupportedBySocwatch: false
  isCpuThrottlingAvailable: false
  isIPMWatchReady: true
  isNvdimmAvailable: false
  isOsCountersCollectorAvailable: true
  l0LoaderStatus: LibNotFound
  l0DevicesAvailable: false
  l0VPUDevicesAvailable: false
  l0GPUDevicesAvailable: false

Getting context values: OK
================================================================================
Check driver:
isSEPDriverAvailable: true
isPAXDriverLoaded: true
Ok
================================================================================
SEP version:
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\sep.exe -version
Stdout:
  Sampling Enabling Product Version: 5.31  built on Dec  4 2021 09:23:59
  SEP Driver Version: 5.31  (public)
  PAX Driver Version: 1.0
  Platform type: 145
  CPU name: Intel(R) microarchitecture code named Alderlake-S
  PMU: alderlake
  Driver configs: Maskable Interrupt, MULTI PEBS OFF (tracepoints not accessible), REGISTER CHECK ON
  Copyright(C) 2007-2020 Intel Corporation. All rights reserved.

Check driver with sep -version: Ok
================================================================================
HW event-based analysis (counting mode)...
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect performance-snapshot -r C:\users\kimel\Documents\VTune\Logs\result_ps -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe
Stdout:
  Addr of buf1 = 000000000099D040
  Offs of buf1 = 000000000099D180
  Addr of buf2 = 00000000029AA040
  Offs of buf2 = 00000000029AA1C0
  Addr of buf3 = 00000000049BD040
  Offs of buf3 = 00000000049BD100
  Addr of buf4 = 00000000069C4040
  Offs of buf4 = 00000000069C4140
  Threads #: 16 Win threads
  Matrix size: 2048
  Using multiply kernel: multiply1
  Execution time = 11.489 seconds
Stderr:
  vtune: Peak bandwidth measurement started.
  vtune: Peak bandwidth measurement finished.
  vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\users\kimel\Documents\VTune\Logs\result_ps -command stop.
  vtune: Collection stopped.
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\result_ps'
  
  vtune: Executing actions  0 %
  vtune: Executing actions 100 %
  vtune: Executing actions 100 % done

HW event-based analysis (counting mode) (Intel driver)   
Example of analysis types: Performance Snapshot
Collection: Ok
--------------------------------------------------------------------------------
Running finalization...
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -finalize -r C:\users\kimel\Documents\VTune\Logs\result_ps
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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-6444-boxer.sc' file
  vtune: Executing actions 25 % Loading 'systemcollector-6444-boxer.sc' file
  vtune: Executing actions 25 % Loading 'emon.0.bwhist' file
  vtune: Executing actions 25 % Loading 'C:\users\kimel\Documents\VTune\Logs\resu
  vtune: Executing actions 25 % Updating precomputed scalar metrics
  vtune: Executing actions 28 % Updating precomputed scalar metrics
  vtune: Executing actions 28 % Processing profile metrics and debug information
  vtune: Executing actions 39 % Processing profile metrics and debug information
  vtune: Executing actions 39 % Setting data model parameters
  vtune: Executing actions 39 % Resolving module symbols
  vtune: Executing actions 39 % Resolving thread name information
  vtune: Executing actions 43 % Resolving thread name information
  vtune: Executing actions 43 % Resolving call target names for dynamic code
  vtune: Executing actions 48 % Resolving call target names for dynamic code
  vtune: Executing actions 48 % Resolving interrupt name information
  vtune: Executing actions 53 % Resolving interrupt name information
  vtune: Executing actions 53 % Processing profile metrics and debug information
  vtune: Executing actions 56 % Processing profile metrics and debug information
  vtune: Executing actions 57 % Processing profile metrics and debug information
  vtune: Executing actions 58 % Processing profile metrics and debug information
  vtune: Executing actions 60 % Processing profile metrics and debug information
  vtune: Executing actions 62 % Processing profile metrics and debug information
  vtune: Executing actions 63 % Processing profile metrics and debug information
  vtune: Executing actions 63 % Preparing output tree
  vtune: Executing actions 63 % Parsing columns in input tree
  vtune: Executing actions 64 % Parsing columns in input tree
  vtune: Executing actions 64 % Creating top-level columns
  vtune: Executing actions 65 % Creating top-level columns
  vtune: Executing actions 65 % Creating top-level rows
  vtune: Executing actions 67 % Creating top-level rows
  vtune: Executing actions 67 % Setting data model parameters
  vtune: Executing actions 68 % Setting data model parameters
  vtune: Executing actions 68 % Precomputing frequently used data
  vtune: Executing actions 68 % Precomputing frequently used data
  vtune: Executing actions 69 % Precomputing frequently used data
  vtune: Executing actions 70 % Precomputing frequently used data
  vtune: Executing actions 71 % Precomputing frequently used data
  vtune: Executing actions 72 % Precomputing frequently used data
  vtune: Executing actions 73 % Precomputing frequently used data
  vtune: Executing actions 74 % Precomputing frequently used data
  vtune: Executing actions 75 % Precomputing frequently used data
  vtune: Executing actions 76 % Precomputing frequently used data
  vtune: Executing actions 77 % Precomputing frequently used data
  vtune: Executing actions 78 % Precomputing frequently used data
  vtune: Executing actions 79 % Precomputing frequently used data
  vtune: Executing actions 79 % Updating precomputed scalar metrics
  vtune: Executing actions 82 % Updating precomputed scalar metrics
  vtune: Executing actions 82 % Discarding redundant overtime data
  vtune: Executing actions 85 % Discarding redundant overtime data
  vtune: Executing actions 85 % Saving the result
  vtune: Executing actions 89 % Saving the result
  vtune: Executing actions 92 % Saving the result
  vtune: Executing actions 99 % Saving the result
  vtune: Executing actions 101 % Saving the result
  vtune: Executing actions 101 % done

Finalization: Ok
--------------------------------------------------------------------------------
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -R summary -r C:\users\kimel\Documents\VTune\Logs\result_ps
Stdout:
  Elapsed Time: 11.555s
  IPC: 0.417
  | 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.402
  | 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.474
  | 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.001
  DP GFLOPS: 1.108
  x87 GFLOPS: 0.000
  Average CPU Frequency: 4.276 GHz
  Logical Core Utilization: 96.0% (15.359 out of 16)
  Physical Core Utilization: 84.2% (8.415 out of 10)
  Microarchitecture Usage: 12.0% 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: 13.0% of Pipeline Slots
  Front-End Bound: 1.7% of Pipeline Slots
  Bad Speculation: 0.1% of Pipeline Slots
  Back-End Bound: 85.2% of Pipeline Slots
  | A significant portion of pipeline slots are remaining empty. When
  | operations take too long in the back-end, they introduce bubbles in
  | the pipeline that ultimately cause fewer pipeline slots containing
  | useful work to be retired per cycle than the machine is capable to
  | support. This opportunity cost results in slower execution. Long-
  | latency operations like divides and memory operations can cause this,
  | as can too many operations being directed to a single execution port
  | (for example, more multiply operations arriving in the back-end per
  | cycle than the execution unit can support).
  |
  Memory Bound: 73.1% of Pipeline Slots
  | The metric value is high. This can indicate that the significant
  | fraction of execution pipeline slots could be stalled due to
  | demand memory load and stores. Use Memory Access analysis to have
  | the metric breakdown by memory hierarchy, memory bandwidth
  | information, correlation by memory objects.
  |
  L1 Bound: 1.6% of Clockticks
  L2 Bound: 0.3% of Clockticks
  L3 Bound: 33.6% of Clockticks
  | This metric shows how often CPU was stalled on L3 cache, or
  | contended with a sibling Core. Avoiding cache misses (L2
  | misses/L3 hits) improves the latency and increases
  | performance.
  |
  DRAM Bound: 46.2% of Clockticks
  | This metric shows how often CPU was stalled on the main
  | memory (DRAM). Caching typically improves the latency and
  | increases performance.
  |
  Memory Bandwidth: 74.9% of Clockticks
  | Issue: A significant fraction of cycles was stalled due
  | to approaching bandwidth limits of the main memory
  | (DRAM).
  |
  | Tips: Improve data accesses to reduce cacheline transfers
  | from/to memory using these possible techniques:
  |     - Consume all bytes of each cacheline before it is
  |       evicted (for example, reorder structure elements
  |       and split non-hot ones).
  |     - Merge compute-limited and bandwidth-limited loops.
  |     - Use NUMA optimizations on a multi-socket system.
  |
  | Note: software prefetches do not help a bandwidth-limited
  | application.
  |
  Memory Latency: 22.5% of Clockticks
  | Issue: A significant fraction of cycles was stalled due
  | to the latency of the main memory (DRAM).
  |
  | Tips: Improve data accesses or interleave them with
  | compute using such possible techniques as data layout re-
  | structuring or software prefetches (through the
  | compiler).
  |
  Core Bound: 12.1% of Pipeline Slots
  | This metric represents how much Core non-memory issues were of a
  | bottleneck. Shortage in hardware compute resources, or
  | dependencies software's instructions are both categorized under
  | Core Bound. Hence it may indicate the machine ran out of an OOO
  | resources, certain execution units are overloaded or dependencies
  | in program's data- or instruction- flow are limiting the
  | performance (e.g. FP-chained long-latency arithmetic operations).
  |
  E-Core
  Retiring: 9.5% of Pipeline Slots
  Front-End Bound: 3.6% of Pipeline Slots
  Bad Speculation: 4.3% of Pipeline Slots
  Back-End Bound: 83.0% 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: 83.0% of Pipeline Slots
  | Resource Bound
  |
  Alternative Back-End Bound: 83.0% 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: 27.2%
  | This metric represents how much Core non-memory issues were of a
  | bottleneck. Shortage in hardware compute resources, or
  | dependencies software's instructions are both categorized under
  | Core Bound. Hence it may indicate the machine ran out of an OOO
  | resources, certain execution units are overloaded or dependencies
  | in program's data- or instruction- flow are limiting the
  | performance (e.g. FP-chained long-latency arithmetic operations).
  |
  Memory Bound: 55.9%
  | 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: 5.4%
  | 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: 14.9%
  | 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: 35.6%
  | This metric shows how often CPU was stalled on the main
  | memory (DRAM). Caching typically improves the latency and
  | increases performance.
  |
  Memory Bound: 73.1% of Pipeline Slots
  | The metric value is high. This can indicate that the significant fraction of
  | execution pipeline slots could be stalled due to demand memory load and
  | stores. Use Memory Access analysis to have the metric breakdown by memory
  | hierarchy, memory bandwidth information, correlation by memory objects.
  |
  P-Core
  Memory Bound: 73.1% of Pipeline Slots
  | The metric value is high. This can indicate that the significant
  | fraction of execution pipeline slots could be stalled due to demand
  | memory load and stores. Use Memory Access analysis to have the metric
  | breakdown by memory hierarchy, memory bandwidth information,
  | correlation by memory objects.
  |
  Cache Bound: 35.4% 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: 46.2% of Clockticks
  | This metric shows how often CPU was stalled on the main memory
  | (DRAM). Caching typically improves the latency and increases
  | performance.
  |
  E-Core
  Memory Bound: 55.9%
  | 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: 20.3% 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: 35.6%
  | 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: 74.3% from SP FP
  128-bit: 74.3% 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: 25.7% from SP FP
  DP FLOPs: 5.3% 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: 94.7% of uOps
  Collection and Platform Info
  Application Command Line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe
  Operating System: Microsoft Windows 10
  Computer Name: boxer
  Result Size: 3.7 MB
  Collection start time: 23:41:15 02/03/2022 UTC
  Collection stop time: 23:41:27 02/03/2022 UTC
  Collector Type: Event-based counting driver
  CPU
  Name: Intel(R) microarchitecture code named Alderlake-S
  Frequency: 3.686 GHz
  Logical CPU Count: 16
  Max DRAM Single-Package Bandwidth: 52.000 GB/s
  Cache Allocation Technology
  Level 2 capability: available
  Level 3 capability: not detected
  
  Recommendations:
  Hotspots: Start with Hotspots analysis to understand the efficiency of your algorithm.
  | Use Hotspots analysis to identify the most time consuming functions.
  | Drill down to see the time spent on every line of code.
  Memory Access: The Memory Bound metric is high  (73.1%). A significant fraction of execution pipeline slots could be stalled due to demand memory load and stores.
  | Use Memory Access analysis to measure metrics that can identify memory
  | access issues.
  HPC Performance Characterization: Vectorization (0.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.
  
  If you want to skip descriptions of detected performance issues in the report,
  enter: vtune -report summary -report-knob show-issues=false -r <my_result_dir>.
  Alternatively, you may view the report in the csv format: vtune -report
  <report_name> -format=csv.
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect hotspots -r C:\users\kimel\Documents\VTune\Logs\result_tpss -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe
Stdout:
  Addr of buf1 = 0000000006072040
  Offs of buf1 = 0000000006072180
  Addr of buf2 = 0000000008089040
  Offs of buf2 = 00000000080891C0
  Addr of buf3 = 000000000A09C040
  Offs of buf3 = 000000000A09C100
  Addr of buf4 = 000000000C0A7040
  Offs of buf4 = 000000000C0A7140
  Threads #: 16 Win threads
  Matrix size: 2048
  Using multiply kernel: multiply1
  Execution time = 13.665 seconds
Stderr:
  vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\users\kimel\Documents\VTune\Logs\result_tpss -command stop.
  vtune: Collection stopped.
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\result_tpss'
  
  vtune: Executing actions  0 %
  vtune: Executing actions 100 %
  vtune: Executing actions 100 % done

Instrumentation based analysis check   
Example of analysis types: Hotspots and Threading with user-mode sampling
Collection: Ok
--------------------------------------------------------------------------------
Running finalization...
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -finalize -r C:\users\kimel\Documents\VTune\Logs\result_tpss
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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-15672-boxer.sc' file
  vtune: Executing actions 25 % Loading 'systemcollector-15672-boxer.sc' file
  vtune: Executing actions 25 % Loading '4660-3028.0.trace' file
  vtune: Executing actions 25 % Loading 'emon.0.bwhist' file
  vtune: Executing actions 25 % Loading 'C:\users\kimel\Documents\VTune\Logs\resu
  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 `KERNELBASE.dll'
  vtune: Executing actions 39 % Resolving information for `ucrtbase.dll'
  vtune: Executing actions 39 % Resolving information for `ntdll.dll'
  vtune: Executing actions 39 % Resolving information for `KERNEL32.DLL'
  vtune: Executing actions 39 % Resolving information for `tpsstool.dll'
  vtune: Executing actions 39 % Resolving information for `matrix.exe'
  vtune: Executing actions 40 % Resolving information for `matrix.exe'
  vtune: Executing actions 41 % Resolving information for `matrix.exe'
  vtune: Executing actions 42 % Resolving information for `matrix.exe'
  vtune: Executing actions 43 % Resolving information for `matrix.exe'
  vtune: Warning: Cannot locate debugging information for file `C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\tpsstool.dll'.
  
  vtune: Executing actions 44 % Resolving information for `matrix.exe'
  vtune: Executing actions 45 % Resolving information for `matrix.exe'
  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 60 % Processing profile metrics and debug information
  vtune: Executing actions 62 % Processing profile metrics and debug information
  vtune: Executing actions 63 % Processing profile metrics and debug information
  vtune: Executing actions 63 % Setting data model parameters
  vtune: Executing actions 64 % Setting data model parameters
  vtune: Executing actions 64 % Precomputing frequently used data
  vtune: Executing actions 64 % Precomputing frequently used data
  vtune: Executing actions 67 % Precomputing frequently used data
  vtune: Executing actions 70 % Precomputing frequently used data
  vtune: Executing actions 73 % Precomputing frequently used data
  vtune: Executing actions 76 % Precomputing frequently used data
  vtune: Executing actions 76 % Updating precomputed scalar metrics
  vtune: Executing actions 78 % Updating precomputed scalar metrics
  vtune: Executing actions 78 % Discarding redundant overtime data
  vtune: Executing actions 82 % Discarding redundant overtime data
  vtune: Executing actions 82 % Saving the result
  vtune: Executing actions 85 % Saving the result
  vtune: Executing actions 89 % Saving the result
  vtune: Executing actions 99 % Saving the result
  vtune: Executing actions 100 % Saving the result
  vtune: Executing actions 100 % done

Finalization: Ok
--------------------------------------------------------------------------------
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\users\kimel\Documents\VTune\Logs\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,213.484725,213.484725,0.0,0.0,matrix.exe,multiply1,multiply.c,0x1400017f0
  init_arr,0.028969,0.028969,0.0,0.0,matrix.exe,init_arr,matrix.c,0x1400010a0
  WaitForMultipleObjects,0.020811,0.0,0.020811,0.0,KERNELBASE.dll,WaitForMultipleObjects,[Unknown],0x18004fa00
  free_base,0.003896,0.003896,0.0,0.0,ucrtbase.dll,free_base,[Unknown],0x180012170
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect hotspots -knob sampling-mode=hw -r C:\users\kimel\Documents\VTune\Logs\result_ah -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe
Stdout:
  Addr of buf1 = 00000000009C2040
  Offs of buf1 = 00000000009C2180
  Addr of buf2 = 00000000029D0040
  Offs of buf2 = 00000000029D01C0
  Addr of buf3 = 00000000049EB040
  Offs of buf3 = 00000000049EB100
  Addr of buf4 = 00000000069F3040
  Offs of buf4 = 00000000069F3140
  Threads #: 16 Win threads
  Matrix size: 2048
  Using multiply kernel: multiply1
  Execution time = 11.813 seconds
Stderr:
  vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\users\kimel\Documents\VTune\Logs\result_ah -command stop.
  vtune: Collection stopped.
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\result_ah'
  
  vtune: Executing actions  0 %
  vtune: Executing actions 100 %
  vtune: Executing actions 100 % done

HW event-based analysis check (Intel driver)   
Example of analysis types: Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
Collection: Ok
--------------------------------------------------------------------------------
Running finalization...
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -finalize -r C:\users\kimel\Documents\VTune\Logs\result_ah
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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-10920-boxer.sc' file
  vtune: Executing actions 25 % Loading 'systemcollector-10920-boxer.sc' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' file
  vtune: Executing actions 25 % Loading 'sep99c.20220303T004202.137738.tb7' 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 `hdaudbus.sys'
  vtune: Executing actions 39 % Resolving information for `ucrtbase.dll'
  vtune: Executing actions 39 % Resolving information for `wdf01000.sys'
  vtune: Executing actions 39 % Resolving information for `ntoskrnl.exe'
  vtune: Executing actions 39 % Resolving information for `volmgr.sys'
  vtune: Executing actions 39 % Resolving information for `volsnap.sys'
  vtune: Executing actions 39 % Resolving information for `ntfs.sys'
  vtune: Executing actions 39 % Resolving information for `kernelbase.dll'
  vtune: Executing actions 39 % Resolving information for `netwtw10.sys'
  vtune: Executing actions 39 % Resolving information for `iorate.sys'
  vtune: Executing actions 39 % Resolving information for `partmgr.sys'
  vtune: Executing actions 40 % Resolving information for `partmgr.sys'
  vtune: Executing actions 40 % Resolving information for `dxgmms2.sys'
  vtune: Executing actions 40 % Resolving information for `classpnp.sys'
  vtune: Executing actions 40 % Resolving information for `dxgkrnl.sys'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\netwtw10.sys'.
  
  vtune: Executing actions 40 % Resolving information for `matrix.exe'
  vtune: Executing actions 41 % Resolving information for `matrix.exe'
  vtune: Executing actions 41 % Resolving information for `secnvme.sys'
  vtune: Executing actions 41 % Resolving information for `fltmgr.sys'
  vtune: Executing actions 41 % Resolving information for `msvcrt.dll'
  vtune: Executing actions 41 % Resolving information for `storport.sys'
  vtune: Executing actions 42 % Resolving information for `storport.sys'
  vtune: Executing actions 42 % Resolving information for `netio.sys'
  vtune: Executing actions 42 % Resolving information for `sepdrv5.sys'
  vtune: Executing actions 42 % Resolving information for `ntdll.dll'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\secnvme.sys'.
  
  vtune: Executing actions 43 % Resolving information for `ntdll.dll'
  vtune: Executing actions 43 % Resolving information for `cng.sys'
  vtune: Executing actions 43 % Resolving information for `intelppm.sys'
  vtune: Executing actions 43 % Resolving information for `tcpip.sys'
  vtune: Executing actions 43 % Resolving information for `nvlddmkm.sys'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\sepdrv5.sys'.
  
  vtune: Executing actions 44 % Resolving information for `nvlddmkm.sys'
  vtune: Executing actions 45 % Resolving information for `nvlddmkm.sys'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\driverstore\filerepository\nv_dispig.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.sys'.
  
  vtune: Executing actions 45 % Resolving bottom user stack information
  vtune: Executing actions 46 % Resolving bottom user stack information
  vtune: Executing actions 47 % Resolving bottom user stack information
  vtune: Executing actions 47 % Resolving thread name information
  vtune: Executing actions 48 % Resolving thread name information
  vtune: Executing actions 48 % Resolving call target names for dynamic code
  vtune: Executing actions 50 % Resolving call target names for dynamic code
  vtune: Executing actions 50 % Resolving interrupt name information
  vtune: Executing actions 53 % Resolving interrupt name information
  vtune: Executing actions 53 % Processing profile metrics and debug information
  vtune: Executing actions 56 % Processing profile metrics and debug information
  vtune: Executing actions 57 % Processing profile metrics and debug information
  vtune: Executing actions 58 % Processing profile metrics and debug information
  vtune: Executing actions 60 % Processing profile metrics and debug information
  vtune: Executing actions 60 % Setting data model parameters
  vtune: Executing actions 60 % Precomputing frequently used data
  vtune: Executing actions 60 % Precomputing frequently used data
  vtune: Executing actions 62 % Precomputing frequently used data
  vtune: Executing actions 63 % Precomputing frequently used data
  vtune: Executing actions 64 % Precomputing frequently used data
  vtune: Executing actions 65 % Precomputing frequently used data
  vtune: Executing actions 66 % Precomputing frequently used data
  vtune: Executing actions 67 % Precomputing frequently used data
  vtune: Executing actions 68 % Precomputing frequently used data
  vtune: Executing actions 70 % Precomputing frequently used data
  vtune: Executing actions 71 % Precomputing frequently used data
  vtune: Executing actions 72 % Precomputing frequently used data
  vtune: Executing actions 72 % Updating precomputed scalar metrics
  vtune: Executing actions 75 % Updating precomputed scalar metrics
  vtune: Executing actions 75 % Discarding redundant overtime data
  vtune: Executing actions 78 % Discarding redundant overtime data
  vtune: Executing actions 78 % Saving the result
  vtune: Executing actions 82 % Saving the result
  vtune: Executing actions 85 % Saving the result
  vtune: Executing actions 100 % Saving the result
  vtune: Executing actions 100 % done

Finalization: Ok
--------------------------------------------------------------------------------
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\users\kimel\Documents\VTune\Logs\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,183.212436,183.212436,0.0,0.0,318055700000,11.6,11.6,2.461349,matrix.exe,multiply1,multiply.c,0x1400017f0
  KiInterruptDispatchNoLockNoEtw,0.163601,0.163601,0.0,0.0,122100000,33.3,33.3,5.515152,ntoskrnl.exe,KiInterruptDispatchNoLockNoEtw,[Unknown],0x140418660
  func@0x31280,0.151557,0.151557,0.0,0.0,51800000,32.9,32.9,12.214286,sepdrv5.sys,func@0x31280,[Unknown],0x31280
  func@0x208a8,0.057210,0.057210,0.0,0.0,370000000,92.8,92.8,0.720000,sepdrv5.sys,func@0x208a8,[Unknown],0x208a8
  HalpApicX2EndOfInterrupt,0.052192,0.052192,0.0,0.0,7400000,36.7,36.7,36.500000,ntoskrnl.exe,HalpApicX2EndOfInterrupt,[Unknown],0x1404124a0
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect uarch-exploration -r C:\users\kimel\Documents\VTune\Logs\result_ge -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe
Stdout:
  Addr of buf1 = 000000000098A040
  Offs of buf1 = 000000000098A180
  Addr of buf2 = 0000000002999040
  Offs of buf2 = 00000000029991C0
  Addr of buf3 = 00000000049AB040
  Offs of buf3 = 00000000049AB100
  Addr of buf4 = 00000000069B4040
  Offs of buf4 = 00000000069B4140
  Threads #: 16 Win threads
  Matrix size: 2048
  Using multiply kernel: multiply1
  Execution time = 14.813 seconds
Stderr:
  vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\users\kimel\Documents\VTune\Logs\result_ge -command stop.
  vtune: Collection stopped.
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\result_ge'
  
  vtune: Executing actions  0 %
  vtune: Executing actions 100 %
  vtune: Executing actions 100 % done

HW event-based analysis check (Intel driver)   
Example of analysis types: Microarchitecture Exploration
Collection: Ok
--------------------------------------------------------------------------------
Running finalization...
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -finalize -r C:\users\kimel\Documents\VTune\Logs\result_ge
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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-12648-boxer.sc' file
  vtune: Executing actions 25 % Loading 'systemcollector-12648-boxer.sc' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' file
  vtune: Executing actions 25 % Loading 'sep3588.20220303T004236.635411.tb7' 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 `ucrtbase.dll'
  vtune: Executing actions 39 % Resolving information for `hidparse.sys'
  vtune: Executing actions 39 % Resolving information for `hidusb.sys'
  vtune: Executing actions 39 % Resolving information for `ndis.sys'
  vtune: Executing actions 39 % Resolving information for `volsnap.sys'
  vtune: Executing actions 39 % Resolving information for `hdaudbus.sys'
  vtune: Executing actions 39 % Resolving information for `watchdog.sys'
  vtune: Executing actions 39 % Resolving information for `usbhub3.sys'
  vtune: Executing actions 39 % Resolving information for `fltmgr.sys'
  vtune: Executing actions 39 % Resolving information for `cng.sys'
  vtune: Executing actions 39 % Resolving information for `partmgr.sys'
  vtune: Executing actions 39 % Resolving information for `ucx01000.sys'
  vtune: Executing actions 39 % Resolving information for `acpi.sys'
  vtune: Executing actions 39 % Resolving information for `ndu.sys'
  vtune: Executing actions 40 % Resolving information for `ndu.sys'
  vtune: Executing actions 40 % Resolving information for `ntfs.sys'
  vtune: Executing actions 40 % Resolving information for `nwifi.sys'
  vtune: Executing actions 40 % Resolving information for `iorate.sys'
  vtune: Executing actions 40 % Resolving information for `wdiwifi.sys'
  vtune: Executing actions 40 % Resolving information for `kernelbase.dll'
  vtune: Executing actions 40 % Resolving information for `wdf01000.sys'
  vtune: Executing actions 41 % Resolving information for `wdf01000.sys'
  vtune: Executing actions 41 % Resolving information for `matrix.exe'
  vtune: Executing actions 41 % Resolving information for `secnvme.sys'
  vtune: Executing actions 41 % Resolving information for `dxgmms2.sys'
  vtune: Executing actions 41 % Resolving information for `usbxhci.sys'
  vtune: Executing actions 41 % Resolving information for `dxgkrnl.sys'
  vtune: Executing actions 42 % Resolving information for `dxgkrnl.sys'
  vtune: Executing actions 42 % Resolving information for `sepdrv5.sys'
  vtune: Executing actions 42 % Resolving information for `ntoskrnl.exe'
  vtune: Executing actions 42 % Resolving information for `classpnp.sys'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\secnvme.sys'.
  
  vtune: Executing actions 42 % Resolving information for `ntdll.dll'
  vtune: Executing actions 42 % Resolving information for `volmgr.sys'
  vtune: Executing actions 42 % Resolving information for `storport.sys'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\sepdrv5.sys'.
  
  vtune: Executing actions 42 % Resolving information for `hidclass.sys'
  vtune: Executing actions 43 % Resolving information for `hidclass.sys'
  vtune: Executing actions 43 % Resolving information for `netio.sys'
  vtune: Executing actions 43 % Resolving information for `wpprecorder.sys'
  vtune: Executing actions 43 % Resolving information for `fvevol.sys'
  vtune: Executing actions 43 % Resolving information for `mouhid.sys'
  vtune: Executing actions 43 % Resolving information for `nvlddmkm.sys'
  vtune: Executing actions 43 % Resolving information for `tcpip.sys'
  vtune: Executing actions 44 % Resolving information for `tcpip.sys'
  vtune: Executing actions 44 % Resolving information for `netwtw10.sys'
  vtune: Executing actions 44 % Resolving information for `usbccgp.sys'
  vtune: Executing actions 44 % Resolving information for `intelppm.sys'
  vtune: Executing actions 44 % Resolving information for `kernel32.dll'
  vtune: Executing actions 44 % Resolving information for `mouclass.sys'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\driverstore\filerepository\nv_dispig.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.sys'.
  
  vtune: Executing actions 45 % Resolving information for `mouclass.sys'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\netwtw10.sys'.
  
  vtune: Executing actions 46 % Resolving information for `mouclass.sys'
  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
--------------------------------------------------------------------------------
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\users\kimel\Documents\VTune\Logs\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: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:Microcode Sequencer(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer: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 Cost(%),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,226.051900,966558400000,761737500000,204820900000,318011300000,240007900000,78003400000,3.039384,3.173802,2.625795,10.3,10.3,5.5,0.0,5.5,0.0,5.7,0.3,0.3,0.0,0.0,0.0,0.0,0.0,0.0,1.0,1.0,0.0,0.0,0.1,0.0,0.1,0.0,0.0,0.0,0.0,0.1,0.1,0.0,0.0,0.2,1.3,95.4,0.3,0.6,0.0,0.5,88.1,78.7,0.3,100.0,100.0,9.5,0.0,0.0,0.0,0.1,0.2,28.1,0.0,12.7,9.1,0.6,54.0,71.9,23.9,0.0,0.0,0.0,0.0,0.0,0.2,0.2,0.0,9.4,0.0,10.0,3.0,0.0,0.0,0.0,0.0,6.6,3.4,4.2,5.6,6.5,9.3,5.7,10.3,1.7,5.9,5.9,0.0,5.9,0.0,1.2,0.0,0.0,0.0,0.0,0.0,1.6,0.0,1.2,0.0,0.4,1.8,0.2,2.2,0.0,2.2,76.1,76.1,87.4,0.0,0.0,0.0,0.0,0.0,76.1,37.9,38.1,3.0,6.9,28.2,4275825145.166534,matrix.exe,multiply1,multiply.c,0x1400017f0
  KiInterruptDispatchNoLockNoEtw,0.228841,954600000,765900000,188700000,170200000,114700000,55500000,5.608696,6.677419,3.400000,3.8,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,7.6,5.1,0.0,5.1,17.1,0.0,3.5,0.0,0.0,0.0,0.0,0.0,0.7,0.0,9.2,17.1,10.8,0.0,0.0,0.0,0.0,0.0,17.1,22.3,6.3,16.0,56.8,6.3,11.8,100.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,4.7,0.0,0.0,0.0,0.0,2.4,23.5,30.6,0.0,7.1,0.0,0.0,0.0,7.6,7.6,0.0,50.5,0.0,54.2,49.4,55.9,0.0,0.0,0.0,4.7,4.7,0.0,15.1,10.8,21.6,43.2,0.0,0.0,40.8,24.5,0.0,24.5,16.3,44.5,2.2,2.2,0.0,0.0,0.0,3.7,3.7,0.0,0.0,0.0,0.0,0.7,0.0,0.0,0.0,41.5,41.5,0.0,0.0,0.0,0.0,0.0,100.0,41.5,17.8,23.7,20.8,0.7,2.2,4171452502.578947,ntoskrnl.exe,KiInterruptDispatchNoLockNoEtw,[Unknown],0x140418660
  func@0x31280,0.120443,647500000,580900000,66600000,25900000,18500000,7400000,25.000000,31.400000,9.000000,3.1,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,10.8,3.1,0.0,3.1,56.4,51.0,0.0,0.6,6.2,0.0,6.2,0.0,0.3,0.0,4.6,5.4,0.0,0.0,0.0,0.0,0.0,0.0,1.3,17.3,0.0,17.3,23.2,0.0,6.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,27.9,15.5,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,23.2,0.0,68.4,49.6,17.7,0.0,0.0,0.0,18.6,6.2,6.2,16.2,0.0,27.0,0.0,0.0,6.8,31.5,14.7,0.0,14.7,16.8,100.0,2.1,0.0,0.0,0.0,2.1,10.5,10.5,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,8.4,8.4,0.0,0.0,0.0,0.0,2.1,96.7,8.4,0.0,25.2,21.0,4.2,0.0,5375999833.750000,sepdrv5.sys,func@0x31280,[Unknown],0x31280
  func@0x208a8,0.072266,299700000,222000000,77700000,447700000,284900000,162800000,0.669421,0.779221,0.477273,22.2,22.2,0.0,0.0,0.0,0.0,0.0,5.5,1.1,0.0,15.5,0.0,0.0,0.0,0.0,16.6,16.6,0.0,1.6,0.0,0.0,0.0,0.0,7.3,0.0,0.0,0.0,27.0,0.0,27.0,0.0,50.0,0.0,13.6,5.8,0.0,5.8,55.4,27.7,48.6,100.0,100.0,4.9,0.0,0.0,0.0,0.0,0.0,40.5,0.0,0.0,0.0,0.0,0.0,24.3,64.9,0.0,24.3,0.0,0.0,0.0,40.5,37.8,2.7,27.7,0.0,3.6,0.0,4.1,0.0,0.0,0.0,0.0,16.2,16.2,10.8,0.0,0.0,54.1,18.0,27.0,37.8,37.8,0.0,37.8,0.0,19.8,0.0,0.0,0.0,0.0,0.0,3.6,1.8,0.0,0.0,1.8,0.0,0.0,0.0,0.0,0.0,41.4,41.4,16.2,7.2,0.0,0.0,1.8,32.4,41.4,18.0,23.4,5.4,18.0,0.0,4147199871.750000,sepdrv5.sys,func@0x208a8,[Unknown],0x208a8
  HalpApicX2EndOfInterrupt,0.068251,299700000,192400000,107300000,3700000,3700000,0,81.000000,52.000000,,11.1,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,14.8,7.4,0.0,7.4,72.4,22.3,14.0,0.0,4.7,0.0,4.7,0.0,0.9,0.0,2.8,50.1,0.0,0.0,0.0,0.0,0.0,0.0,0.9,16.5,0.0,16.5,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,28.1,9.4,0.0,18.7,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,39.5,37.4,18.7,0.0,0.0,0.0,0.0,18.7,18.7,64.9,54.1,54.1,100.0,0.0,0.0,9.1,0.0,0.0,0.0,13.0,67.8,0.0,0.0,0.0,0.0,0.0,10.4,6.5,0.0,0.0,3.9,14.4,5.2,0.0,0.0,0.0,9.1,9.1,0.0,0.0,0.0,0.0,0.0,69.2,9.1,9.1,0.0,0.0,0.0,0.0,4391152805.382353,ntoskrnl.exe,HalpApicX2EndOfInterrupt,[Unknown],0x1404124a0
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect memory-access -r C:\users\kimel\Documents\VTune\Logs\result_ma -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe
Stdout:
  Addr of buf1 = 00000000009D9040
  Offs of buf1 = 00000000009D9180
  Addr of buf2 = 00000000029E1040
  Offs of buf2 = 00000000029E11C0
  Addr of buf3 = 00000000049FD040
  Offs of buf3 = 00000000049FD100
  Addr of buf4 = 0000000006A0F040
  Offs of buf4 = 0000000006A0F140
  Threads #: 16 Win threads
  Matrix size: 2048
  Using multiply kernel: multiply1
  Execution time = 12.455 seconds
Stderr:
  vtune: Peak bandwidth measurement started.
  vtune: Peak bandwidth measurement finished.
  vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\users\kimel\Documents\VTune\Logs\result_ma -command stop.
  vtune: Collection stopped.
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\result_ma'
  
  vtune: Executing actions  0 %
  vtune: Executing actions 100 %
  vtune: Executing actions 100 % done

HW event-based analysis with uncore events (Intel driver)   
Example of analysis types: Memory Access
Collection: Ok
--------------------------------------------------------------------------------
Running finalization...
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -finalize -r C:\users\kimel\Documents\VTune\Logs\result_ma
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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-13352-boxer.sc' file
  vtune: Executing actions 25 % Loading 'systemcollector-13352-boxer.sc' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' file
  vtune: Executing actions 25 % Loading 'sep2a10.20220303T004352.750626.tb7' 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 `acpi.sys'
  vtune: Executing actions 39 % Resolving information for `hdaudbus.sys'
  vtune: Executing actions 39 % Resolving information for `ucx01000.sys'
  vtune: Executing actions 39 % Resolving information for `ntoskrnl.exe'
  vtune: Executing actions 39 % Resolving information for `watchdog.sys'
  vtune: Executing actions 39 % Resolving information for `dxgkrnl.sys'
  vtune: Executing actions 39 % Resolving information for `kernelbase.dll'
  vtune: Executing actions 39 % Resolving information for `dxgmms2.sys'
  vtune: Executing actions 39 % Resolving information for `volsnap.sys'
  vtune: Executing actions 39 % Resolving information for `mouclass.sys'
  vtune: Executing actions 39 % Resolving information for `wdf01000.sys'
  vtune: Executing actions 39 % Resolving information for `hidusb.sys'
  vtune: Executing actions 39 % Resolving information for `storport.sys'
  vtune: Executing actions 40 % Resolving information for `storport.sys'
  vtune: Executing actions 40 % Resolving information for `wdiwifi.sys'
  vtune: Executing actions 40 % Resolving information for `ntfs.sys'
  vtune: Executing actions 40 % Resolving information for `matrix.exe'
  vtune: Executing actions 40 % Resolving information for `hidclass.sys'
  vtune: Executing actions 40 % Resolving information for `classpnp.sys'
  vtune: Executing actions 41 % Resolving information for `classpnp.sys'
  vtune: Executing actions 41 % Resolving information for `usbhub3.sys'
  vtune: Executing actions 41 % Resolving information for `netio.sys'
  vtune: Executing actions 41 % Resolving information for `sepdrv5.sys'
  vtune: Executing actions 41 % Resolving information for `wpprecorder.sys'
  vtune: Executing actions 42 % Resolving information for `wpprecorder.sys'
  vtune: Executing actions 42 % Resolving information for `iorate.sys'
  vtune: Executing actions 42 % Resolving information for `usbxhci.sys'
  vtune: Executing actions 42 % Resolving information for `mouhid.sys'
  vtune: Executing actions 42 % Resolving information for `secnvme.sys'
  vtune: Executing actions 42 % Resolving information for `cng.sys'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\sepdrv5.sys'.
  
  vtune: Executing actions 42 % Resolving information for `intelppm.sys'
  vtune: Executing actions 42 % Resolving information for `hidparse.sys'
  vtune: Executing actions 43 % Resolving information for `hidparse.sys'
  vtune: Executing actions 43 % Resolving information for `usbccgp.sys'
  vtune: Executing actions 43 % Resolving information for `ntdll.dll'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\secnvme.sys'.
  
  vtune: Executing actions 43 % Resolving information for `fvevol.sys'
  vtune: Executing actions 43 % Resolving information for `tcpip.sys'
  vtune: Executing actions 44 % Resolving information for `tcpip.sys'
  vtune: Executing actions 44 % Resolving information for `nwifi.sys'
  vtune: Executing actions 44 % Resolving information for `nvlddmkm.sys'
  vtune: Executing actions 44 % Resolving information for `netwtw10.sys'
  vtune: Executing actions 44 % Resolving information for `ndis.sys'
  vtune: Executing actions 45 % Resolving information for `ndis.sys'
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\netwtw10.sys'.
  vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\driverstore\filerepository\nv_dispig.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.sys'.
  
  vtune: Executing actions 46 % Resolving information for `ndis.sys'
  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 80 % Precomputing frequently used data
  vtune: Executing actions 80 % Updating precomputed scalar metrics
  vtune: Executing actions 82 % Updating precomputed scalar metrics
  vtune: Executing actions 82 % Discarding redundant overtime data
  vtune: Executing actions 85 % Discarding redundant overtime data
  vtune: Executing actions 85 % Saving the result
  vtune: Executing actions 89 % Saving the result
  vtune: Executing actions 92 % Saving the result
  vtune: Executing actions 100 % Saving the result
  vtune: Executing actions 100 % done

Finalization: Ok
--------------------------------------------------------------------------------
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\users\kimel\Documents\VTune\Logs\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,Module,Function (Full),Source File,Start Address
  multiply1,189.813700,72.0,0.0,0.2,29.0,50.7,0.0,56.0,4.8,10.9,40.4,155927277678,17306519180,1678511063,matrix.exe,multiply1,multiply.c,0x1400017f0
  KiInterruptDispatchNoLockNoEtw,0.255941,16.1,2.9,0.0,4.4,0.0,0.0,18.1,16.5,0.5,1.2,126603798,43901317,0,ntoskrnl.exe,KiInterruptDispatchNoLockNoEtw,[Unknown],0x140418660
  KeClockInterruptNotify,0.227837,69.9,0.0,3.9,52.1,3.9,0.0,37.1,11.8,23.3,2.1,9000270,16800504,0,ntoskrnl.exe,KeClockInterruptNotify,[Unknown],0x140301d20
  func@0x31280,0.172635,0.0,0.0,0.0,0.0,0.0,0.0,17.5,13.6,2.2,1.8,3300099,0,0,sepdrv5.sys,func@0x31280,[Unknown],0x31280
  HalpApicX2EndOfInterrupt,0.118435,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,12100363,0,0,ntoskrnl.exe,HalpApicX2EndOfInterrupt,[Unknown],0x1404124a0
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r C:\users\kimel\Documents\VTune\Logs\result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe
Stdout:
  Addr of buf1 = 000000000076C040
  Offs of buf1 = 000000000076C180
  Addr of buf2 = 000000000277A040
  Offs of buf2 = 000000000277A1C0
  Addr of buf3 = 000000000478B040
  Offs of buf3 = 000000000478B100
  Addr of buf4 = 0000000006790040
  Offs of buf4 = 0000000006790140
  Threads #: 16 Win threads
  Matrix size: 2048
  Using multiply kernel: multiply1
  Execution time = 15.774 seconds
Stderr:
  vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\users\kimel\Documents\VTune\Logs\result_ah_with_stacks -command stop.
  vtune: Collection stopped.
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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
--------------------------------------------------------------------------------
Running finalization...
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -finalize -r C:\users\kimel\Documents\VTune\Logs\result_ah_with_stacks
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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-15176-boxer.sc' file
  vtune: Executing actions 25 % Loading 'systemcollector-15176-boxer.sc' file
  vtune: Executing actions 25 % Loading '3928.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 `e2f68.sys'
  vtune: Executing actions 39 % Resolving information for `tcpip.sys'
  vtune: Executing actions 39 % Resolving information for `WdFilter.sys'
  vtune: Executing actions 39 % Resolving information for `msvcrt.dll'
  vtune: Executing actions 39 % Resolving information for `CLASSPNP.SYS'
  vtune: Executing actions 39 % Resolving information for `cng.sys'
  vtune: Executing actions 39 % Resolving information for `vtss.sys'
  vtune: Executing actions 39 % Resolving information for `nvlddmkm.sys'
  vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\drivers\e2f68.sys'.
  
  vtune: Executing actions 39 % Resolving information for `HDAudBus.sys'
  vtune: Executing actions 39 % Resolving information for `ndis.sys'
  vtune: Executing actions 40 % Resolving information for `ndis.sys'
  vtune: Executing actions 40 % Resolving information for `ucrtbase.dll'
  vtune: Executing actions 40 % Resolving information for `NETIO.SYS'
  vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\system32\drivers\vtss.sys'.
  
  vtune: Executing actions 40 % Resolving information for `dxgmms2.sys'
  vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.sys'.
  
  vtune: Executing actions 40 % Resolving information for `ntoskrnl.exe'
  vtune: Executing actions 40 % Resolving information for `iorate.sys'
  vtune: Executing actions 41 % Resolving information for `iorate.sys'
  vtune: Executing actions 41 % Resolving information for `storport.sys'
  vtune: Executing actions 41 % Resolving information for `Netwtw10.sys'
  vtune: Executing actions 41 % Resolving information for `ntdll.dll'
  vtune: Executing actions 41 % Resolving information for `Wdf01000.sys'
  vtune: Executing actions 42 % Resolving information for `Wdf01000.sys'
  vtune: Executing actions 42 % Resolving information for `volsnap.sys'
  vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\system32\drivers\wd\WdFilter.sys'.
  
  vtune: Executing actions 42 % Resolving information for `kernel32.dll'
  vtune: Executing actions 43 % Resolving information for `kernel32.dll'
  vtune: Executing actions 43 % Resolving information for `secnvme.sys'
  vtune: Executing actions 43 % Resolving information for `intelppm.sys'
  vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\drivers\Netwtw10.sys'.
  
  vtune: Executing actions 43 % Resolving information for `partmgr.sys'
  vtune: Executing actions 43 % Resolving information for `matrix.exe'
  vtune: Executing actions 43 % Resolving information for `KernelBase.dll'
  vtune: Executing actions 44 % Resolving information for `KernelBase.dll'
  vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\drivers\secnvme.sys'.
  
  vtune: Executing actions 45 % Resolving information for `KernelBase.dll'
  vtune: Executing actions 45 % Resolving bottom user stack information
  vtune: Executing actions 46 % Resolving bottom user stack information
  vtune: Executing actions 47 % Resolving bottom user stack information
  vtune: Executing actions 47 % Resolving thread name information
  vtune: Executing actions 48 % Resolving thread name information
  vtune: Executing actions 48 % Resolving call target names for dynamic code
  vtune: Executing actions 50 % Resolving call target names for dynamic code
  vtune: Executing actions 50 % Resolving interrupt name information
  vtune: Executing actions 53 % Resolving interrupt name information
  vtune: Executing actions 53 % Processing profile metrics and debug information
  vtune: Executing actions 56 % Processing profile metrics and debug information
  vtune: Executing actions 57 % Processing profile metrics and debug information
  vtune: Executing actions 58 % Processing profile metrics and debug information
  vtune: Executing actions 60 % Processing profile metrics and debug information
  vtune: Executing actions 60 % Setting data model parameters
  vtune: Executing actions 60 % Precomputing frequently used data
  vtune: Executing actions 60 % Precomputing frequently used data
  vtune: Executing actions 62 % Precomputing frequently used data
  vtune: Executing actions 63 % Precomputing frequently used data
  vtune: Executing actions 64 % Precomputing frequently used data
  vtune: Executing actions 65 % Precomputing frequently used data
  vtune: Executing actions 66 % Precomputing frequently used data
  vtune: Executing actions 67 % Precomputing frequently used data
  vtune: Executing actions 68 % Precomputing frequently used data
  vtune: Executing actions 69 % Precomputing frequently used data
  vtune: Executing actions 71 % Precomputing frequently used data
  vtune: Executing actions 72 % Precomputing frequently used data
  vtune: Executing actions 72 % Updating precomputed scalar metrics
  vtune: Executing actions 75 % Updating precomputed scalar metrics
  vtune: Executing actions 75 % Discarding redundant overtime data
  vtune: Executing actions 78 % Discarding redundant overtime data
  vtune: Executing actions 78 % Saving the result
  vtune: Executing actions 82 % Saving the result
  vtune: Executing actions 85 % Saving the result
  vtune: Executing actions 99 % Saving the result
  vtune: Executing actions 100 % Saving the result
  vtune: Executing actions 100 % done

Finalization: Ok
--------------------------------------------------------------------------------
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\users\kimel\Documents\VTune\Logs\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,134.540950,134.540950,0.0,0.0,209373869965,10.9,10.9,2.946543,matrix.exe,multiply1,multiply.c,0x1400017f0
  ThreadFunction,1.596165,1.596165,0.0,0.0,544003887,83.0,83.0,2.546381,matrix.exe,ThreadFunction,thrmodel.c,0x140001910
  KiDispatchInterrupt,0.645653,0.645653,0.0,0.0,278200507,61.2,61.2,1.948663,ntoskrnl.exe,KiDispatchInterrupt,[Unknown],0x14041dff0
  KiExecuteAllDpcs,0.303707,0.303707,0.0,0.0,140908986,69.2,69.2,2.606458,ntoskrnl.exe,KiExecuteAllDpcs,[Unknown],0x1402f3b40
  KiDpcInterruptBypass,0.128695,0.128695,0.0,0.0,52987280,59.3,59.3,1.861600,ntoskrnl.exe,KiDpcInterruptBypass,[Unknown],0x14041d850
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r C:\users\kimel\Documents\VTune\Logs\result_th -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe
Stdout:
  Addr of buf1 = 00000000007A9040
  Offs of buf1 = 00000000007A9180
  Addr of buf2 = 00000000027BC040
  Offs of buf2 = 00000000027BC1C0
  Addr of buf3 = 00000000047C5040
  Offs of buf3 = 00000000047C5100
  Addr of buf4 = 00000000067D9040
  Offs of buf4 = 00000000067D9140
  Threads #: 16 Win threads
  Matrix size: 2048
  Using multiply kernel: multiply1
  Execution time = 14.477 seconds
Stderr:
  vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\users\kimel\Documents\VTune\Logs\result_th -command stop.
  vtune: Collection stopped.
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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
--------------------------------------------------------------------------------
Running finalization...
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -finalize -r C:\users\kimel\Documents\VTune\Logs\result_th
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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-2976-boxer.sc' file
  vtune: Executing actions 25 % Loading 'systemcollector-2976-boxer.sc' file
  vtune: Executing actions 25 % Loading '4664.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 dangling locations
  vtune: Executing actions 39 % Resolving information for `matrix.exe'
  vtune: Executing actions 39 % Resolving information for `ntdll.dll'
  vtune: Executing actions 40 % Resolving information for `ntdll.dll'
  vtune: Executing actions 40 % Resolving information for `vcruntime140.dll'
  vtune: Executing actions 40 % Resolving information for `ucrtbase.dll'
  vtune: Executing actions 41 % Resolving information for `ucrtbase.dll'
  vtune: Executing actions 42 % Resolving information for `ucrtbase.dll'
  vtune: Executing actions 44 % Resolving information for `ucrtbase.dll'
  vtune: Executing actions 45 % Resolving information for `ucrtbase.dll'
  vtune: Executing actions 45 % Resolving bottom user stack information
  vtune: Executing actions 46 % Resolving bottom user stack information
  vtune: Executing actions 47 % Resolving bottom user stack information
  vtune: Executing actions 47 % Resolving thread name information
  vtune: Executing actions 48 % Resolving thread name information
  vtune: Executing actions 48 % Resolving call target names for dynamic code
  vtune: Executing actions 50 % Resolving call target names for dynamic code
  vtune: Executing actions 50 % Resolving interrupt name information
  vtune: Executing actions 53 % Resolving interrupt name information
  vtune: Executing actions 53 % Processing profile metrics and debug information
  vtune: Executing actions 56 % Processing profile metrics and debug information
  vtune: Executing actions 57 % Processing profile metrics and debug information
  vtune: Executing actions 58 % Processing profile metrics and debug information
  vtune: Executing actions 60 % Processing profile metrics and debug information
  vtune: Executing actions 62 % Processing profile metrics and debug information
  vtune: Executing actions 63 % Processing profile metrics and debug information
  vtune: Executing actions 63 % Setting data model parameters
  vtune: Executing actions 64 % Setting data model parameters
  vtune: Executing actions 64 % Precomputing frequently used data
  vtune: Executing actions 64 % Precomputing frequently used data
  vtune: Executing actions 66 % Precomputing frequently used data
  vtune: Executing actions 67 % Precomputing frequently used data
  vtune: Executing actions 68 % Precomputing frequently used data
  vtune: Executing actions 69 % Precomputing frequently used data
  vtune: Executing actions 70 % Precomputing frequently used data
  vtune: Executing actions 71 % Precomputing frequently used data
  vtune: Executing actions 73 % Precomputing frequently used data
  vtune: Executing actions 74 % Precomputing frequently used data
  vtune: Executing actions 76 % Precomputing frequently used data
  vtune: Executing actions 76 % Updating precomputed scalar metrics
  vtune: Executing actions 78 % Updating precomputed scalar metrics
  vtune: Executing actions 78 % Discarding redundant overtime data
  vtune: Executing actions 82 % Discarding redundant overtime data
  vtune: Executing actions 82 % Saving the result
  vtune: Executing actions 85 % Saving the result
  vtune: Executing actions 89 % Saving the result
  vtune: Executing actions 99 % Saving the result
  vtune: Executing actions 100 % Saving the result
  vtune: Executing actions 100 % done

Finalization: Ok
--------------------------------------------------------------------------------
Command line:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\users\kimel\Documents\VTune\Logs\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,149.415064,149.415064,0.0,0.0,8.147297,0.0,0.0,0.0,0.0,0.0,0.0,8.147297,0.000005,8.147292,0.0,0.0,0.0,16868,0,0,0,0,0,0,16868,1,16867,0,0,0,matrix.exe,multiply1,multiply.c,0x1400017f0
  [Outside any known module],2.089440,2.089440,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,[Unknown],[Outside any known module],[Unknown],0x0
  init_arr,0.041323,0.041323,0.0,0.0,0.000011,0.0,0.0,0.0,0.0,0.0,0.0,0.000011,0.0,0.000011,0.0,0.0,0.0,1,0,0,0,0,0,0,1,0,1,0,0,0,matrix.exe,init_arr,matrix.c,0x1400010a0
  ZwWaitForMultipleObjects,0.001007,0.001007,0.0,0.0,13.740462,0.573100,0.000487,0.572613,0.0,0.0,0.0,13.167362,0.000436,13.166926,0.0,0.0,0.0,17,15,0,15,0,0,0,2,0,2,0,0,0,ntdll.dll,ZwWaitForMultipleObjects,[Unknown],0x1800a4290
  LdrpInitialize,0.0,0.0,0.0,0.0,0.000105,0.0,0.0,0.0,0.0,0.0,0.0,0.000105,0.000105,0.0,0.0,0.0,0.0,2,0,0,0,0,0,0,2,2,0,0,0,0,ntdll.dll,LdrpInitialize,[Unknown],0x18007a8d8
Stderr:
  vtune: Using result path `C:\users\kimel\Documents\VTune\Logs\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
Exception: [WinError 2] The system cannot find the file specified
Checking DPC++ application as prerequisite for GPU analyses...
Checking sycl.dll library
Command line:
where.exe sycl.dll
Stderr:
  INFO: Could not find files for the given pattern(s).

Unable to find sycl.dll
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.


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: C:\users\kimel\Documents\VTune\Logs\log.txt