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: /opt/intel/oneapi/vtune/2022.2.0/bin64/amplxe-runss --context-value-list Stdout: targetOS: Linux OS: Linux OSBuildNumber: 0 OSBitness: 64 RootPrivileges: true isPtraceScopeLimited: false isCATSupportedByCPU: false isL3MonitoringSupportedByCPU: false isTSXAvailable: false isPTAvailable: false isHTEnabled: false fpgaOnBoard: None omniPathOnBoard: None genArchOnBoard: 0 pciClassParts: tidValuesForIO: populatedIoParts: populatedIoUnits: populatedTidValuesForIO: isSGXAvailable: false LinuxRelease: 5.4.0-109-generic is3DXPPresent: false is3DXP2LMMode: false is3DXPAppDirectMode: false IsNUMANodeWithoutCPUsPresent: false Hypervisor: VMwareVMware PerfmonVersion: 1 isMaxDRAMBandwidthMeasurementSupported: true preferedGpuAdapter: none isEHFIAvailable: false isPtraceAvailable: true i915Status: MissingDriver isFtraceAvailable: yes isMdfEtwAvailable: false isCSwitchAvailable: yes isGpuBusynessAvailable: unsupportedHardware isGpuWaitAvailable: no isFunctionTracingAvailable: yes isIowaitTracingAvailable: yes isVSyncAvailable: yes HypervisorType: None isDeviceOrCredentialGuardEnabled: false isSEPDriverAvailable: true SEPDriverVersion: 5.19 isPAXDriverLoaded: true PAXDriverVersion: 1.0 platformType: 123 CPU_NAME: Intel(R) microarchitecture code named Icelake PMU: icelake referenceFrequency: 2300000000 isPStateAvailable: false isVTSSPPDriverAvailable: true isNMIWatchDogTimerRunning: false LinuxPerfCredentials: Unlimited LinuxPerfCapabilities: breakpoint:raw;cpu:raw,format,events;kprobe:raw,format;msr:raw,format,events;power:raw,format,events;software:raw;tracepoint:raw;uprobe:raw,format LinuxPerfStackCapabilities: fp,dwarf,lbr areKernelPtrsRestricted: no LinuxPerfMuxIntervalMs: 4 isPerfPCIeMappingAvailable: false isAOCLAvailable: false isTPSSAvailable: true isPytraceAvailable: true forceShowInlines: false isEnergyCollectionSupported: true isSocwatchDriverLoaded: true isCPUSupportedBySocwatch: true isCpuThrottlingAvailable: true isIPMWatchReady: false osCountersCollectorAvailability: dstatNotFound l0LoaderStatus: LibNotFound l0DevicesAvailable: false l0VPUDevicesAvailable: false l0GPUDevicesAvailable: false Getting context values: OK ================================================================================ Check driver: isSEPDriverAvailable: true isPAXDriverLoaded: true Command line: lsmod Stdout: sep5 884736 0 socperf3 598016 2 socwatch2_12,sep5 Is SEP in lsmod: True Ok ================================================================================ SEP version: Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/sep -version Stdout: Sampling Enabling Product Version: 5.33 built on Mar 1 2022 18:03:06 SEP Driver Version: 5.19 (public) PAX Driver Version: 1.0 Platform type: 123 CPU name: Intel(R) microarchitecture code named Icelake PMU: icelake Driver configs: Non-Maskable Interrupt, PSTATE OFF, REGISTER CHECK ON Virtualization platform: Host VM on VMware Copyright(C) 2007-2020 Intel Corporation. All rights reserved. Check driver with sep -version: Ok ================================================================================ HW event-based analysis (counting mode)... Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -collect performance-snapshot -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ps -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f7878db7010 Offs of buf1 = 0x7f7878db7180 Addr of buf2 = 0x7f7876db6010 Offs of buf2 = 0x7f7876db61c0 Addr of buf3 = 0x7f7874db5010 Offs of buf3 = 0x7f7874db5100 Addr of buf4 = 0x7f7872db4010 Offs of buf4 = 0x7f7872db4140 Threads #: 2 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 21.926 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ps -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ps' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ps/config/runsa.options HW event-based analysis (counting mode) Example of analysis types: Performance Snapshot Collection: Ok -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ps Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ps' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-3037-ubuntu.sc' file vtune: Executing actions 25 % Loading 'systemcollector-3037-ubuntu.sc' file vtune: Executing actions 25 % Loading '3037-3042.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 `matrix' vtune: Executing actions 39 % Resolving information for `libc.so.6' vtune: Executing actions 41 % Resolving information for `libc.so.6' vtune: Executing actions 44 % Resolving information for `libc.so.6' vtune: Executing actions 44 % Resolving bottom user stack information vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving thread name information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 48 % Resolving call target names for dynamic code vtune: Executing actions 49 % Resolving call target names for dynamic code vtune: Executing actions 49 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 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: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -R summary -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ps Stdout: Elapsed Time: 22.094s Total Thread Count: 3 Collection and Platform Info Application Command Line: /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/matrix Operating System: 5.4.0-109-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.6 LTS" Computer Name: ubuntu Result Size: 3.4 MB Collection start time: 02:06:46 21/04/2022 UTC Collection stop time: 02:07:08 21/04/2022 UTC Collector Type: User-mode sampling and tracing CPU Name: Intel(R) microarchitecture code named Icelake Frequency: 2.304 GHz Logical CPU Count: 2 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, Threading or Memory Consumption analyses. Set | up Perf driverless collection (see the Profiling Hardware Without Intel | Sampling Drivers recipe from Intel VTune Profiler Performance Analysis | Cookbook for further details or 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 `/tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ps' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ Instrumentation based analysis check... Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -collect hotspots -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_tpss -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7f8412285010 Offs of buf1 = 0x7f8412285180 Addr of buf2 = 0x7f8410284010 Offs of buf2 = 0x7f84102841c0 Addr of buf3 = 0x7f840e283010 Offs of buf3 = 0x7f840e283100 Addr of buf4 = 0x7f840c282010 Offs of buf4 = 0x7f840c282140 Threads #: 2 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 22.735 seconds Stderr: vtune: Warning: Microarchitecture performance insights will not be available. Make sure the sampling driver is installed and enabled on your system. vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_tpss -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_tpss' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done Instrumentation based analysis check Example of analysis types: Hotspots and Threading with user-mode sampling Collection: Ok vtune: Warning: Microarchitecture performance insights will not be available. Make sure the sampling driver is installed and enabled on your system. -------------------------------------------------------------------------------- Running finalization... Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -finalize -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_tpss Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_tpss' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 0 % Finalizing the result vtune: Executing actions 0 % Clearing the database vtune: Executing actions 14 % Clearing the database vtune: Executing actions 14 % Loading raw data to the database vtune: Executing actions 14 % Loading 'systemcollector-3093-ubuntu.sc' file vtune: Executing actions 25 % Loading 'systemcollector-3093-ubuntu.sc' file vtune: Executing actions 25 % Loading '3093-3098.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 `matrix' vtune: Executing actions 39 % Resolving information for `libc.so.6' vtune: Executing actions 40 % Resolving information for `libc.so.6' vtune: Executing actions 40 % Resolving information for `libpthread.so.0' vtune: Executing actions 42 % Resolving information for `libpthread.so.0' vtune: Executing actions 42 % Resolving information for dangling locations vtune: Executing actions 43 % Resolving information for dangling locations vtune: Executing actions 45 % Resolving information for dangling locations vtune: Executing actions 45 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving bottom user stack information vtune: Executing actions 46 % Resolving thread name information vtune: Executing actions 47 % Resolving thread name information vtune: Executing actions 48 % Resolving thread name information vtune: Executing actions 48 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving call target names for dynamic code vtune: Executing actions 50 % Resolving interrupt name information vtune: Executing actions 53 % Resolving interrupt name information vtune: Executing actions 53 % Processing profile metrics and debug information vtune: Executing actions 56 % Processing profile metrics and debug information vtune: Executing actions 57 % Processing profile metrics and debug information vtune: Executing actions 58 % Processing profile metrics and debug information vtune: Executing actions 60 % Processing profile metrics and debug information vtune: Executing actions 60 % Setting data model parameters vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 60 % Precomputing frequently used data vtune: Executing actions 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 100 % Saving the result vtune: Executing actions 100 % done Finalization: Ok -------------------------------------------------------------------------------- Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_tpss Stdout: Function,CPU Time,CPU Time:Effective Time,CPU Time:Spin Time,CPU Time:Overhead Time,Module,Function (Full),Source File,Start Address multiply1,45.179904,45.179904,0.0,0.0,matrix,multiply1,multiply.c,0x401550 [Outside any known module],0.010000,0.010000,0.0,0.0,[Unknown],[Outside any known module],[Unknown],0x0 init_arr,0.010000,0.010000,0.0,0.0,matrix,init_arr,matrix.c,0x400d4f Stderr: vtune: Using result path `/tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_tpss' vtune: Executing actions 0 % vtune: Executing actions 0 % Finalizing results vtune: Executing actions 50 % Finalizing results vtune: Executing actions 50 % Generating a report vtune: Executing actions 50 % Setting data model parameters vtune: Executing actions 75 % Setting data model parameters vtune: Executing actions 75 % Generating a report vtune: Executing actions 100 % Generating a report vtune: Executing actions 100 % done Report: Ok ================================================================================ HW event-based analysis check... Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -collect hotspots -knob sampling-mode=hw -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ah -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/matrix Stderr: vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Error: Failed to execute sep process. Data collection is interrupted. vtune: Collection failed. vtune: Internal Error Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/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: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Error: Failed to execute sep process. Data collection is interrupted. ================================================================================ HW event-based analysis check... Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -collect uarch-exploration -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ge -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/matrix Stderr: vtune: Warning: CPU frequency data collection is not supported on this platform. vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Error: Failed to execute sep process. Data collection is interrupted. vtune: Collection failed. vtune: Internal Error Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ge/config/runsa.options HW event-based analysis check Example of analysis types: Microarchitecture Exploration Collection: Fail vtune: Warning: CPU frequency data collection is not supported on this platform. vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Error: Failed to execute sep process. Data collection is interrupted. ================================================================================ HW event-based analysis with uncore events... Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -collect memory-access -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ma -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/matrix 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: /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/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: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/matrix Stderr: vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Error: Failed to execute sep process. Data collection is interrupted. vtune: Collection failed. vtune: Internal Error Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/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: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Error: Failed to execute sep process. Data collection is interrupted. ================================================================================ HW event-based analysis with context switches... Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/vtune -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/result_th -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2022.2.0/samples/en/C++/matrix/matrix Stderr: vtune: Warning: CPU frequency data collection is not supported on this platform. vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Error: Failed to execute sep process. Data collection is interrupted. vtune: Collection failed. vtune: Internal Error Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/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: Warning: CPU frequency data collection is not supported on this platform. vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location. vtune: Error: Failed to execute sep process. Data collection is interrupted. Getting available devices: Command line: sycl-ls Exception: [Errno 2] No such file or directory: 'sycl-ls': 'sycl-ls' Checking DPC++ application as prerequisite for GPU analyses... Setting envirnoment variable: SYCL_DEVICE_FILTER=opencl:gpu Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stderr: /opt/intel/oneapi/vtune/2022.2.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libsycl.so.5: cannot open shared object file: No such file or directory Setting envirnoment variable: SYCL_DEVICE_FILTER=level_zero:gpu Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stderr: /opt/intel/oneapi/vtune/2022.2.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libsycl.so.5: cannot open shared object file: No such file or directory Setting envirnoment variable: ZES_ENABLE_SYSMAN=1 Command line: /opt/intel/oneapi/vtune/2022.2.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stderr: /opt/intel/oneapi/vtune/2022.2.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libsycl.so.5: cannot open shared object file: No such file or directory Checking DPC++ application as prerequisite for GPU analyses: Fail Unable to run DPC++ application on GPU connected to this system. If you are using an Intel GPU and want to verify profiling support for DPC++ applications, check these requirements: * Install Intel(R) GPU driver. * Install Intel(R) Level Zero GPU runtime. * Install Intel(R) oneAPI DPC++ Runtime and set the environment. The 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: /tmp/vtune-tmp-root/self-checker-2022.04.20_20.06.44/log.txt