Intel(R) VTune(TM) Profiler Self Check Utility Copyright (C) 2009-2020 Intel Corporation. All rights reserved. Build Number: 621966 Ignored warnings: ['To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location.', 'To enable hardware event-based sampling, PRODUCT_LEGAL_SHORT_NAME has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.'] Check of files: Ok ================================================================================ Context values: Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\amplxe-runss.exe --context-value-list Stdout: targetOS: Windows OS: Windows OSBuildNumber: 19043 OSBitness: 64 AdministratorPrivileges: false isPtraceScopeLimited: false isCATSupportedByCPU: false isL3MonitoringSupportedByCPU: false isTSXAvailable: true isPTAvailable: false isHTEnabled: true fpgaOnBoard: None omniPathOnBoard: None genArchOnBoard: 0 pciClassParts: tidValuesForIO: populatedIoParts: populatedIoUnits: populatedTidValuesForIO: isSGXAvailable: false Hypervisor: Microsoft Hv PerfmonVersion: 4 isMaxDRAMBandwidthMeasurementSupported: true preferedGpuAdapter: 0:1:0.0 isEHFIAvailable: false areGpuHardwareMetricsAvailableList: gpuPlatformIndexList: ETW: ACCESS_DENIED isGpuBusynessAvailable: notAccessible isGpuBusynessDetailsAvailable: notAccessible isGpuWaitAvailable: no isEtwCLRSupported: accessDenied isFtraceAvailable: isMdfEtwAvailable: false isCSwitchAvailable: yes isFunctionTracingAvailable: no isIowaitTracingAvailable: no isVSyncAvailable: na HypervisorType: None isDeviceOrCredentialGuardEnabled: false isSEPDriverAvailable: false isPAXDriverLoaded: false platformType: 122 CPU_NAME: Intel(R) microarchitecture code named Coffeelake PMU: skylake referenceFrequency: 3600000000 isPStateAvailable: true isVTSSPPDriverAvailable: true isNMIWatchDogTimerRunning: false isAOCLAvailable: false isTPSSAvailable: true isPytraceAvailable: true isGENDebugInfoAvailableList: isGTPinCollectionAvailableList: forceShowInlines: false isEnergyCollectionSupported: false isSocwatchDriverLoaded: true isCPUSupportedBySocwatch: true isCpuThrottlingAvailable: false isIPMWatchReady: false isNvdimmAvailable: false isOsCountersCollectorAvailable: false l0LoaderStatus: LibNotFound l0DevicesAvailable: false l0VPUDevicesAvailable: false l0GPUDevicesAvailable: false Getting context values: OK ================================================================================ Check driver: isSEPDriverAvailable: false isPAXDriverLoaded: false The SEP driver is not available. ================================================================================ SEP version: Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\sep.exe -version Stdout: Sampling Enabling Product Version: 5.31 built on Dec 4 2021 09:23:59 SEP Driver Version: PAX Driver Version: Platform type: 122 CPU name: Intel(R) microarchitecture code named Coffeelake PMU: skylake Stderr: Error retrieving SEP driver version Error retrieving PAX driver version Check driver with sep -version: Fail ================================================================================ HW event-based analysis (counting mode)... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect performance-snapshot -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ps -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe Stdout: Addr of buf1 = 0000000006F01040 Offs of buf1 = 0000000006F01180 Addr of buf2 = 0000000008F1D040 Offs of buf2 = 0000000008F1D1C0 Addr of buf3 = 000000000AF28040 Offs of buf3 = 000000000AF28100 Addr of buf4 = 000000000CF35040 Offs of buf4 = 000000000CF35140 Threads #: 8 Win threads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 44.757 seconds Stderr: vtune: Warning: To collect hardware events, run the product as administrator. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ps -command stop. vtune: Collection stopped. vtune: Using result path `C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ps' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done Cannot find 'runsa.options' by path: C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ps\config\runsa.options HW event-based analysis (counting mode) Example of analysis types: Performance Snapshot Collection: Ok vtune: Warning: To collect hardware events, run the product as administrator. -------------------------------------------------------------------------------- Running finalization... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -finalize -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ps Stderr: vtune: Using result path `C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\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-8288-BRUCEH-WIN10.dlogic vtune: Executing actions 25 % Loading 'systemcollector-8288-BRUCEH-WIN10.dlogic vtune: Executing actions 25 % Loading '28976-22880.0.trace' 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 `ntdll.dll' vtune: Executing actions 39 % Resolving information for `matrix.exe' vtune: Executing actions 39 % Resolving information for `KERNEL32.dll' vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\SYSTEM32\ntdll.dll'. vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\KERNEL32.dll'. vtune: Executing actions 41 % Resolving information for `KERNEL32.dll' vtune: Executing actions 43 % Resolving information for `KERNEL32.dll' vtune: Executing actions 45 % Resolving information for `KERNEL32.dll' vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 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 60 % Setting data model parameters vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 63 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 72 % Updating precomputed scalar metrics vtune: Executing actions 75 % Updating precomputed scalar metrics vtune: Executing actions 75 % Discarding redundant overtime data vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 78 % Saving the result vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok -------------------------------------------------------------------------------- Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -R summary -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ps Stdout: Elapsed Time: 44.840s Total Thread Count: 9 Collection and Platform Info Application Command Line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe Operating System: Microsoft Windows 10 Computer Name: BRUCEH-WIN10.dlogics.com Result Size: 4.1 MB Collection start time: 20:37:07 01/07/2022 UTC Collection stop time: 20:37:52 01/07/2022 UTC Collector Type: User-mode sampling and tracing CPU Name: Intel(R) microarchitecture code named Coffeelake Frequency: 3.600 GHz Logical CPU Count: 8 Cache Allocation Technology Level 2 capability: not detected Level 3 capability: not detected Recommendations: Cannot perform hardware collection of CPU events on this system: | You can only run Hotspots or Threading analyses. To run other analyses | that require hardware collection of CPU events, install the sampling | driver (see the Sampling Drivers help topic for further details) for | hardware event-based sampling collection. 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. If you want to skip descriptions of detected performance issues in the report, enter: vtune -report summary -report-knob show-issues=false -r . Alternatively, you may view the report in the csv format: vtune -report -format=csv. Stderr: vtune: Using result path `C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ps' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ Instrumentation based analysis check... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect hotspots -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_tpss -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe Stdout: Addr of buf1 = 00000000071BF040 Offs of buf1 = 00000000071BF180 Addr of buf2 = 00000000091D3040 Offs of buf2 = 00000000091D31C0 Addr of buf3 = 000000000B1E9040 Offs of buf3 = 000000000B1E9100 Addr of buf4 = 000000000D1FF040 Offs of buf4 = 000000000D1FF140 Threads #: 8 Win threads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 48.669 seconds Stderr: vtune: Warning: Hardware collection of CPU events is not possible on this system. Microarchitecture performance insights will not be available. vtune: Warning: To collect microarchitecture performance insights, run the product as administrator. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_tpss -command stop. vtune: Collection stopped. vtune: Using result path `C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_tpss' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done Instrumentation based analysis check Example of analysis types: Hotspots and Threading with user-mode sampling Collection: Ok vtune: Warning: Hardware collection of CPU events is not possible on this system. Microarchitecture performance insights will not be available. vtune: Warning: To collect microarchitecture performance insights, run the product as administrator. -------------------------------------------------------------------------------- Running finalization... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -finalize -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_tpss Stderr: vtune: Using result path `C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\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-4152-BRUCEH-WIN10.dlogic vtune: Executing actions 25 % Loading 'systemcollector-4152-BRUCEH-WIN10.dlogic vtune: Executing actions 25 % Loading '18508-24288.0.trace' 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 `KERNEL32.dll' vtune: Executing actions 39 % Resolving information for `ucrtbase.dll' vtune: Executing actions 39 % Resolving information for `matrix.exe' vtune: Executing actions 39 % Resolving information for `ntdll.dll' vtune: Executing actions 39 % Resolving information for `KERNELBASE.dll' vtune: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\KERNEL32.dll'. vtune: Executing actions 39 % Resolving information for `hmpalert.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: Warning: Cannot locate debugging information for file `C:\WINDOWS\System32\KERNELBASE.dll'. vtune: Executing actions 40 % Resolving information for `hmpalert.dll' vtune: Warning: Cannot locate debugging information for file `C:\Windows\system32\hmpalert.dll'. vtune: Executing actions 40 % Resolving information for `tpsstool.dll' vtune: Executing actions 41 % Resolving information for `tpsstool.dll' vtune: Executing actions 42 % Resolving information for `tpsstool.dll' vtune: Executing actions 43 % Resolving information for `tpsstool.dll' vtune: Executing actions 44 % Resolving information for `tpsstool.dll' vtune: Warning: Cannot locate debugging information for file `C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\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 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 63 % Precomputing frequently used data vtune: Executing actions 66 % Precomputing frequently used data vtune: Executing actions 69 % Precomputing frequently used data vtune: Executing actions 72 % Precomputing frequently used data vtune: Executing actions 72 % Updating precomputed scalar metrics vtune: Executing actions 75 % Updating precomputed scalar metrics vtune: Executing actions 75 % Discarding redundant overtime data vtune: Executing actions 78 % Discarding redundant overtime data vtune: Executing actions 78 % Saving the result vtune: Executing actions 82 % Saving the result vtune: Executing actions 85 % Saving the result vtune: Executing actions 99 % Saving the result vtune: Executing actions 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok -------------------------------------------------------------------------------- Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\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,263.631856,263.631856,0.0,0.0,matrix.exe,multiply1,multiply.c,0x1400017f0 WaitForMultipleObjects,0.051444,0.0,0.051444,0.0,KERNELBASE.dll,WaitForMultipleObjects,[Unknown],0x18004cab0 init_arr,0.039107,0.039107,0.0,0.0,matrix.exe,init_arr,matrix.c,0x1400010a0 free_base,0.004690,0.004690,0.0,0.0,ucrtbase.dll,free_base,[Unknown],0x18000f040 Stderr: vtune: Using result path `C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_tpss' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ HW event-based analysis check... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect hotspots -knob sampling-mode=hw -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ah -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe Stderr: vtune: Error: Cannot enable Hardware Event-Based Sampling. Please check the following: * Check that the Sampling Driver is loaded (see the Install the Sampling Drivers for Windows Targets help topic for details). * Run the product as administrator to collect hardware events. Cannot find 'runsa.options' by path: C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ah\config\runsa.options HW event-based analysis check Example of analysis types: Hotspots with HW event-based sampling, HPC Performance Characterization, etc. Collection: Fail vtune: Error: Cannot enable Hardware Event-Based Sampling. Please check the following: * Check that the Sampling Driver is loaded (see the Install the Sampling Drivers for Windows Targets help topic for details). * Run the product as administrator to collect hardware events. ================================================================================ HW event-based analysis check... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect uarch-exploration -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ge -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe Stderr: vtune: Error: Cannot enable Hardware Event-Based Sampling. Please check the following: * Check that the Sampling Driver is loaded (see the Install the Sampling Drivers for Windows Targets help topic for details). * Run the product as administrator to collect hardware events. Cannot find 'runsa.options' by path: C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ge\config\runsa.options HW event-based analysis check Example of analysis types: Microarchitecture Exploration Collection: Fail vtune: Error: Cannot enable Hardware Event-Based Sampling. Please check the following: * Check that the Sampling Driver is loaded (see the Install the Sampling Drivers for Windows Targets help topic for details). * Run the product as administrator to collect hardware events. ================================================================================ HW event-based analysis with uncore events... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect memory-access -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ma -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe Stderr: vtune: Error: Memory Access analysis is not supported inside a virtual machine since uncore events cannot be collected. For full functionality, consider using a bare-metal environment. Cannot find 'runsa.options' by path: C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ma\config\runsa.options HW event-based analysis with uncore events Example of analysis types: Memory Access Collection: Fail vtune: Error: Memory Access analysis is not supported inside a virtual machine since uncore events cannot be collected. For full functionality, consider using a bare-metal environment. ================================================================================ HW event-based analysis with stacks... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe Stderr: vtune: Error: Cannot enable Hardware Event-Based Sampling. Please check the following: * Check that the Sampling Driver is loaded (see the Install the Sampling Drivers for Windows Targets help topic for details). * Run the product as administrator to collect hardware events. Cannot find 'runsa.options' by path: C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_ah_with_stacks\config\runsa.options HW event-based analysis with stacks Example of analysis types: Hotspots with HW event-based sampling and call stacks Collection: Fail vtune: Error: Cannot enable Hardware Event-Based Sampling. Please check the following: * Check that the Sampling Driver is loaded (see the Install the Sampling Drivers for Windows Targets help topic for details). * Run the product as administrator to collect hardware events. ================================================================================ HW event-based analysis with context switches... Command line: C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune.exe -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_th -data-limit 0 -finalization-mode none -source-search-dir C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\src -- C:\Program Files (x86)\Intel\oneAPI\vtune\latest\samples\en\C++\matrix\matrix.exe Stderr: vtune: Error: Cannot enable Hardware Event-Based Sampling. Please check the following: * Check that the Sampling Driver is loaded (see the Install the Sampling Drivers for Windows Targets help topic for details). * Run the product as administrator to collect hardware events. Cannot find 'runsa.options' by path: C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\result_th\config\runsa.options HW event-based analysis with context switches Example of analysis types: Threading with HW event-based sampling Collection: Fail vtune: Error: Cannot enable Hardware Event-Based Sampling. Please check the following: * Check that the Sampling Driver is loaded (see the Install the Sampling Drivers for Windows Targets help topic for details). * Run the product as administrator to collect hardware events. 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 The following analyses have failed on the system: * Hotspots with HW event-based sampling, HPC Performance Characterization, etc. * Microarchitecture Exploration * Memory Access * Hotspots with HW event-based sampling and call stacks * Threading with HW event-based sampling * GPU Compute/Media Hotspots (characterization mode) * GPU Compute/Media Hotspots (source analysis mode) Log location: C:\Users\bruceh\AppData\Local\Temp\vtune-tmp-bruceh\self-checker-2022.07.01_15.37.02\log.txt