Intel(R) VTune(TM) Profiler Self Check Utility Copyright (C) 2009 Intel Corporation. All rights reserved. Build Number: 623516 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: false isL3MonitoringSupportedByCPU: false isTSXAvailable: false isPTAvailable: true isHTEnabled: true fpgaOnBoard: None omniPathOnBoard: None genArchOnBoard: 10 pciClassParts: tidValuesForIO: populatedIoParts: populatedIoUnits: populatedTidValuesForIO: isSGXAvailable: false Hypervisor: Microsoft Hv PerfmonVersion: 5 isMaxDRAMBandwidthMeasurementSupported: true preferedGpuAdapter: 0:0:2.0 gpuAdapterNameList: 0:0:2.0|Intel(R) UHD Graphics; gpuAdapterTileNameList: 0:0:2.0|Intel(R) UHD Graphics|0,; gpuOpenCLDeviceOrder: none isEHFIAvailable: false areGpuHardwareMetricsAvailableList: 0:0:2.0|true; gpuPlatformIndexList: 0:0:2.0|17; ETW: OK isGpuBusynessAvailable: yes isGpuBusynessDetailsAvailable: notAccessible isGpuWaitAvailable: no isEtwCLRSupported: yes isFtraceAvailable: isMdfEtwAvailable: false isCSwitchAvailable: yes isFunctionTracingAvailable: no isIowaitTracingAvailable: no isVSyncAvailable: na HypervisorType: Hyper-V isDeviceOrCredentialGuardEnabled: false isSEPDriverAvailable: true SEPDriverVersion: 5.33 isPAXDriverLoaded: true PAXDriverVersion: 1.0 platformType: 142 CPU_NAME: Intel(R) microarchitecture code named Tigerlake H PMU: tigerlake availablePmuTypes: core,imc,gt,power referenceFrequency: 2300000000 isPStateAvailable: true isVTSSPPDriverAvailable: true isNMIWatchDogTimerRunning: false isAOCLAvailable: false isTPSSAvailable: true isPytraceAvailable: true isGENDebugInfoAvailableList: 0:0:2.0|true; isGTPinCollectionAvailableList: 0:0:2.0|true; forceShowInlines: false isEnergyCollectionSupported: true isSocwatchDriverLoaded: true isCPUSupportedBySocwatch: true isCpuThrottlingAvailable: true isIPMWatchReady: true isNvdimmAvailable: false osCountersCollectorAvailability: restricted l0LoaderStatus: Ok l0DevicesAvailable: true l0VPUDevicesAvailable: false l0GPUDevicesAvailable: true 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.33 built on Mar 1 2022 17:57:13 SEP Driver Version: 5.33 (public) PAX Driver Version: 1.0 Platform type: 142 CPU name: Intel(R) microarchitecture code named Tigerlake H PMU: tigerlake Driver configs: Maskable Interrupt, MULTI PEBS OFF (tracepoints not accessible), OFFCORE OFF (by OS security), REGISTER CHECK ON Virtualization platform: Host VM on Hyper-V with VBS enabled 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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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 = 0000000000876040 Offs of buf1 = 0000000000876180 Addr of buf2 = 000000000288B040 Offs of buf2 = 000000000288B1C0 Addr of buf3 = 000000000489F040 Offs of buf3 = 000000000489F100 Addr of buf4 = 00000000068BA040 Offs of buf4 = 00000000068BA140 Threads #: 16 Win threads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 15.974 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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ps -command stop. vtune: Collection stopped. vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ps Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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-20784-Seahawk.sc' file vtune: Executing actions 25 % Loading 'systemcollector-20784-Seahawk.sc' file vtune: Executing actions 25 % Loading 'gen_metrics0_0_2_0_0.0.vtss' file vtune: Executing actions 25 % Loading 'C:\Users\edsan\AppData\Local\Temp\vtune- 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 64 % Processing profile metrics and debug information vtune: Executing actions 65 % Processing profile metrics and debug information vtune: Executing actions 67 % Processing profile metrics and debug information vtune: Executing actions 67 % Preparing output tree vtune: Executing actions 67 % Parsing columns in input tree vtune: Executing actions 67 % Creating top-level columns vtune: Executing actions 69 % Creating top-level columns vtune: Executing actions 69 % Creating top-level rows vtune: Executing actions 70 % Creating top-level rows vtune: Executing actions 70 % Preparing output tree vtune: Executing actions 70 % Parsing columns in input tree vtune: Executing actions 71 % Parsing columns in input tree vtune: Executing actions 71 % Creating top-level columns vtune: Executing actions 72 % Creating top-level columns vtune: Executing actions 72 % Creating top-level rows vtune: Executing actions 74 % Creating top-level rows vtune: Executing actions 74 % Preparing output tree vtune: Executing actions 74 % Parsing columns in input tree vtune: Executing actions 74 % Creating top-level columns vtune: Executing actions 76 % Creating top-level columns vtune: Executing actions 76 % Creating top-level rows vtune: Executing actions 77 % Creating top-level rows vtune: Executing actions 78 % Creating top-level rows vtune: Executing actions 78 % Preparing output tree vtune: Executing actions 78 % Parsing columns in input tree vtune: Executing actions 78 % Creating top-level columns vtune: Executing actions 79 % Creating top-level columns vtune: Executing actions 79 % Creating top-level rows vtune: Executing actions 81 % Creating top-level rows vtune: Executing actions 81 % Preparing output tree vtune: Executing actions 81 % Parsing columns in input tree vtune: Executing actions 81 % Creating top-level columns vtune: Executing actions 83 % Creating top-level columns vtune: Executing actions 83 % Creating top-level rows vtune: Executing actions 84 % Creating top-level rows vtune: Executing actions 85 % Creating top-level rows vtune: Executing actions 85 % Preparing output tree vtune: Executing actions 85 % Parsing columns in input tree vtune: Executing actions 85 % Creating top-level columns vtune: Executing actions 86 % Creating top-level columns vtune: Executing actions 86 % Creating top-level rows vtune: Executing actions 88 % Creating top-level rows vtune: Executing actions 89 % Creating top-level rows vtune: Executing actions 90 % Creating top-level rows vtune: Executing actions 91 % Creating top-level rows vtune: Executing actions 92 % Creating top-level rows vtune: Executing actions 92 % Preparing output tree vtune: Executing actions 92 % Parsing columns in input tree vtune: Executing actions 92 % Creating top-level columns vtune: Executing actions 93 % Creating top-level columns vtune: Executing actions 93 % Creating top-level rows vtune: Executing actions 95 % Creating top-level rows vtune: Executing actions 95 % Preparing output tree vtune: Executing actions 95 % Parsing columns in input tree vtune: Executing actions 96 % Parsing columns in input tree vtune: Executing actions 96 % Creating top-level columns vtune: Executing actions 97 % Creating top-level columns vtune: Executing actions 97 % Creating top-level rows vtune: Executing actions 98 % Creating top-level rows vtune: Executing actions 99 % Creating top-level rows vtune: Executing actions 99 % Setting data model parameters vtune: Executing actions 100 % Setting data model parameters vtune: Executing actions 100 % Precomputing frequently used data vtune: Executing actions 100 % Precomputing frequently used data vtune: Executing actions 100 % Updating precomputed scalar metrics vtune: Executing actions 100 % Discarding redundant overtime data 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 -R summary -r C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ps Stdout: Elapsed Time: 16.042s CPU IPC: 0.305 | The IPC may be too low. This could be caused by issues such as memory | stalls, instruction starvation, branch misprediction or long latency | instructions. Explore the other hardware-related metrics to identify | what is causing low IPC. | SP GFLOPS: 0.000 DP GFLOPS: 1.068 x87 GFLOPS: 0.000 Average CPU Frequency: 4.190 GHz GPU Time: 0.1% (0.008s) of Elapsed time | GPU utilization is low. Consider offloading more work to the GPU to | increase overall application performance. | Logical Core Utilization: 98.0% (15.688 out of 16) Physical Core Utilization: 98.8% (7.904 out of 8) Microarchitecture Usage: 11.8% of Pipeline Slots | You code efficiency on this platform is too low. | | Possible cause: memory stalls, instruction starvation, branch misprediction | or long latency instructions. | | Next steps: Run Microarchitecture Exploration analysis to identify the cause | of the low microarchitecture usage efficiency. | Retiring: 11.8% of Pipeline Slots Front-End Bound: 3.5% of Pipeline Slots Bad Speculation: 0.6% of Pipeline Slots Back-End Bound: 84.1% 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: 76.4% 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: 5.9% of Clockticks L2 Bound: 0.6% of Clockticks L3 Bound: 50.1% 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. | L3 Latency: 31.2% of Clockticks | This metric shows a fraction of cycles with demand load | accesses that hit the L3 cache under unloaded scenarios | (possibly L3 latency limited). Avoiding private cache misses | (i.e. L2 misses/L3 hits) will improve the latency, reduce | contention with sibling physical cores and increase | performance. Note the value of this node may overlap with its | siblings. | DRAM Bound: 27.4% 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: 29.4% 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: 61.1% of Clockticks | Issue: A significant fraction of cycles was stalled due to | the latency of the main memory (DRAM). | | Tips: Improve data accesses or interleave them with compute | using such possible techniques as data layout re-structuring | or software prefetches (through the compiler). | Store Bound: 0.0% of Clockticks Core Bound: 7.6% of Pipeline Slots Memory Bound: 76.4% 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: 56.6% of Clockticks | A significant proportion of cycles are being spent on data fetches from | caches. Check Memory Access analysis to see if accesses to L2 or L3 | caches are problematic and consider applying the same performance tuning | as you would for a cache-missing workload. This may include reducing the | data working set size, improving data access locality, blocking or | partitioning the working set to fit in the lower cache levels, or | exploiting hardware prefetchers. Consider using software prefetchers, but | note that they can interfere with normal loads, increase latency, and | increase pressure on the memory system. This metric includes coherence | penalties for shared data. Check Microarchitecture Exploration analysis | to see if contested accesses or data sharing are indicated as likely | issues. | DRAM Bound: 27.4% of Clockticks | The metric value is high. This indicates that a significant fraction of | cycles could be stalled on the main memory (DRAM) because of demand loads | or stores. | | The code is memory bandwidth bound, which means that there are a | significant fraction of cycles during which the bandwidth limits of the | main memory are being reached and the code could stall. Review the | Bandwidth Utilization Histogram to estimate the scale of the issue. | Improve data accesses to reduce cacheline transfers from/to memory using | these possible techniques: 1) consume all bytes of each cacheline before | it is evicted (for example, reorder structure elements and split non-hot | ones); 2) merge compute-limited and bandwidth-limited loops; 3) use NUMA | optimizations on a multi-socket system. | | The code is latency bound, which means that there are a significant | fraction of cycles during which the code could be stalled due to main | memory latency. Consider optimizing data layout or using software | prefetches through the compiler to improve cache reuse and to reduce the | data fetched from the main memory. | Average DRAM Bandwidth, GB/s: 7.438 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: 0.2% from SP FP 128-bit: 0.2% from SP FP 256-bit: 0.0% from SP FP 512-bit: 0.0% from SP FP Scalar: 99.8% from SP FP | A significant fraction of floating point arithmetic instructions | are scalar. This indicates that the code was not fully | vectorized. Use Intel Advisor to see possible reasons why the | code was not vectorized. | DP FLOPs: 5.5% of uOps Packed: 0.0% from DP FP 128-bit: 0.0% from DP FP 256-bit: 0.0% from DP FP 512-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.5% of uOps FP Arith/Mem Rd Instr. Ratio: 0.111 | The metric value is low. This can be a result of unaligned access to data | for vector operations. Use Intel Advisor to find possible data access | inefficiencies for vector operations. | FP Arith/Mem Wr Instr. Ratio: 0.978 GPU Active Time: 0.1% | GPU utilization is low. Consider offloading more work to the GPU to increase | overall application performance. | GPU Utilization when Busy: 3.8% | The percentage of time when the EUs were stalled or idle is high, which | has a negative impact on compute-bound applications. | EU State: 3.8% Active: 3.8% Stalled: 13.3% Idle: 82.9% | A significant portion of GPU time is spent idle. This is usually | caused by imbalance or thread scheduling problems. | Occupancy: 9.8% of peak value | Several factors including shared local memory, use of memory barriers, | and inefficient work scheduling can cause a low value of the occupancy | metric. | Collection and Platform Info Application Command Line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe Operating System: Microsoft Windows 10 Computer Name: Seahawk Result Size: 4.3 MB Collection start time: 20:57:53 08/04/2022 UTC Collection stop time: 20:58:09 08/04/2022 UTC Collector Type: Event-based sampling driver,Event-based counting driver CPU Name: Intel(R) microarchitecture code named Tigerlake H Frequency: 2.304 GHz Logical CPU Count: 16 Max DRAM Single-Package Bandwidth: 29.000 GB/s Cache Allocation Technology Level 2 capability: not detected Level 3 capability: not detected GPU Name: Intel(R) UHD Graphics Vendor: Intel Corporation Driver: 30.0.101.1003 EU Count: 32 Max EU Thread Count: 7 Max Core Frequency: 1.450 GHz L3 size: 2.0 MB LLC size: 25.2 MB 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 (76.4%). 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 . Alternatively, you may view the report in the csv format: vtune -report -format=csv. Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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 = 000000000607C040 Offs of buf1 = 000000000607C180 Addr of buf2 = 000000000808A040 Offs of buf2 = 000000000808A1C0 Addr of buf3 = 000000000A09A040 Offs of buf3 = 000000000A09A100 Addr of buf4 = 000000000C0A8040 Offs of buf4 = 000000000C0A8140 Threads #: 16 Win threads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 16.298 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_tpss -command stop. vtune: Collection stopped. vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_tpss Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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-15428-Seahawk.sc' file vtune: Executing actions 25 % Loading 'systemcollector-15428-Seahawk.sc' file vtune: Executing actions 25 % Loading '19576-25116.0.trace' file vtune: Executing actions 25 % Loading 'C:\Users\edsan\AppData\Local\Temp\vtune- vtune: Executing actions 25 % Updating precomputed scalar metrics vtune: Executing actions 28 % Updating precomputed scalar metrics vtune: Executing actions 28 % Processing profile metrics and debug information vtune: Executing actions 39 % Processing profile metrics and debug information vtune: Executing actions 39 % Setting data model parameters vtune: Executing actions 39 % Resolving module symbols vtune: Executing actions 39 % Resolving information for `matrix.exe' vtune: Executing actions 39 % Resolving information for `KERNELBASE.dll' vtune: Executing actions 39 % Resolving information for `tpsstool.dll' 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 `KERNEL32.DLL' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\KERNELBASE.dll'. vtune: Executing actions 41 % Resolving information for `KERNEL32.DLL' vtune: Warning: Cannot locate debugging information for file `C:\Windows\SYSTEM32\ntdll.dll'. vtune: Executing actions 42 % Resolving information for `KERNEL32.DLL' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\KERNEL32.DLL'. 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 `KERNEL32.DLL' vtune: Executing actions 45 % Resolving information for `KERNEL32.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 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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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,254.233694,254.233694,0.0,0.0,matrix.exe,multiply1,multiply.c,0x1400017f0 init_arr,0.044773,0.044773,0.0,0.0,matrix.exe,init_arr,matrix.c,0x1400010a0 WaitForMultipleObjects,0.016886,0.0,0.016886,0.0,KERNELBASE.dll,WaitForMultipleObjects,[Unknown],0x18004f8e0 Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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 = 00000000008E0040 Offs of buf1 = 00000000008E0180 Addr of buf2 = 00000000028F5040 Offs of buf2 = 00000000028F51C0 Addr of buf3 = 000000000490F040 Offs of buf3 = 000000000490F100 Addr of buf4 = 0000000006926040 Offs of buf4 = 0000000006926140 Threads #: 16 Win threads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 15.412 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ah -command stop. vtune: Collection stopped. vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ah Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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-9188-Seahawk.sc' file vtune: Executing actions 25 % Loading 'systemcollector-9188-Seahawk.sc' 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 call target names for dynamic code vtune: Executing actions 46 % Resolving call target names for dynamic code vtune: Executing actions 46 % 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 53 % Setting data model parameters vtune: Executing actions 53 % Precomputing frequently used data vtune: Executing actions 53 % Precomputing frequently used data vtune: Executing actions 65 % Precomputing frequently used data vtune: Executing actions 65 % Updating precomputed scalar metrics vtune: Executing actions 68 % Updating precomputed scalar metrics vtune: Executing actions 68 % Discarding redundant overtime data vtune: Executing actions 71 % Discarding redundant overtime data vtune: Executing actions 71 % Saving the result vtune: Executing actions 75 % Saving the result vtune: Executing actions 78 % 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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ah Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ah' vtune: Executing actions 0 % vtune: Executing actions 0 % done vtune: Error: 0x40000024 (No data) -- No data is collected. Possible reasons: - Workload is too small. No samples are collected. - The application environment is not specified correctly. - The executable file has been stripped so cannot be profiled with algorithm analysis types. See the Troubleshooting help topic for more details. Also consider checking the collection log for additional information. Report: Fail vtune: Error: 0x40000024 (No data) -- No data is collected. Possible reasons: - Workload is too small. No samples are collected. - The application environment is not specified correctly. - The executable file has been stripped so cannot be profiled with algorithm analysis types. See the Troubleshooting help topic for more details. Also consider checking the collection log for additional information. ================================================================================ HW event-based analysis check... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect uarch-exploration -r C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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 = 00000000009D5040 Offs of buf1 = 00000000009D5180 Addr of buf2 = 00000000029E0040 Offs of buf2 = 00000000029E01C0 Addr of buf3 = 00000000049F0040 Offs of buf3 = 00000000049F0100 Addr of buf4 = 0000000006A0F040 Offs of buf4 = 0000000006A0F140 Threads #: 16 Win threads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 14.337 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ge -command stop. vtune: Collection stopped. vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ge Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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-23944-Seahawk.sc' file vtune: Executing actions 25 % Loading 'systemcollector-23944-Seahawk.sc' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.tb7' file vtune: Executing actions 25 % Loading 'sep1f1c.20220408T165905.427222.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 dangling locations vtune: Executing actions 39 % Resolving information for `condrv.sys' vtune: Executing actions 39 % Resolving information for `partmgr.sys' vtune: Executing actions 39 % Resolving information for `storport.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\condrv.sys'. vtune: Executing actions 39 % Resolving information for `netio.sys' vtune: Executing actions 39 % Resolving information for `ntfs.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\partmgr.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\storport.sys'. vtune: Executing actions 39 % Resolving information for `netwtw10.sys' vtune: Executing actions 39 % Resolving information for `rt640x64.sys' vtune: Executing actions 39 % Resolving information for `winhvr.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\netio.sys'. vtune: Executing actions 39 % Resolving information for `ndis.sys' vtune: Executing actions 39 % Resolving information for `volmgr.sys' vtune: Executing actions 40 % Resolving information for `volmgr.sys' vtune: Executing actions 40 % Resolving information for `fvevol.sys' vtune: Executing actions 40 % Resolving information for `ntdll.dll' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ntfs.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\rt640x64.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 `vmbkmclr.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\winhvr.sys'. vtune: Executing actions 40 % Resolving information for `tcpip.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ndis.sys'. vtune: Executing actions 41 % Resolving information for `tcpip.sys' vtune: Executing actions 41 % Resolving information for `matrix.exe' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\volmgr.sys'. vtune: Executing actions 41 % Resolving information for `cng.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\ntdll.dll'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\fvevol.sys'. vtune: Executing actions 41 % Resolving information for `dxgmms2.sys' vtune: Executing actions 42 % Resolving information for `dxgmms2.sys' vtune: Executing actions 42 % Resolving information for `stornvme.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\dxgkrnl.sys'. vtune: Executing actions 42 % Resolving information for `igdkmdn64.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\vmbkmclr.sys'. vtune: Executing actions 42 % Resolving information for `sepdrv5.sys' vtune: Executing actions 42 % Resolving information for `ntoskrnl.exe' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\tcpip.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\cng.sys'. vtune: Executing actions 42 % Resolving information for `ucrtbase.dll' vtune: Executing actions 42 % Resolving information for `wdf01000.sys' vtune: Executing actions 43 % Resolving information for `wdf01000.sys' vtune: Executing actions 43 % Resolving information for `iorate.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\dxgmms2.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\stornvme.sys'. vtune: Executing actions 43 % Resolving information for `classpnp.sys' vtune: Executing actions 43 % Resolving information for `intelppm.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\sepdrv5.sys'. vtune: Executing actions 43 % Resolving information for `ndu.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\ntoskrnl.exe'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\driverstore\filerepository\iigd_dch.inf_amd64_1973c0a49e1f4f8c\igdkmdn64.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\ucrtbase.dll'. vtune: Executing actions 44 % Resolving information for `ndu.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\wdf01000.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\iorate.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\classpnp.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\intelppm.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ndu.sys'. vtune: Executing actions 45 % Resolving information for `ndu.sys' vtune: Executing actions 45 % Resolving information for `nvlddmkm.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\driverstore\filerepository\nvlt.inf_amd64_9bfed4a7b51c0204\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 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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ge Stdout: Function,CPU Time,Clockticks,Instructions Retired,CPI Rate,Retiring(%),Retiring:Light Operations(%),Retiring:Light Operations:FP Arithmetic(%),Retiring:Light Operations:FP Arithmetic:FP x87(%),Retiring:Light Operations:FP Arithmetic:FP Scalar(%),Retiring:Light Operations:FP Arithmetic:FP Vector(%),Retiring:Light Operations:Memory Operations(%),Retiring:Light Operations:Branch Instructions(%),Retiring:Light Operations:Nop Instructions(%),Retiring:Light Operations:Other(%),Retiring:Heavy Operations(%),Retiring:Heavy Operations:Microcode Sequencer(%),Retiring:Heavy Operations:Microcode Sequencer:Assists(%),Retiring:Heavy Operations:Microcode Sequencer:CISC(%),Front-End Bound(%),Front-End Bound:Front-End Latency(%),Front-End Bound:Front-End Latency:ICache Misses(%),Front-End Bound:Front-End Latency:ITLB Overhead(%),Front-End Bound:Front-End Latency:Branch Resteers(%),Front-End Bound:Front-End Latency:Branch Resteers:Mispredicts Resteers(%),Front-End Bound:Front-End Latency:Branch Resteers:Clears Resteers(%),Front-End Bound:Front-End Latency:Branch Resteers:Unknown Branches(%),Front-End Bound:Front-End Latency:DSB Switches(%),Front-End Bound:Front-End Latency:Length Changing Prefixes(%),Front-End Bound:Front-End Latency:MS Switches(%),Front-End Bound:Front-End Bandwidth(%),Front-End Bound:Front-End Bandwidth:Front-End Bandwidth MITE(%),Front-End Bound:Front-End Bandwidth:Front-End Bandwidth DSB(%),Front-End Bound:Front-End Bandwidth:Front-End Bandwidth LSD(%),Front-End Bound:Front-End Bandwidth:(Info) DSB Coverage(%),Front-End Bound:Front-End Bandwidth:(Info) LSD Coverage(%),Front-End Bound:Front-End Bandwidth:(Info) DSB Misses Cost(%),Bad Speculation(%),Bad Speculation:Branch Mispredict(%),Bad Speculation:Machine Clears(%),Back-End Bound(%),Back-End Bound:Memory Bound(%),Back-End Bound:Memory Bound:L1 Bound(%),Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead(%),Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead:Load STLB Hit(%),Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead:Load STLB Miss(%),Back-End Bound:Memory Bound:L1 Bound:Loads Blocked by Store Forwarding(%),Back-End Bound:Memory Bound:L1 Bound:Lock Latency(%),Back-End Bound:Memory Bound:L1 Bound:Split Loads(%),Back-End Bound:Memory Bound:L1 Bound:4K Aliasing(%),Back-End Bound:Memory Bound:L1 Bound:FB Full(%),Back-End Bound:Memory Bound:L2 Bound(%),Back-End Bound:Memory Bound:L3 Bound(%),Back-End Bound:Memory Bound:L3 Bound:L3 Latency(%),Back-End Bound:Memory Bound:L3 Bound:SQ Full(%),Back-End Bound:Memory Bound:DRAM Bound(%),Back-End Bound:Memory Bound:DRAM Bound:Memory Bandwidth(%),Back-End Bound:Memory Bound:DRAM Bound:Memory Latency(%),Back-End Bound:Memory Bound:Store Bound(%),Back-End Bound:Memory Bound:Store Bound:Store Latency(%),Back-End Bound:Memory Bound:Store Bound:Split Stores(%),Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead(%),Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead:Store STLB Hit(%),Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead:Store STLB Hit(%),Back-End Bound:Core Bound(%),Back-End Bound:Core Bound:Divider(%),Back-End Bound:Core Bound:Port Utilization(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Serializing Operations(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Serializing Operations:Slow Pause(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Mixing Vectors(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 1 Port Utilized(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 2 Ports Utilized(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 0(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 1(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 5(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 6(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Load Operation Utilization(%),Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Store Operation Utilization(%),Back-End Bound:Core Bound:Port Utilization:Vector Capacity Usage (FPU)(%),Average CPU Frequency,Module,Function (Full),Source File,Start Address multiply1,214.986178,900896200000,317949700000,2.833455,13.9,13.9,5.6,0.0,5.6,0.0,7.4,0.8,0.0,0.1,0.0,0.0,0.0,0.0,4.1,2.5,0.0,0.0,0.1,0.1,0.0,0.0,0.1,0.0,0.0,1.6,0.0,0.0,0.8,0.8,98.7,0.9,0.6,0.6,0.0,81.5,72.1,7.8,100.0,100.0,31.5,0.0,0.0,0.0,0.1,0.0,1.9,55.3,44.8,0.0,15.2,28.3,58.0,0.0,0.0,0.0,0.0,0.0,0.0,9.4,0.0,10.5,0.3,0.1,0.0,0.0,9.4,5.5,3.5,9.0,10.8,13.6,4.6,7.2,17.5,1.9,12.5,4190484288.310197,matrix.exe,multiply1,multiply.c,0x1400017f0 func@0x31400,0.394314,1474300000,50600000,29.136364,18.3,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,21.6,21.6,0.0,21.6,38.8,34.9,0.0,15.7,5.1,0.0,1.0,4.1,0.0,0.0,22.3,3.9,0.0,0.0,0.0,0.0,0.0,0.0,40.5,0.0,40.5,2.4,0.2,7.1,100.0,100.0,1.5,0.0,0.0,0.0,0.0,0.0,2.0,0.0,0.0,0.0,0.0,12.2,3.1,0.0,1.0,0.0,1.4,0.6,0.7,2.2,0.0,81.6,65.1,23.4,0.0,0.0,14.2,12.2,10.2,22.2,25.9,38.9,13.0,11.1,8.3,6.9,0.0,3738895043.863291,sepdrv5.sys,func@0x31400,[Unknown],0x31400 func@0x140418b30,0.267535,1129300000,163300000,6.915493,15.6,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,16.5,10.6,0.0,10.6,28.0,10.6,6.6,6.1,4.6,0.0,3.3,1.3,0.0,0.0,17.1,17.4,0.0,0.0,0.0,0.0,0.0,0.0,28.9,0.0,28.9,27.5,4.6,12.0,100.0,100.0,0.1,0.0,0.0,0.0,0.0,0.0,0.0,6.6,0.0,0.0,4.0,15.9,2.7,0.0,13.3,0.0,1.5,1.0,0.6,22.9,0.0,85.4,79.7,45.8,0.0,0.0,5.3,2.7,0.0,7.7,5.6,8.4,8.4,8.4,4.2,2.1,0.0,4221133020.246268,ntoskrnl.exe,func@0x140418b30,[Unknown],0x140418b30 func@0x140412970,0.166710,690000000,20700000,33.333333,15.7,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,21.3,21.3,0.0,21.3,55.1,22.5,1.1,0.4,4.3,0.0,4.3,0.0,0.0,0.0,20.2,32.6,2.7,0.0,0.0,0.0,0.0,32.6,23.6,0.0,23.6,5.6,0.9,13.0,100.0,100.0,2.0,0.0,0.0,0.0,0.0,0.0,0.0,2.2,0.0,0.0,0.0,15.2,2.2,0.0,15.2,0.0,0.5,0.0,0.5,4.7,0.0,77.5,71.7,15.9,0.0,0.0,4.3,8.7,0.0,13.6,0.0,16.3,10.9,27.2,5.4,1.4,0.0,4138920873.053892,ntoskrnl.exe,func@0x140412970,[Unknown],0x140412970 func@0x20868,0.093837,450800000,545100000,0.827004,21.7,14.0,0.0,0.0,0.0,0.0,1.5,1.1,0.0,11.4,7.7,5.0,0.0,5.0,25.0,5.4,3.3,26.6,0.0,0.0,0.0,0.0,0.3,0.0,9.0,19.6,7.2,0.0,0.0,0.0,0.0,39.2,53.3,0.0,53.3,0.0,0.0,6.7,100.0,100.0,32.3,0.0,0.0,0.0,0.0,0.0,0.0,36.6,0.0,0.0,0.0,6.7,23.3,0.0,26.6,0.0,8.7,7.6,1.1,0.0,0.0,38.0,36.6,1.0,0.0,0.0,0.0,6.7,13.3,18.1,14.5,21.7,14.5,21.7,14.5,12.7,0.0,4804083617.617022,sepdrv5.sys,func@0x20868,[Unknown],0x20868 Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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 = 000000000097B040 Offs of buf1 = 000000000097B180 Addr of buf2 = 000000000298F040 Offs of buf2 = 000000000298F1C0 Addr of buf3 = 00000000049A8040 Offs of buf3 = 00000000049A8100 Addr of buf4 = 00000000069B8040 Offs of buf4 = 00000000069B8140 Threads #: 16 Win threads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 14.713 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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ma -command stop. vtune: Collection stopped. vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ma Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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-22796-Seahawk.sc' file vtune: Executing actions 25 % Loading 'systemcollector-22796-Seahawk.sc' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.tb7' file vtune: Executing actions 25 % Loading 'sep6338.20220408T165945.886317.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 `ndu.sys' vtune: Executing actions 39 % Resolving information for `classpnp.sys' vtune: Executing actions 39 % Resolving information for `wdf01000.sys' vtune: Executing actions 39 % Resolving information for `dxgmms2.sys' vtune: Executing actions 39 % Resolving information for `ntfs.sys' vtune: Executing actions 39 % Resolving information for `partmgr.sys' vtune: Executing actions 39 % Resolving information for `tcpip.sys' vtune: Executing actions 39 % Resolving information for `vtss.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ndu.sys'. vtune: Executing actions 39 % Resolving information for `vmbkmclr.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\classpnp.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\dxgmms2.sys'. vtune: Executing actions 39 % Resolving information for `netio.sys' vtune: Executing actions 39 % Resolving information for `nvlddmkm.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ntfs.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\wdf01000.sys'. vtune: Executing actions 39 % Resolving information for `cng.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\partmgr.sys'. vtune: Executing actions 40 % Resolving information for `cng.sys' vtune: Executing actions 40 % Resolving information for `vwififlt.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\tcpip.sys'. vtune: Executing actions 40 % Resolving information for `dxgkrnl.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\vtss.sys'. vtune: Executing actions 40 % Resolving information for `wpprecorder.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\vmbkmclr.sys'. vtune: Executing actions 40 % Resolving information for `sepdrv5.sys' vtune: Executing actions 40 % Resolving information for `matrix.exe' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\netio.sys'. vtune: Executing actions 40 % Resolving information for `watchdog.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\cng.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\vwififlt.sys'. vtune: Executing actions 41 % Resolving information for `watchdog.sys' vtune: Executing actions 41 % Resolving information for `wdfilter.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\dxgkrnl.sys'. vtune: Executing actions 41 % Resolving information for `ndis.sys' vtune: Executing actions 41 % Resolving information for `ntoskrnl.exe' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\driverstore\filerepository\nvlt.inf_amd64_9bfed4a7b51c0204\nvlddmkm.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\wpprecorder.sys'. vtune: Executing actions 41 % Resolving information for `intelppm.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\sepdrv5.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\watchdog.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\wd\wdfilter.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\intelppm.sys'. vtune: Executing actions 41 % Resolving information for `kernelbase.dll' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ndis.sys'. vtune: Executing actions 42 % Resolving information for `kernelbase.dll' vtune: Executing actions 42 % Resolving information for `volsnap.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\ntoskrnl.exe'. vtune: Executing actions 42 % Resolving information for `netwtw10.sys' vtune: Executing actions 42 % Resolving information for `storport.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\kernelbase.dll'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\volsnap.sys'. vtune: Executing actions 42 % Resolving information for dangling locations 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\drivers\storport.sys'. vtune: Executing actions 42 % Resolving information for `igdkmdn64.sys' vtune: Executing actions 42 % Resolving information for `winhvr.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\winhvr.sys'. vtune: Executing actions 43 % Resolving information for `winhvr.sys' vtune: Executing actions 43 % Resolving information for `condrv.sys' vtune: Executing actions 43 % Resolving information for `ftsvnic.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\driverstore\filerepository\iigd_dch.inf_amd64_1973c0a49e1f4f8c\igdkmdn64.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\condrv.sys'. vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ftsvnic.sys'. vtune: Executing actions 43 % Resolving information for `nwifi.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\nwifi.sys'. vtune: Executing actions 43 % Resolving information for `rt640x64.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\rt640x64.sys'. vtune: Executing actions 43 % Resolving information for `fltmgr.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\fltmgr.sys'. vtune: Executing actions 44 % Resolving information for `fltmgr.sys' vtune: Executing actions 44 % Resolving information for `ntdll.dll' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\ntdll.dll'. vtune: Executing actions 44 % Resolving information for `vmbusr.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\vmbusr.sys'. vtune: Executing actions 44 % Resolving information for `stornvme.sys' vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\stornvme.sys'. vtune: Executing actions 45 % Resolving information for `stornvme.sys' vtune: Executing actions 46 % Resolving information for `stornvme.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 79 % Updating precomputed scalar metrics vtune: Executing actions 82 % Updating precomputed scalar metrics vtune: Executing actions 82 % Discarding redundant overtime data vtune: Executing actions 85 % Discarding redundant overtime data vtune: Executing actions 85 % Saving the result vtune: Executing actions 89 % Saving the result vtune: Executing actions 92 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok -------------------------------------------------------------------------------- Command line: 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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ma Stdout: Function,CPU Time,Memory Bound(%),Memory Bound:L1 Bound(%),Memory Bound:L2 Bound(%),Memory Bound:L3 Bound(%),Memory Bound:DRAM Bound(%),Memory Bound:Store Bound(%),Loads,Stores,LLC Miss Count,Average Latency (cycles),Module,Function (Full),Source File,Start Address multiply1,217.873159,70.7,8.3,0.8,54.5,15.1,0.0,164756242539,18289448667,1012925250,38.872657,matrix.exe,multiply1,multiply.c,0x1400017f0 func@0x31400,0.533073,2.3,13.5,6.8,0.4,0.0,0.0,14400432,0,0,0.0,sepdrv5.sys,func@0x31400,[Unknown],0x31400 func@0x140418b30,0.409288,9.2,26.1,4.2,1.2,2.4,0.0,291608748,94502835,0,9.356322,ntoskrnl.exe,func@0x140418b30,[Unknown],0x140418b30 func@0x140412970,0.271528,1.3,12.7,6.4,0.0,0.8,0.0,9900297,0,0,0.933333,ntoskrnl.exe,func@0x140412970,[Unknown],0x140412970 func@0x20868,0.144748,30.5,30.8,,44.7,,0.0,250207506,342910287,0,15.090909,sepdrv5.sys,func@0x20868,[Unknown],0x20868 Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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 = 000000000099D040 Offs of buf1 = 000000000099D180 Addr of buf2 = 00000000029A3040 Offs of buf2 = 00000000029A31C0 Addr of buf3 = 00000000049B0040 Offs of buf3 = 00000000049B0100 Addr of buf4 = 00000000069C5040 Offs of buf4 = 00000000069C5140 Threads #: 16 Win threads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 25.130 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ah_with_stacks -command stop. vtune: Collection stopped. vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ah_with_stacks Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_ah_with_stacks' vtune: Executing actions 0 % vtune: Warning: The result contains a lot of raw data. Finalization may take a long time to complete. 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-21832-Seahawk.sc' file vtune: Executing actions 25 % Loading 'systemcollector-21832-Seahawk.sc' file vtune: Executing actions 25 % Loading '14736.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 `partmgr.sys' vtune: Executing actions 39 % Resolving information for `dxgkrnl.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\partmgr.sys'. vtune: Executing actions 39 % Resolving information for `Wdf01000.sys' vtune: Executing actions 39 % Resolving information for `Ntfs.sys' vtune: Executing actions 39 % Resolving information for `ndis.sys' 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 `rt640x64.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\dxgkrnl.sys'. vtune: Executing actions 39 % Resolving information for `igdkmdn64.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\system32\drivers\Wdf01000.sys'. vtune: Executing actions 39 % Resolving information for `Ndu.sys' vtune: Executing actions 39 % Resolving information for `ntoskrnl.exe' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\Drivers\Ntfs.sys'. vtune: Executing actions 39 % Resolving information for `winfsp-x64.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\system32\drivers\ndis.sys'. vtune: Executing actions 40 % Resolving information for `winfsp-x64.sys' vtune: Executing actions 40 % Resolving information for `Netwtw10.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\ucrtbase.dll'. vtune: Executing actions 40 % Resolving information for `vcruntime140.dll' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\rt640x64.sys'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\KernelBase.dll'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\system32\drivers\Ndu.sys'. vtune: Executing actions 40 % Resolving information for `matrix.exe' vtune: Executing actions 40 % Resolving information for `vtss.sys' vtune: Executing actions 40 % Resolving information for `CLASSPNP.SYS' vtune: Warning: Cannot locate debugging information for file `C:\Windows\system32\ntoskrnl.exe'. vtune: Warning: Cannot locate debugging information for file `C:\Program Files (x86)\WinFsp\bin\winfsp-x64.sys'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_1973c0a49e1f4f8c\igdkmdn64.sys'. vtune: Executing actions 41 % Resolving information for `CLASSPNP.SYS' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\Netwtw10.sys'. vtune: Executing actions 41 % Resolving information for `WppRecorder.sys' vtune: Finalization may slow down when loading files from the symbol server specified in the project properties. vtune: Warning: Cannot locate debugging information for file `C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\vcruntime140.dll'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\system32\drivers\vtss.sys'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\CLASSPNP.SYS'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\Drivers\WppRecorder.sys'. vtune: Executing actions 41 % Resolving information for `intelppm.sys' vtune: Executing actions 41 % Resolving information for `winhvr.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\intelppm.sys'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\winhvr.sys'. vtune: Executing actions 41 % Resolving information for `USBXHCI.SYS' vtune: Executing actions 42 % Resolving information for `USBXHCI.SYS' vtune: Executing actions 42 % Resolving information for dangling locations vtune: Executing actions 42 % Resolving information for `nvlddmkm.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\USBXHCI.SYS'. vtune: Executing actions 42 % Resolving information for `msvcrt.dll' vtune: Executing actions 42 % Resolving information for `tcpip.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\msvcrt.dll'. vtune: Executing actions 42 % Resolving information for `NETIO.SYS' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\tcpip.sys'. vtune: Executing actions 43 % Resolving information for `NETIO.SYS' vtune: Executing actions 43 % Resolving information for `ntdll.dll' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_9bfed4a7b51c0204\nvlddmkm.sys'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\system32\drivers\NETIO.SYS'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\ntdll.dll'. vtune: Executing actions 43 % Resolving information for `dxgmms2.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\dxgmms2.sys'. vtune: Executing actions 43 % Resolving information for `cng.sys' vtune: Executing actions 43 % Resolving information for `wdiwifi.sys' vtune: Executing actions 43 % Resolving information for `kernel32.dll' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\cng.sys'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\system32\DRIVERS\wdiwifi.sys'. vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\kernel32.dll'. vtune: Executing actions 44 % Resolving information for `kernel32.dll' vtune: Executing actions 44 % Resolving information for `storport.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\drivers\storport.sys'. vtune: Executing actions 44 % Resolving information for `WdFilter.sys' vtune: Warning: Cannot locate debugging information for file `C:\Windows\system32\drivers\wd\WdFilter.sys'. vtune: Executing actions 45 % Resolving information for `WdFilter.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 69 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 72 % Updating precomputed scalar metrics vtune: Executing actions 75 % Updating precomputed scalar metrics vtune: Executing actions 75 % Discarding redundant overtime data vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 78 % Saving the result vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok vtune: Warning: The result contains a lot of raw data. Finalization may take a long time to complete. -------------------------------------------------------------------------------- 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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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,265.417762,265.417762,0.0,0.0,315970294108,11.8,11.8,3.639008,matrix.exe,multiply1,multiply.c,0x1400017f0 ThreadFunction,7.538935,7.538935,0.0,0.0,2581732997,76.6,76.6,3.497968,matrix.exe,ThreadFunction,thrmodel.c,0x140001910 [ntoskrnl.exe],2.905679,2.905679,0.0,0.0,1179340684,49.0,49.0,3.049127,ntoskrnl.exe,[ntoskrnl.exe],[Unknown],0x0 func@0x140244350,0.550704,0.550704,0.0,0.0,220239969,49.0,49.0,3.547620,ntoskrnl.exe,func@0x140244350,[Unknown],0x140244350 _chkstk,0.207387,0.207387,0.0,0.0,87040240,32.5,32.5,2.884934,ntoskrnl.exe,_chkstk,[Unknown],0x14041fcc0 Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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 = 00000000007D3040 Offs of buf1 = 00000000007D3180 Addr of buf2 = 00000000027E9040 Offs of buf2 = 00000000027E91C0 Addr of buf3 = 00000000047F9040 Offs of buf3 = 00000000047F9100 Addr of buf4 = 0000000006805040 Offs of buf4 = 0000000006805140 Threads #: 16 Win threads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 20.729 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_th -command stop. vtune: Collection stopped. vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\result_th Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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-23964-Seahawk.sc' file vtune: Executing actions 25 % Loading 'systemcollector-23964-Seahawk.sc' file vtune: Executing actions 25 % Loading '19424.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 `ntdll.dll' vtune: Executing actions 39 % Resolving information for `matrix.exe' vtune: Executing actions 41 % Resolving information for `matrix.exe' vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\ntdll.dll'. vtune: Executing actions 43 % 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 46 % Resolving thread name information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 48 % Resolving call target names for dynamic code vtune: Executing actions 49 % Resolving call target names for dynamic code vtune: Executing actions 49 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 62 % Processing profile metrics and debug information vtune: Executing actions 63 % Processing profile metrics and debug information vtune: Executing actions 63 % Setting data model parameters vtune: Executing actions 64 % Setting data model parameters vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 64 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 67 % Precomputing frequently used data vtune: Executing actions 68 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 70 % Precomputing frequently used data vtune: Executing actions 71 % Precomputing frequently used data vtune: Executing actions 73 % Precomputing frequently used data vtune: Executing actions 74 % Precomputing frequently used data vtune: Executing actions 76 % Precomputing frequently used data vtune: Executing actions 76 % Updating precomputed scalar metrics vtune: Executing actions 78 % Updating precomputed scalar metrics vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 82 % Discarding redundant overtime data vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 89 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok -------------------------------------------------------------------------------- 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\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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,255.313597,255.313597,0.0,0.0,16.456100,0.0,0.0,0.0,0.0,0.0,0.0,16.456100,0.0,11.429283,5.026817,0.0,0.0,66595,0,0,0,0,0,0,66595,0,18210,48385,0,0,matrix.exe,multiply1,multiply.c,0x1400017f0 [Outside any known module],5.677414,5.677414,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,[Unknown],[Outside any known module],[Unknown],0x0 init_arr,0.047016,0.047016,0.0,0.0,,,,,,,,,,,,,,,,,,,,,,,,,,,matrix.exe,init_arr,matrix.c,0x1400010a0 LdrInitializeThunk,0.0,0.0,0.0,0.0,0.009665,0.0,0.0,0.0,0.0,0.0,0.0,0.009665,0.000559,0.003175,0.005930,0.0,0.0,5,0,0,0,0,0,0,5,1,3,1,0,0,ntdll.dll,LdrInitializeThunk,[Unknown],0x18007a8b0 NtConnectPort,0.0,0.0,0.0,0.0,0.000121,0.0,0.0,0.0,0.0,0.0,0.0,0.000121,0.000121,0.0,0.0,0.0,0.0,1,0,0,0,0,0,0,1,1,0,0,0,0,ntdll.dll,NtConnectPort,[Unknown],0x1800a4b70 Stderr: vtune: Using result path `C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\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 check observed a product failure on your system. Review errors in the output above to fix a problem or contact Intel technical support. The system is ready for the following analyses: * Performance Snapshot * Hotspots and Threading with user-mode sampling * 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: * Hotspots with HW event-based sampling, HPC Performance Characterization, etc. * GPU Compute/Media Hotspots (characterization mode) * GPU Compute/Media Hotspots (source analysis mode) Log location: C:\Users\edsan\AppData\Local\Temp\vtune-tmp-edsan\self-checker-2022.04.08_16.57.44\log.txt