Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 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\2022.2.0\bin64\amplxe-runss.exe --context-value-list
- Stdout:
- targetOS: Windows
- OS: Windows
- OSBuildNumber: 22000
- OSBitness: 64
- AdministratorPrivileges: true
- isPtraceScopeLimited: false
- isCATSupportedByCPU: 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 770;
- gpuAdapterTileNameList: 0:0:2.0|Intel(R) UHD Graphics 770|0,;
- gpuOpenCLDeviceOrder: none
- isEHFIAvailable: true
- 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: 145
- CPU_NAME: Intel(R) microarchitecture code named Alderlake-S
- PMU: alderlake
- availablePmuTypes: bigcore,smallcore,imc,power
- referenceFrequency: 3187000000
- 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: false
- isCpuThrottlingAvailable: false
- isIPMWatchReady: true
- isNvdimmAvailable: false
- osCountersCollectorAvailability: available
- 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\2022.2.0\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: 145
- CPU name: Intel(R) microarchitecture code named Alderlake-S
- PMU: alderlake
- 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\2022.2.0\bin64\vtune.exe -collect performance-snapshot -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ps -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\matrix.exe
- Stdout:
- Addr of buf1 = 00000000009D7040
- Offs of buf1 = 00000000009D7180
- Addr of buf2 = 00000000029E3040
- Offs of buf2 = 00000000029E31C0
- Addr of buf3 = 00000000049F2040
- Offs of buf3 = 00000000049F2100
- Addr of buf4 = 0000000006A04040
- Offs of buf4 = 0000000006A04140
- Threads #: 16 Win threads
- Matrix size: 2048
- Using multiply kernel: multiply1
- Execution time = 7.630 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\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ps -command stop.
- vtune: Collection stopped.
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -finalize -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ps
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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-5920-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'systemcollector-5920-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'gen_metrics0_0_2_0_0.0.vtss' file
- vtune: Executing actions 25 % Loading 'emon.0.bwhist' file
- vtune: Executing actions 25 % Loading 'C:\Users\EMELRA~1\AppData\Local\Temp\vtu
- 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\2022.2.0\bin64\vtune.exe -R summary -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ps
- Stdout:
- Elapsed Time: 7.693s
- CPU
- IPC: 0.585
- | The IPC may be too low. This could be caused by issues such as memory
- | stalls, instruction starvation, branch misprediction or long latency
- | instructions. Explore the other hardware-related metrics to identify
- | what is causing low IPC.
- |
- P-Core: 0.574
- | The IPC may be too low. This could be caused by issues such as
- | memory stalls, instruction starvation, branch misprediction or
- | long latency instructions. Explore the other hardware-related
- | metrics to identify what is causing low IPC.
- |
- E-Core: 0.614
- | 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.189
- DP GFLOPS: 1.755
- x87 GFLOPS: 0.000
- Average CPU Frequency: 4.503 GHz
- GPU
- Time: 0.0% (0s) of Elapsed time
- | GPU utilization is low. Consider offloading more work to the GPU to
- | increase overall application performance.
- |
- Logical Core Utilization: 72.2% (17.323 out of 24)
- | The metric value is low, which may signal a poor logical CPU cores
- | utilization. Consider improving physical core utilization as the first step
- | and then look at opportunities to utilize logical cores, which in some cases
- | can improve processor throughput and overall performance of multi-threaded
- | applications.
- |
- Physical Core Utilization: 70.5% (11.284 out of 16)
- | The metric value is low, which may signal a poor physical CPU cores
- | utilization caused by:
- | - load imbalance
- | - threading runtime overhead
- | - contended synchronization
- | - thread/process underutilization
- | - incorrect affinity that utilizes logical cores instead of physical
- | cores
- | Run the HPC Performance Characterization analysis to estimate the
- | efficiency of MPI and OpenMP parallelism or run the Locks and Waits
- | analysis to identify parallel bottlenecks for other parallel runtimes.
- |
- Microarchitecture Usage
- P-Core
- Retiring
- Front-End Bound
- Bad Speculation
- Back-End Bound: 0.0% of Pipeline Slots
- Memory Bound: 0.0% of Pipeline Slots
- L1 Bound: 1.3% of Clockticks
- L2 Bound: 0.5% of Clockticks
- L3 Bound: 28.8% of Clockticks
- DRAM Bound: 45.3% of Clockticks
- Memory Bandwidth: 0.0% of Clockticks
- Memory Latency: 0.0% of Clockticks
- Core Bound: 0.0% of Pipeline Slots
- E-Core
- Retiring: 13.2% of Pipeline Slots
- Front-End Bound: 8.3% of Pipeline Slots
- Bad Speculation: 6.9% of Pipeline Slots
- Back-End Bound: 71.3% of Pipeline Slots
- | A significant portion of pipeline slots are remaining empty. When
- | operations take too long in the back-end, they introduce bubbles in
- | the pipeline that ultimately cause fewer pipeline slots containing
- | useful work to be retired per cycle than the machine is capable to
- | support. This opportunity cost results in slower execution. Long-
- | latency operations like divides and memory operations can cause this,
- | as can too many operations being directed to a single execution port
- | (for example, more multiply operations arriving in the back-end per
- | cycle than the execution unit can support).
- |
- Resource Bound: 71.3% of Pipeline Slots
- | Resource Bound
- |
- Alternative Back-End Bound: 71.3% of Pipeline Slots
- | A significant portion of pipeline slots are remaining empty. When
- | operations take too long in the back-end, they introduce bubbles in
- | the pipeline that ultimately cause fewer pipeline slots containing
- | useful work to be retired per cycle than the machine is capable to
- | support. This opportunity cost results in slower execution. Long-
- | latency operations like divides and memory operations can cause this,
- | as can too many operations being directed to a single execution port
- | (for example, more multiply operations arriving in the back-end per
- | cycle than the execution unit can support).
- |
- Core Bound: 24.4%
- | This metric represents how much Core non-memory issues were of a
- | bottleneck. Shortage in hardware compute resources, or
- | dependencies software's instructions are both categorized under
- | Core Bound. Hence it may indicate the machine ran out of an OOO
- | resources, certain execution units are overloaded or dependencies
- | in program's data- or instruction- flow are limiting the
- | performance (e.g. FP-chained long-latency arithmetic operations).
- |
- Memory Bound: 46.9%
- | The metric value is high. This can indicate that the significant
- | fraction of execution pipeline slots could be stalled due to
- | demand memory load and stores. Use Memory Access analysis to have
- | the metric breakdown by memory hierarchy, memory bandwidth
- | information, correlation by memory objects.
- |
- L2 Bound: 3.9%
- L3 Bound: 15.1%
- | This metric shows how often CPU was stalled on L3 cache, or
- | contended with a sibling Core. Avoiding cache misses (L2
- | misses/L3 hits) improves the latency and increases
- | performance.
- |
- DRAM Bound: 27.9%
- | This metric shows how often CPU was stalled on the main
- | memory (DRAM). Caching typically improves the latency and
- | increases performance.
- |
- Memory Bound: 0.0% of Pipeline Slots
- P-Core
- Memory Bound: 0.0% of Pipeline Slots
- Cache Bound: 30.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: 45.3% of Clockticks
- E-Core
- Memory Bound: 46.9%
- | The metric value is high. This can indicate that the significant
- | fraction of execution pipeline slots could be stalled due to demand
- | memory load and stores. Use Memory Access analysis to have the metric
- | breakdown by memory hierarchy, memory bandwidth information,
- | correlation by memory objects.
- |
- Cache Bound: 19.0% of Clockticks
- DRAM Bound: 27.9%
- | This metric shows how often CPU was stalled on the main memory
- | (DRAM). Caching typically improves the latency and increases
- | performance.
- |
- Vectorization: 1.5% of Packed FP Operations
- | A significant fraction of floating point arithmetic instructions are scalar.
- | This indicates that the code was not fully vectorized. Use Intel Advisor to
- | see possible reasons why the code was not vectorized.
- |
- Instruction Mix
- SP FLOPs: 0.1% of uOps
- Packed: 51.1% from SP FP
- 128-bit: 7.7% from SP FP
- | A significant fraction of floating point arithmetic vector
- | instructions is executed with a partial vector load. Make
- | sure you compile the code with the latest instruction set or
- | use Intel Advisor for vectorization help.
- |
- 256-bit: 43.4% from SP FP
- Scalar: 48.9% 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.3% from DP FP
- 128-bit: 0.3% from DP FP
- 256-bit: 0.0% from DP FP
- Scalar: 99.7% 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.4% of uOps
- GPU Active Time: 0.0%
- | GPU utilization is low. Consider offloading more work to the GPU to increase
- | overall application performance.
- |
- Collection and Platform Info
- Application Command Line: C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\matrix.exe
- Operating System: Microsoft Windows 10
- Computer Name: Desktop
- Result Size: 4.4 MB
- Collection start time: 15:12:10 16/04/2022 UTC
- Collection stop time: 15:12:17 16/04/2022 UTC
- Collector Type: Event-based sampling driver,Event-based counting driver
- CPU
- Name: Intel(R) microarchitecture code named Alderlake-S
- Frequency: 3.187 GHz
- Logical CPU Count: 24
- Max DRAM Single-Package Bandwidth: 67.000 GB/s
- Cache Allocation Technology
- Level 2 capability: not detected
- Level 3 capability: not detected
- GPU
- Name: Intel(R) UHD Graphics 770
- Vendor: Intel Corporation
- Driver: 30.0.101.1273
- EU Count: 32
- Max EU Thread Count: 7
- Max Core Frequency: 1.550 GHz
- L3 size: 2.0 MB
- LLC size: 31.5 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.
- HPC Performance Characterization: Vectorization (1.5%) 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.
- Threading: There is poor utilization of logical CPU cores (72.2%) in your application.
- | Use Threading to explore more opportunities to increase parallelism in
- | your application.
- If you want to skip descriptions of detected performance issues in the report,
- enter: vtune -report summary -report-knob show-issues=false -r <my_result_dir>.
- Alternatively, you may view the report in the csv format: vtune -report
- <report_name> -format=csv.
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -collect hotspots -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_tpss -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\matrix.exe
- Stdout:
- Addr of buf1 = 0000000006C39040
- Offs of buf1 = 0000000006C39180
- Addr of buf2 = 0000000008C4F040
- Offs of buf2 = 0000000008C4F1C0
- Addr of buf3 = 000000000AC60040
- Offs of buf3 = 000000000AC60100
- Addr of buf4 = 000000000CC7C040
- Offs of buf4 = 000000000CC7C140
- Threads #: 16 Win threads
- Matrix size: 2048
- Using multiply kernel: multiply1
- Execution time = 9.016 seconds
- Stderr:
- vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_tpss -command stop.
- vtune: Collection stopped.
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -finalize -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_tpss
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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-8640-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'systemcollector-8640-Desktop.sc' file
- vtune: Executing actions 25 % Loading '28880-16604.0.trace' file
- vtune: Executing actions 25 % Loading 'C:\Users\EMELRA~1\AppData\Local\Temp\vtu
- 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 `KERNEL32.DLL'
- vtune: Executing actions 39 % Resolving information for `KERNELBASE.dll'
- vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\KERNEL32.DLL'.
- vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\KERNELBASE.dll'.
- vtune: Executing actions 39 % Resolving information for `ntdll.dll'
- vtune: Executing actions 40 % Resolving information for `ntdll.dll'
- vtune: Executing actions 41 % Resolving information for `ntdll.dll'
- vtune: Executing actions 41 % Resolving information for `matrix.exe'
- vtune: Executing actions 41 % Resolving information for `ucrtbase.dll'
- vtune: Executing actions 41 % Resolving information for `tpsstool.dll'
- vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\ucrtbase.dll'.
- vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\SYSTEM32\ntdll.dll'.
- vtune: Executing actions 42 % Resolving information for `tpsstool.dll'
- vtune: Executing actions 43 % Resolving information for `tpsstool.dll'
- vtune: Warning: Cannot locate debugging information for file `C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\bin64\tpsstool.dll'.
- vtune: Executing actions 44 % Resolving information for `tpsstool.dll'
- vtune: Executing actions 45 % Resolving information for `tpsstool.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 100 % Saving the result
- vtune: Executing actions 100 % done
- Finalization: Ok
- --------------------------------------------------------------------------------
- Command line:
- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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,138.148181,138.148181,0.0,0.0,matrix.exe,multiply1,multiply.c,0x1400017f0
- init_arr,0.030568,0.030568,0.0,0.0,matrix.exe,init_arr,matrix.c,0x1400010a0
- WaitForMultipleObjects,0.017303,0.0,0.017303,0.0,KERNELBASE.dll,WaitForMultipleObjects,[Unknown],0x18004f8e0
- free_base,0.003697,0.003697,0.0,0.0,ucrtbase.dll,free_base,[Unknown],0x180012170
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -collect hotspots -knob sampling-mode=hw -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ah -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\matrix.exe
- Stdout:
- Addr of buf1 = 0000000000A67040
- Offs of buf1 = 0000000000A67180
- Addr of buf2 = 0000000002A7F040
- Offs of buf2 = 0000000002A7F1C0
- Addr of buf3 = 0000000004A93040
- Offs of buf3 = 0000000004A93100
- Addr of buf4 = 0000000006AA2040
- Offs of buf4 = 0000000006AA2140
- Threads #: 16 Win threads
- Matrix size: 2048
- Using multiply kernel: multiply1
- Execution time = 9.663 seconds
- Stderr:
- vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ah -command stop.
- vtune: Collection stopped.
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -finalize -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ah
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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-25364-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'systemcollector-25364-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.tb7' file
- vtune: Executing actions 25 % Loading 'sep5618.20220416T171242.996850.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 `fwpkclnt.sys'
- vtune: Executing actions 39 % Resolving information for `cng.sys'
- vtune: Executing actions 39 % Resolving information for `wdf01000.sys'
- vtune: Executing actions 39 % Resolving information for `usbaudio.sys'
- vtune: Executing actions 39 % Resolving information for `nvlddmkm.sys'
- vtune: Executing actions 39 % Resolving information for `hidbth.sys'
- vtune: Executing actions 39 % Resolving information for `usbxhci.sys'
- vtune: Executing actions 39 % Resolving information for `magicmouse.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\usbxhci.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\cng.sys'.
- vtune: Executing actions 39 % Resolving information for `tcpip.sys'
- vtune: Executing actions 39 % Resolving information for `ks.sys'
- vtune: Executing actions 39 % Resolving information for `bthport.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\wdf01000.sys'.
- vtune: Executing actions 40 % Resolving information for `bthport.sys'
- vtune: Executing actions 40 % Resolving information for `watchdog.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\fwpkclnt.sys'.
- vtune: Executing actions 40 % Resolving information for `ntoskrnl.exe'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\usbaudio.sys'.
- vtune: Executing actions 40 % Resolving information for `dxgkrnl.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\hidbth.sys'.
- vtune: Executing actions 41 % Resolving information for `dxgkrnl.sys'
- vtune: Executing actions 41 % Resolving information for `intelppm.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\tcpip.sys'.
- vtune: Executing actions 41 % Resolving information for `matrix.exe'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ks.sys'.
- vtune: Executing actions 41 % Resolving information for `mouhid.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\bthport.sys'.
- vtune: Executing actions 42 % Resolving information for `mouhid.sys'
- vtune: Executing actions 42 % Resolving information for `ucx01000.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.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\ntoskrnl.exe'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\dxgkrnl.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\mouhid.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ucx01000.sys'.
- vtune: Executing actions 42 % Resolving information for `wpprecorder.sys'
- vtune: Executing actions 42 % Resolving information for `hidclass.sys'
- vtune: Executing actions 43 % Resolving information for `hidclass.sys'
- vtune: Executing actions 43 % Resolving information for `dxgmms2.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\wpprecorder.sys'.
- vtune: Executing actions 43 % Resolving information for `hdaudbus.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\hidclass.sys'.
- vtune: Executing actions 44 % Resolving information for `hdaudbus.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\hdaudbus.sys'.
- vtune: Executing actions 45 % Resolving information for `hdaudbus.sys'
- vtune: Executing actions 45 % Resolving bottom user stack information
- vtune: Executing actions 46 % Resolving bottom user stack information
- vtune: Executing actions 47 % Resolving bottom user stack information
- vtune: Executing actions 47 % Resolving thread name information
- vtune: Executing actions 48 % Resolving thread name information
- vtune: Executing actions 48 % Resolving call target names for dynamic code
- vtune: Executing actions 50 % Resolving call target names for dynamic code
- vtune: Executing actions 50 % Resolving interrupt name information
- vtune: Executing actions 53 % Resolving interrupt name information
- vtune: Executing actions 53 % Processing profile metrics and debug information
- vtune: Executing actions 56 % Processing profile metrics and debug information
- vtune: Executing actions 57 % Processing profile metrics and debug information
- vtune: Executing actions 58 % Processing profile metrics and debug information
- vtune: Executing actions 60 % Processing profile metrics and debug information
- vtune: Executing actions 60 % Setting data model parameters
- vtune: Executing actions 60 % Precomputing frequently used data
- vtune: Executing actions 60 % Precomputing frequently used data
- vtune: Executing actions 62 % Precomputing frequently used data
- vtune: Executing actions 63 % Precomputing frequently used data
- vtune: Executing actions 64 % Precomputing frequently used data
- vtune: Executing actions 65 % Precomputing frequently used data
- vtune: Executing actions 66 % Precomputing frequently used data
- vtune: Executing actions 67 % Precomputing frequently used data
- vtune: Executing actions 68 % Precomputing frequently used data
- vtune: Executing actions 70 % Precomputing frequently used data
- vtune: Executing actions 71 % Precomputing frequently used data
- vtune: Executing actions 72 % Precomputing frequently used data
- vtune: Executing actions 72 % Updating precomputed scalar metrics
- vtune: Executing actions 75 % Updating precomputed scalar metrics
- vtune: Executing actions 75 % Discarding redundant overtime data
- vtune: Executing actions 78 % Discarding redundant overtime data
- vtune: Executing actions 78 % Saving the result
- vtune: Executing actions 82 % Saving the result
- vtune: Executing actions 85 % Saving the result
- vtune: Executing actions 100 % Saving the result
- vtune: Executing actions 100 % done
- Finalization: Ok
- --------------------------------------------------------------------------------
- Command line:
- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ah
- Stdout:
- Function,CPU Time,CPU Time:Effective Time,CPU Time:Spin Time,CPU Time:Overhead Time,Instructions Retired,Microarchitecture Usage(%),Microarchitecture Usage:Microarchitecture Usage(%),Microarchitecture Usage:CPI Rate,Module,Function (Full),Source File,Start Address
- multiply1,39.964524,39.964524,0.0,0.0,80525929000,10.9,10.9,1.835556,matrix.exe,multiply1,multiply.c,0x1400017f0
- func@0x1404184b0,0.035998,0.035998,0.0,0.0,22309000,5.1,5.1,7.428571,ntoskrnl.exe,func@0x1404184b0,[Unknown],0x1404184b0
- func@0x14041e750,0.028998,0.028998,0.0,0.0,0,9.6,9.6,,ntoskrnl.exe,func@0x14041e750,[Unknown],0x14041e750
- KeClockInterruptNotify,0.027998,0.027998,0.0,0.0,0,2.2,2.2,,ntoskrnl.exe,KeClockInterruptNotify,[Unknown],0x140252520
- func@0x14041da8a,0.026998,0.026998,0.0,0.0,9561000,5.2,5.2,13.666667,ntoskrnl.exe,func@0x14041da8a,[Unknown],0x14041da8a
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ah'
- vtune: Executing actions 0 %
- vtune: Executing actions 0 % Finalizing results
- vtune: Executing actions 50 % Finalizing results
- vtune: Executing actions 50 % Generating a report
- vtune: Executing actions 50 % Setting data model parameters
- vtune: Executing actions 75 % Setting data model parameters
- vtune: Executing actions 75 % Generating a report
- vtune: Executing actions 100 % Generating a report
- vtune: Executing actions 100 % done
- Report: Ok
- ================================================================================
- HW event-based analysis check...
- Command line:
- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\bin64\vtune.exe -collect uarch-exploration -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ge -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\matrix.exe
- Stdout:
- Addr of buf1 = 00000000009E1040
- Offs of buf1 = 00000000009E1180
- Addr of buf2 = 00000000029FC040
- Offs of buf2 = 00000000029FC1C0
- Addr of buf3 = 0000000004A0A040
- Offs of buf3 = 0000000004A0A100
- Addr of buf4 = 0000000006A1A040
- Offs of buf4 = 0000000006A1A140
- Threads #: 16 Win threads
- Matrix size: 2048
- Using multiply kernel: multiply1
- Execution time = 8.564 seconds
- Stderr:
- vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ge -command stop.
- vtune: Collection stopped.
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -finalize -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ge
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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-30340-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'systemcollector-30340-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.tb7' file
- vtune: Executing actions 25 % Loading 'sep3fd4.20220416T171301.974625.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 `ks.sys'
- vtune: Executing actions 39 % Resolving information for `dxgkrnl.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ks.sys'.
- vtune: Executing actions 39 % Resolving information for `usbaudio.sys'
- vtune: Executing actions 39 % Resolving information for `ntoskrnl.exe'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\dxgkrnl.sys'.
- vtune: Executing actions 39 % Resolving information for `wdf01000.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\usbaudio.sys'.
- vtune: Executing actions 39 % Resolving information for `nvlddmkm.sys'
- vtune: Executing actions 40 % Resolving information for `nvlddmkm.sys'
- vtune: Executing actions 40 % Resolving information for `intelppm.sys'
- vtune: Executing actions 40 % Resolving information for `matrix.exe'
- vtune: Executing actions 40 % Resolving information for `hidbth.sys'
- vtune: Executing actions 40 % Resolving information for `watchdog.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\ntoskrnl.exe'.
- vtune: Executing actions 40 % Resolving information for `hdaudbus.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\intelppm.sys'.
- vtune: Executing actions 40 % Resolving information for `usbxhci.sys'
- vtune: Executing actions 40 % Resolving information for `cng.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\hdaudbus.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\hidbth.sys'.
- vtune: Executing actions 41 % Resolving information for `cng.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\cng.sys'.
- vtune: Executing actions 41 % Resolving information for `usbhub3.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\usbxhci.sys'.
- vtune: Executing actions 41 % Resolving information for `hidclass.sys'
- vtune: Executing actions 42 % Resolving information for `hidclass.sys'
- vtune: Executing actions 42 % Resolving information for `bthport.sys'
- vtune: Executing actions 42 % Resolving information for `magicmouse.sys'
- vtune: Executing actions 42 % Resolving information for `wpprecorder.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\usbhub3.sys'.
- vtune: Executing actions 42 % Resolving information for `hidparse.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\hidclass.sys'.
- vtune: Executing actions 43 % Resolving information for `hidparse.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\bthport.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\wpprecorder.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\hidparse.sys'.
- vtune: Executing actions 43 % Resolving information for `dxgmms2.sys'
- vtune: Executing actions 44 % Resolving information for `dxgmms2.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\dxgmms2.sys'.
- vtune: Executing actions 45 % Resolving information for `dxgmms2.sys'
- vtune: Executing actions 45 % Resolving bottom user stack information
- vtune: Executing actions 46 % Resolving bottom user stack information
- vtune: Executing actions 47 % Resolving bottom user stack information
- vtune: Executing actions 47 % Resolving thread name information
- vtune: Executing actions 48 % Resolving thread name information
- vtune: Executing actions 48 % Resolving call target names for dynamic code
- vtune: Executing actions 50 % Resolving call target names for dynamic code
- vtune: Executing actions 50 % Resolving interrupt name information
- vtune: Executing actions 53 % Resolving interrupt name information
- vtune: Executing actions 53 % Processing profile metrics and debug information
- vtune: Executing actions 56 % Processing profile metrics and debug information
- vtune: Executing actions 57 % Processing profile metrics and debug information
- vtune: Executing actions 58 % Processing profile metrics and debug information
- vtune: Executing actions 60 % Processing profile metrics and debug information
- vtune: Executing actions 60 % Setting data model parameters
- vtune: Executing actions 60 % Precomputing frequently used data
- vtune: Executing actions 60 % Precomputing frequently used data
- vtune: Executing actions 62 % Precomputing frequently used data
- vtune: Executing actions 63 % Precomputing frequently used data
- vtune: Executing actions 64 % Precomputing frequently used data
- vtune: Executing actions 65 % Precomputing frequently used data
- vtune: Executing actions 66 % Precomputing frequently used data
- vtune: Executing actions 67 % Precomputing frequently used data
- vtune: Executing actions 68 % Precomputing frequently used data
- vtune: Executing actions 70 % Precomputing frequently used data
- vtune: Executing actions 71 % Precomputing frequently used data
- vtune: Executing actions 72 % Precomputing frequently used data
- vtune: Executing actions 72 % Updating precomputed scalar metrics
- vtune: Executing actions 75 % Updating precomputed scalar metrics
- vtune: Executing actions 75 % Discarding redundant overtime data
- vtune: Executing actions 78 % Discarding redundant overtime data
- vtune: Executing actions 78 % Saving the result
- vtune: Executing actions 82 % Saving the result
- vtune: Executing actions 85 % Saving the result
- vtune: Executing actions 100 % Saving the result
- vtune: Executing actions 100 % done
- Finalization: Ok
- --------------------------------------------------------------------------------
- Command line:
- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ge
- Stdout:
- Function,CPU Time,Clockticks,Clockticks:P-Core,Clockticks:E-Core,Instructions Retired,Instructions Retired:P-Core,Instructions Retired:E-Core,CPI Rate,CPI Rate:P-Core,CPI Rate:E-Core,P-Core:Retiring(%),P-Core:Retiring:Light Operations(%),P-Core:Retiring:Light Operations:FP Arithmetic(%),P-Core:Retiring:Light Operations:FP Arithmetic:FP x87(%),P-Core:Retiring:Light Operations:FP Arithmetic:FP Scalar(%),P-Core:Retiring:Light Operations:FP Arithmetic:FP Vector(%),P-Core:Retiring:Light Operations:Memory Operations(%),P-Core:Retiring:Light Operations:Fused Instructions(%),P-Core:Retiring:Light Operations:Non Fused Branches(%),P-Core:Retiring:Light Operations:Nop Instructions(%),P-Core:Retiring:Light Operations:Other(%),P-Core:Retiring:Heavy Operations(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer:Assists(%),P-Core:Retiring:Heavy Operations:Microcode Sequencer:CISC(%),P-Core:Front-End Bound(%),P-Core:Front-End Bound:Front-End Latency(%),P-Core:Front-End Bound:Front-End Latency:ICache Misses(%),P-Core:Front-End Bound:Front-End Latency:ITLB Overhead(%),P-Core:Front-End Bound:Front-End Latency:Branch Resteers(%),P-Core:Front-End Bound:Front-End Latency:Branch Resteers:Mispredicts Resteers(%),P-Core:Front-End Bound:Front-End Latency:Branch Resteers:Clears Resteers(%),P-Core:Front-End Bound:Front-End Latency:Branch Resteers:Unknown Branches(%),P-Core:Front-End Bound:Front-End Latency:DSB Switches(%),P-Core:Front-End Bound:Front-End Latency:Length Changing Prefixes(%),P-Core:Front-End Bound:Front-End Latency:MS Switches(%),P-Core:Front-End Bound:Front-End Bandwidth(%),P-Core:Front-End Bound:Front-End Bandwidth:Front-End Bandwidth MITE(%),P-Core:Front-End Bound:Front-End Bandwidth:Front-End Bandwidth MITE:Decoder-0 Alone(%),P-Core:Front-End Bound:Front-End Bandwidth:Front-End Bandwidth DSB(%),P-Core:Front-End Bound:Front-End Bandwidth:Front-End Bandwidth LSD(%),P-Core:Front-End Bound:Front-End Bandwidth:(Info) DSB Coverage(%),P-Core:Front-End Bound:Front-End Bandwidth:(Info) LSD Coverage(%),P-Core:Front-End Bound:Front-End Bandwidth:(Info) DSB Misses Cost(%),P-Core:Bad Speculation(%),P-Core:Bad Speculation:Branch Mispredict(%),P-Core:Bad Speculation:Machine Clears(%),P-Core:Back-End Bound(%),P-Core:Back-End Bound:Memory Bound(%),P-Core:Back-End Bound:Memory Bound:L1 Bound(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead:Load STLB Hit(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:DTLB Overhead:Load STLB Miss(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:Loads Blocked by Store Forwarding(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:Lock Latency(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:Split Loads(%),P-Core:Back-End Bound:Memory Bound:L1 Bound:FB Full(%),P-Core:Back-End Bound:Memory Bound:L2 Bound(%),P-Core:Back-End Bound:Memory Bound:L3 Bound(%),P-Core:Back-End Bound:Memory Bound:L3 Bound:L3 Latency(%),P-Core:Back-End Bound:Memory Bound:L3 Bound:SQ Full(%),P-Core:Back-End Bound:Memory Bound:DRAM Bound(%),P-Core:Back-End Bound:Memory Bound:DRAM Bound:Memory Bandwidth(%),P-Core:Back-End Bound:Memory Bound:DRAM Bound:Memory Latency(%),P-Core:Back-End Bound:Memory Bound:Store Bound(%),P-Core:Back-End Bound:Memory Bound:Store Bound:Store Latency(%),P-Core:Back-End Bound:Memory Bound:Store Bound:Split Stores(%),P-Core:Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead(%),P-Core:Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead:Store STLB Hit(%),P-Core:Back-End Bound:Memory Bound:Store Bound:DTLB Store Overhead:Store STLB Hit(%),P-Core:Back-End Bound:Core Bound(%),P-Core:Back-End Bound:Core Bound:Divider(%),P-Core:Back-End Bound:Core Bound:Port Utilization(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Serializing Operations(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Serializing Operations:Slow Pause(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Serializing Operations:Memory Fence(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 0 Ports Utilized:Mixing Vectors(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 1 Port Utilized(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 2 Ports Utilized(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 0(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 1(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:ALU Operation Utilization:Port 6(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Load Operation Utilization(%),P-Core:Back-End Bound:Core Bound:Port Utilization:Cycles of 3+ Ports Utilized:Store Operation Utilization(%),E-Core:Retiring(%),E-Core:Retiring:General Retirement(%),E-Core:Retiring:General Retirement:FP Arithmetic(%),E-Core:Retiring:General Retirement:Other(%),E-Core:Retiring:Microcode Sequencer(%),E-Core:Front-End Bound(%),E-Core:Front-End Bound:Front-End Latency(%),E-Core:Front-End Bound:Front-End Latency:ICache Misses(%),E-Core:Front-End Bound:Front-End Latency:ITLB Overhead(%),E-Core:Front-End Bound:Front-End Latency:BACLEARS(%),E-Core:Front-End Bound:Front-End Latency:Branch Resteers(%),E-Core:Front-End Bound:Front-End Bandwidth(%),E-Core:Front-End Bound:Front-End Bandwidth:Cisc(%),E-Core:Front-End Bound:Front-End Bandwidth:Decode(%),E-Core:Front-End Bound:Front-End Bandwidth:Pre-Decode Wrong(%),E-Core:Front-End Bound:Front-End Bandwidth:Front-End Other(%),E-Core:Bad Speculation(%),E-Core:Bad Speculation:Branch Mispredict(%),E-Core:Bad Speculation:Machine Clears(%),E-Core:Bad Speculation:Machine Clears:Machine Clear(%),E-Core:Bad Speculation:Machine Clears:MO Machine Clear Overhead(%),E-Core:Back-End Bound(%),E-Core:Back-End Bound:Resource Bound(%),E-Core:Back-End Bound:Resource Bound:Memory Scheduler(%),E-Core:Back-End Bound:Resource Bound:Non-memory Scheduler(%),E-Core:Back-End Bound:Resource Bound:Register(%),E-Core:Back-End Bound:Resource Bound:Full Re-order Buffer (ROB)(%),E-Core:Back-End Bound:Resource Bound:Allocation Restriction(%),E-Core:Back-End Bound:Resource Bound:Serializing Operations(%),E-Core:Alternative Back-End Bound(%),E-Core:Alternative Back-End Bound:Core Bound(%),E-Core:Alternative Back-End Bound:Memory Bound(%),E-Core:Alternative Back-End Bound:Memory Bound:L2 Bound(%),E-Core:Alternative Back-End Bound:Memory Bound:L3 Bound(%),E-Core:Alternative Back-End Bound:Memory Bound:DRAM Bound(%),Average CPU Frequency,Module,Function (Full),Source File,Start Address
- multiply1,32.189005,119241605000,0,119241605000,67309440000,0,67309440000,1.771544,0.0,1.771544,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,11.4,11.3,30.3,0.0,0.1,0.5,0.0,0.0,0.0,0.0,0.0,54.4,27.2,27.2,0.0,0.1,98.9,16.4,16.5,0.0,16.4,98.9,98.9,100.0,0.0,0.0,0.0,100.0,0.1,98.9,41.0,57.9,1.2,12.0,44.7,3704420314.692150,matrix.exe,multiply1,multiply.c,0x1400017f0
- func@0x1404184b0,0.024998,86049000,0,86049000,9561000,0,9561000,9.000000,0.0,9.000000,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,3.5,3.5,100.0,0.0,0.0,10.5,2.3,1.2,1.2,0.0,0.0,65.1,32.5,32.5,0.0,0.0,82.5,17.4,20.9,3.5,17.4,82.5,82.5,34.9,0.0,0.0,0.0,34.9,63.9,82.5,58.1,24.4,11.6,10.5,2.3,3442173296.760000,ntoskrnl.exe,func@0x1404184b0,[Unknown],0x1404184b0
- KeClockInterruptNotify,0.016999,82862000,0,82862000,3187000,0,3187000,26.000000,0.0,26.000000,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,8.4,3.6,2.4,0.0,1.2,0.0,43.4,21.7,21.7,0.0,0.0,88.1,20.5,20.5,0.0,20.5,88.1,88.1,48.3,0.0,0.0,0.0,48.3,45.9,88.1,57.9,30.2,6.0,21.7,2.4,4874537348.352941,ntoskrnl.exe,KeClockInterruptNotify,[Unknown],0x140252520
- func@0x14041e750,0.011999,12748000,0,12748000,3187000,0,3187000,4.000000,0.0,4.000000,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,0.0,54.9,0.0,0.0,0.0,0.0,0.0,100.0,86.3,86.3,0.0,7.8,100.0,39.2,39.2,0.0,39.2,100.0,100.0,94.1,0.0,0.0,0.0,94.1,100.0,100.0,62.8,70.6,7.8,54.9,7.8,1062399165.666667,ntoskrnl.exe,func@0x14041e750,[Unknown],0x14041e750
- [ntoskrnl.exe],0.008000,12748000,0,12748000,6374000,0,6374000,2.000000,0.0,2.000000,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,23.5,0.0,100.0,0.0,31.4,62.8,23.5,23.5,0.0,0.0,0.0,100.0,100.0,100.0,0.0,0.0,100.0,31.4,31.4,0.0,31.4,100.0,100.0,100.0,0.0,0.0,0.0,100.0,54.9,100.0,78.4,100.0,23.5,62.8,15.7,1593598748.500000,ntoskrnl.exe,[ntoskrnl.exe],[Unknown],0x0
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -collect memory-access -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ma -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\matrix.exe
- Stdout:
- Addr of buf1 = 0000000000A1B040
- Offs of buf1 = 0000000000A1B180
- Addr of buf2 = 0000000002A2C040
- Offs of buf2 = 0000000002A2C1C0
- Addr of buf3 = 0000000004A37040
- Offs of buf3 = 0000000004A37100
- Addr of buf4 = 0000000006A43040
- Offs of buf4 = 0000000006A43140
- Threads #: 16 Win threads
- Matrix size: 2048
- Using multiply kernel: multiply1
- Execution time = 7.933 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\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ma -command stop.
- vtune: Collection stopped.
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -finalize -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ma
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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-20420-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'systemcollector-20420-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.tb7' file
- vtune: Executing actions 25 % Loading 'sep7a04.20220416T171328.659634.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 `usbaudio.sys'
- vtune: Executing actions 39 % Resolving information for `dxgkrnl.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\usbaudio.sys'.
- vtune: Executing actions 39 % Resolving information for `ucrtbase.dll'
- vtune: Executing actions 39 % Resolving information for `netio.sys'
- vtune: Executing actions 39 % Resolving information for `ntdll.dll'
- vtune: Executing actions 39 % Resolving information for `nvlddmkm.sys'
- vtune: Executing actions 39 % Resolving information for `matrix.exe'
- vtune: Executing actions 39 % Resolving information for `ks.sys'
- vtune: Executing actions 39 % Resolving information for `intelppm.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\dxgkrnl.sys'.
- vtune: Executing actions 39 % Resolving information for `ntoskrnl.exe'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\ucrtbase.dll'.
- 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 40 % Resolving information for `ntoskrnl.exe'
- vtune: Executing actions 40 % Resolving information for `cng.sys'
- vtune: Executing actions 40 % Resolving information for `usbxhci.sys'
- vtune: Executing actions 40 % Resolving information for dangling locations
- vtune: Executing actions 41 % Resolving information for dangling locations
- vtune: Executing actions 41 % Resolving information for `dxgmms2.sys'
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\ks.sys'.
- vtune: Executing actions 41 % Resolving information for `wdf01000.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\driverstore\filerepository\nv_dispi.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.sys'.
- vtune: Executing actions 41 % Resolving information for `hdaudbus.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\drivers\dxgmms2.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\usbxhci.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\cng.sys'.
- vtune: Executing actions 42 % Resolving information for `hdaudbus.sys'
- vtune: Executing actions 42 % Resolving information for `classpnp.sys'
- vtune: Executing actions 42 % Resolving information for `wpprecorder.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\hdaudbus.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\wpprecorder.sys'.
- vtune: Executing actions 42 % Resolving information for `ucx01000.sys'
- vtune: Executing actions 43 % Resolving information for `ucx01000.sys'
- vtune: Executing actions 43 % Resolving information for `volsnap.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\ucx01000.sys'.
- vtune: Warning: Cannot locate debugging information for file `c:\windows\system32\drivers\volsnap.sys'.
- vtune: Executing actions 44 % Resolving information for `volsnap.sys'
- vtune: Executing actions 45 % Resolving information for `volsnap.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 54 % Processing profile metrics and debug information
- vtune: Executing actions 55 % Processing profile metrics and debug information
- vtune: Executing actions 56 % Processing profile metrics and debug information
- vtune: Executing actions 57 % Processing profile metrics and debug information
- vtune: Executing actions 58 % Processing profile metrics and debug information
- vtune: Executing actions 60 % Processing profile metrics and debug information
- vtune: Executing actions 62 % Processing profile metrics and debug information
- vtune: Executing actions 63 % Processing profile metrics and debug information
- vtune: Executing actions 63 % Preparing output tree
- vtune: Executing actions 63 % Parsing columns in input tree
- vtune: Executing actions 64 % Parsing columns in input tree
- vtune: Executing actions 64 % Creating top-level columns
- vtune: Executing actions 65 % Creating top-level columns
- vtune: Executing actions 65 % Creating top-level rows
- vtune: Executing actions 67 % Creating top-level rows
- vtune: Executing actions 67 % Setting data model parameters
- vtune: Executing actions 68 % Setting data model parameters
- vtune: Executing actions 68 % Precomputing frequently used data
- vtune: Executing actions 68 % Precomputing frequently used data
- vtune: Executing actions 69 % Precomputing frequently used data
- vtune: Executing actions 70 % Precomputing frequently used data
- vtune: Executing actions 71 % Precomputing frequently used data
- vtune: Executing actions 72 % Precomputing frequently used data
- vtune: Executing actions 73 % Precomputing frequently used data
- vtune: Executing actions 74 % Precomputing frequently used data
- vtune: Executing actions 75 % Precomputing frequently used data
- vtune: Executing actions 76 % Precomputing frequently used data
- vtune: Executing actions 77 % Precomputing frequently used data
- vtune: Executing actions 78 % Precomputing frequently used data
- vtune: Executing actions 79 % Precomputing frequently used data
- vtune: Executing actions 79 % Updating precomputed scalar metrics
- vtune: Executing actions 82 % Updating precomputed scalar metrics
- vtune: Executing actions 82 % Discarding redundant overtime data
- vtune: Executing actions 85 % Discarding redundant overtime data
- vtune: Executing actions 85 % Saving the result
- vtune: Executing actions 89 % Saving the result
- vtune: Executing actions 92 % Saving the result
- vtune: Executing actions 100 % Saving the result
- vtune: Executing actions 100 % done
- Finalization: Ok
- --------------------------------------------------------------------------------
- Command line:
- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ma
- Stdout:
- Function,CPU Time,P-Core:Memory Bound(%),P-Core:Memory Bound:L1 Bound(%),P-Core:Memory Bound:L2 Bound(%),P-Core:Memory Bound:L3 Bound(%),P-Core:Memory Bound:DRAM Bound(%),P-Core:Memory Bound:Store Bound(%),E-Core:Memory Bound(%),E-Core:Memory Bound:L2 Bound(%),E-Core:Memory Bound:L3 Bound(%),E-Core:Memory Bound:DRAM Bound(%),Loads,Stores,LLC Miss Count,Module,Function (Full),Source File,Start Address
- multiply1,24.945454,0.0,0.0,0.0,0.0,0.0,0.0,100.0,0.9,12.1,95.5,27140814200,3120693618,223206696,matrix.exe,multiply1,multiply.c,0x1400017f0
- KeClockInterruptNotify,0.037998,0.0,0.0,0.0,0.0,0.0,0.0,53.1,6.1,21.1,25.9,2600078,1200036,0,ntoskrnl.exe,KeClockInterruptNotify,[Unknown],0x140252520
- func@0x1404184b0,0.029998,0.0,0.0,0.0,0.0,0.0,0.0,69.9,16.1,7.5,46.3,8600258,6200186,0,ntoskrnl.exe,func@0x1404184b0,[Unknown],0x1404184b0
- func@0x14041e750,0.016999,0.0,0.0,0.0,0.0,0.0,0.0,76.4,3.4,30.8,42.2,2000060,800024,0,ntoskrnl.exe,func@0x14041e750,[Unknown],0x14041e750
- func@0x14008f73c,0.011999,0.0,0.0,0.0,0.0,0.0,0.0,23.0,0.0,0.0,23.0,600018,0,0,nvlddmkm.sys,func@0x14008f73c,[Unknown],0x14008f73c
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\matrix.exe
- Stdout:
- Addr of buf1 = 0000000000856040
- Offs of buf1 = 0000000000856180
- Addr of buf2 = 0000000002867040
- Offs of buf2 = 00000000028671C0
- Addr of buf3 = 0000000004874040
- Offs of buf3 = 0000000004874100
- Addr of buf4 = 0000000006882040
- Offs of buf4 = 0000000006882140
- Threads #: 16 Win threads
- Matrix size: 2048
- Using multiply kernel: multiply1
- Execution time = 9.923 seconds
- Stderr:
- vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ah_with_stacks -command stop.
- vtune: Collection stopped.
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -finalize -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ah_with_stacks
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_ah_with_stacks'
- vtune: Executing actions 0 %
- vtune: Executing actions 0 % Finalizing results
- vtune: Executing actions 0 % Finalizing the result
- vtune: Executing actions 0 % Clearing the database
- vtune: Executing actions 14 % Clearing the database
- vtune: Executing actions 14 % Loading raw data to the database
- vtune: Executing actions 14 % Loading 'systemcollector-24564-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'systemcollector-24564-Desktop.sc' file
- vtune: Executing actions 25 % Loading '31944.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 `ucrtbase.dll'
- vtune: Executing actions 39 % Resolving information for `kernel32.dll'
- vtune: Executing actions 39 % Resolving information for `ntdll.dll'
- vtune: Executing actions 39 % Resolving information for `dxgmms2.sys'
- vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\kernel32.dll'.
- vtune: Warning: Cannot locate debugging information for file `C:\Windows\System32\ucrtbase.dll'.
- vtune: Executing actions 39 % Resolving information for `nvlddmkm.sys'
- vtune: Executing actions 39 % Resolving information for `tcpip.sys'
- vtune: Executing actions 40 % Resolving information for `tcpip.sys'
- vtune: Executing actions 40 % Resolving information for `matrix.exe'
- vtune: Executing actions 40 % Resolving information for `ntoskrnl.exe'
- 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\dxgmms2.sys'.
- vtune: Executing actions 40 % Resolving information for `vtss.sys'
- vtune: Executing actions 41 % Resolving information for `vtss.sys'
- vtune: Executing actions 41 % Resolving information for `intelppm.sys'
- vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\drivers\tcpip.sys'.
- vtune: Executing actions 42 % Resolving information for `intelppm.sys'
- vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\system32\ntoskrnl.exe'.
- vtune: Executing actions 43 % Resolving information for `intelppm.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\vtss.sys'.
- vtune: Executing actions 44 % Resolving information for `intelppm.sys'
- vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.sys'.
- vtune: Executing actions 45 % Resolving information for `intelppm.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
- --------------------------------------------------------------------------------
- Command line:
- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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: Fail
- ================================================================================
- HW event-based analysis with context switches...
- Command line:
- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\bin64\vtune.exe -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_th -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\samples\en\C++\matrix\matrix.exe
- Stdout:
- Addr of buf1 = 000000000080E040
- Offs of buf1 = 000000000080E180
- Addr of buf2 = 000000000281F040
- Offs of buf2 = 000000000281F1C0
- Addr of buf3 = 0000000004839040
- Offs of buf3 = 0000000004839100
- Addr of buf4 = 0000000006844040
- Offs of buf4 = 0000000006844140
- Threads #: 16 Win threads
- Matrix size: 2048
- Using multiply kernel: multiply1
- Execution time = 9.473 seconds
- Stderr:
- vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_th -command stop.
- vtune: Collection stopped.
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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\2022.2.0\bin64\vtune.exe -finalize -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\result_th
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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-32004-Desktop.sc' file
- vtune: Executing actions 25 % Loading 'systemcollector-32004-Desktop.sc' file
- vtune: Executing actions 25 % Loading '13688.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 41 % Resolving information for dangling locations
- vtune: Executing actions 41 % Resolving information for `ntdll.dll'
- 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\2022.2.0\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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
- LdrInitializeThunk,0.0,0.0,0.0,0.0,0.004729,0.0,0.0,0.0,0.0,0.0,0.0,0.004729,0.004729,0.0,0.0,0.0,0.0,7,0,0,0,0,0,0,7,7,0,0,0,0,ntdll.dll,LdrInitializeThunk,[Unknown],0x18007a8b0
- NtConnectPort,0.0,0.0,0.0,0.0,0.000042,0.0,0.0,0.0,0.0,0.0,0.0,0.000042,0.000042,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
- NtCreateFile,0.0,0.0,0.0,0.0,0.000137,0.0,0.0,0.0,0.0,0.0,0.0,0.000137,0.000137,0.0,0.0,0.0,0.0,1,0,0,0,0,0,0,1,1,0,0,0,0,ntdll.dll,NtCreateFile,[Unknown],0x1800a41e0
- NtCreateThreadEx,0.0,0.0,0.0,0.0,0.000083,0.0,0.0,0.0,0.0,0.0,0.0,0.000083,0.000083,0.0,0.0,0.0,0.0,2,0,0,0,0,0,0,2,2,0,0,0,0,ntdll.dll,NtCreateThreadEx,[Unknown],0x1800a4fd0
- NtDeviceIoControlFile,0.0,0.0,0.0,0.0,0.000304,0.000096,0.000096,0.0,0.0,0.0,0.0,0.000208,0.000208,0.0,0.0,0.0,0.0,13,5,5,0,0,0,0,8,8,0,0,0,0,ntdll.dll,NtDeviceIoControlFile,[Unknown],0x1800a3820
- Stderr:
- vtune: Using result path `C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\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: Fail
- 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
- * Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
- * Microarchitecture Exploration
- * Memory Access
- The following analyses have failed on the system:
- * Hotspots with HW event-based sampling and call stacks
- * Threading with HW event-based sampling
- * GPU Compute/Media Hotspots (characterization mode)
- * GPU Compute/Media Hotspots (source analysis mode)
- Log location: C:\Users\EMELRA~1\AppData\Local\Temp\vtune-tmp-emelrad12\self-checker-2022.04.16_17.12.00\log.txt
Add Comment
Please, Sign In to add comment