Intel(R) VTune(TM) Profiler Self Check Utility Copyright (C) 2009 Intel Corporation. All rights reserved. Build Number: 627177 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/2024.0/bin64/amplxe-runss --context-value-list Stdout: targetOS: Linux OS: Linux OSBuildNumber: 0 OSBitness: 64 RootPrivileges: false isPtraceScopeLimited: true isCATSupportedByCPU: false isL3MonitoringSupportedByCPU: false isTSXAvailable: false isPTAvailable: true isHTEnabled: true fpgaOnBoard: None omniPathOnBoard: None genArchOnBoard: 12 pciClassParts: tidValuesForIO: populatedIoParts: populatedIoUnits: populatedTidValuesForIO: isSGXAvailable: false LinuxRelease: 6.5.0-21-generic is3DXPPresent: false is3DXP2LMMode: false is3DXPAppDirectMode: false IsNUMANodeWithoutCPUsPresent: false Hypervisor: None PerfmonVersion: 5 isMaxDRAMBandwidthMeasurementSupported: true preferedGpuAdapter: 0:3:0.0 gpuAdapterNameList: 0:0:2.0|Raptor Lake-S GT1 [UHD Graphics 770];0:3:0.0|DG2 [Arc A770]; gpuAdapterTileNameList: 0:0:2.0|Raptor Lake-S GT1 [UHD Graphics 770]|0,;0:3:0.0|DG2 [Arc A770]|0,; gpuOpenCLDeviceOrder: bdf gpuAdapterNameAliasList: 0:0:2.0|Raptor Lake-S GT1 [UHD Graphics 770]|GPU 0;0:3:0.0|DG2 [Arc A770]|GPU 1; isEHFIAvailable: true isPtraceAvailable: true areGpuHardwareMetricsAvailableList: 0:3:0.0|InsufficientPermissions;0:0:2.0|InsufficientPermissions; gpuPlatformIndexList: 0:3:0.0|0;0:0:2.0|0; i915Status: KernelNotPatched isFtraceAvailable: ftraceAccessError,debugfsNotAccessible isMdfEtwAvailable: false isCSwitchAvailable: no isGpuBusynessAvailable: i915TracepointsConfigOff,notAccessible isGpuWaitAvailable: no isFunctionTracingAvailable: no isIowaitTracingAvailable: no isVSyncAvailable: no HypervisorType: None isDeviceOrCredentialGuardEnabled: false isSEPDriverAvailable: false isPAXDriverLoaded: false platformType: 151 CPU_NAME: Intel(R) microarchitecture code named Raptorlake-DT PMU: alderlake referenceFrequency: 3000000000 isPStateAvailable: true isVTSSPPDriverAvailable: false isNMIWatchDogTimerRunning: true LinuxPerfCredentials: Restricted LinuxPerfCapabilities: NotAvailable LinuxPerfStackCapabilities: NotAvailable areKernelPtrsRestricted: yes isPerfPCIeMappingAvailable: false isAOCLAvailable: false isTPSSAvailable: true isPytraceAvailable: true isGENDebugInfoAvailableList: 0:3:0.0|true;0:0:2.0|true; isGTPinCollectionAvailableList: 0:3:0.0|true;0:0:2.0|true; forceShowInlines: false isEnergyCollectionSupported: true isSocwatchDriverLoaded: false isCPUSupportedBySocwatch: true isCpuThrottlingAvailable: false isIPMWatchReady: false osCountersCollectorAvailability: dstatNotAvailable l0LoaderStatus: InitializationError l0DevicesAvailable: false l0VPUDevicesAvailable: false l0GPUDevicesAvailable: false isGpuHwStallReasonCollectionAvailableList: 0:3:0.0|false;0:0:2.0|false; isXelinkAvailable: false Getting context values: OK ================================================================================ Check driver: isSEPDriverAvailable: false isPAXDriverLoaded: false Command line: lsmod Is SEP in lsmod: False The SEP driver is not available. ================================================================================ SEP version: Command line: /opt/intel/oneapi/vtune/2024.0/bin64/sep -version Stdout: Sampling Enabling Product Version: 5.43 built on Dec 15 2023 06:09:03 SEP Driver Version: PAX Driver Version: Platform type: 151 CPU name: Intel(R) microarchitecture code named Raptorlake-DT PMU: alderlake 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: /opt/intel/oneapi/vtune/2024.0/bin64/vtune -collect performance-snapshot -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ps -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/matrix Stdout: Addr of buf1 = 0x7fa7af5b5010 Offs of buf1 = 0x7fa7af5b5180 Addr of buf2 = 0x7fa7ad5b4010 Offs of buf2 = 0x7fa7ad5b41c0 Addr of buf3 = 0x7fa7ab5b3010 Offs of buf3 = 0x7fa7ab5b3100 Addr of buf4 = 0x7fa7a95b2010 Offs of buf4 = 0x7fa7a95b2140 Threads #: 16 Pthreads Matrix size: 2048 Using multiply kernel: multiply1 Execution time = 2.070 seconds Stderr: vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ps -command stop. vtune: Collection stopped. vtune: Using result path `/tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ps' vtune: Executing actions 0 % vtune: Executing actions 100 % vtune: Executing actions 100 % done Cannot find 'runsa.options' by path: /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/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/2024.0/bin64/vtune -finalize -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ps Stderr: vtune: Using result path `/tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/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-8704-linux-desktop.sc' f vtune: Executing actions 25 % Loading 'systemcollector-8704-linux-desktop.sc' f vtune: Executing actions 25 % Loading '8704-8709.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 59 % 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/2024.0/bin64/vtune -R summary -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ps Stdout: Elapsed Time: 2.084s Total Thread Count: 17 Collection and Platform Info Application Command Line: /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/matrix Operating System: 6.5.0-21-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS" Computer Name: linux-desktop Result Size: 3.6 MB Collection start time: 01:32:51 27/03/2024 UTC Collection stop time: 01:32:53 27/03/2024 UTC Collector Type: User-mode sampling and tracing CPU Name: Intel(R) microarchitecture code named Raptorlake-DT Frequency: 2.995 GHz Logical CPU Count: 32 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-david/self-checker-2024.03.27_01.32.49/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/2024.0/bin64/vtune -collect hotspots -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_tpss -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/matrix Stderr: vtune: Error: Cannot start data collection because the scope of ptrace system call is limited. To enable profiling, please set /proc/sys/kernel/yama/ptrace_scope to 0. To make this change permanent, set kernel.yama.ptrace_scope to 0 in /etc/sysctl.d/10-ptrace.conf and reboot the machine. vtune: Warning: Microarchitecture performance insights will not be available. Make sure the sampling driver is installed and enabled on your system. Instrumentation based analysis check Example of analysis types: Hotspots and Threading with user-mode sampling Collection: Fail vtune: Error: Cannot start data collection because the scope of ptrace system call is limited. To enable profiling, please set /proc/sys/kernel/yama/ptrace_scope to 0. To make this change permanent, set kernel.yama.ptrace_scope to 0 in /etc/sysctl.d/10-ptrace.conf and reboot the machine. vtune: Warning: Microarchitecture performance insights will not be available. Make sure the sampling driver is installed and enabled on your system. ================================================================================ HW event-based analysis check... Command line: /opt/intel/oneapi/vtune/2024.0/bin64/vtune -collect hotspots -knob sampling-mode=hw -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ah -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/matrix Stderr: vtune: Error: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. Cannot find 'runsa.options' by path: /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/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: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. ================================================================================ HW event-based analysis check... Command line: /opt/intel/oneapi/vtune/2024.0/bin64/vtune -collect uarch-exploration -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ge -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/matrix Stderr: vtune: Error: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. Cannot find 'runsa.options' by path: /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ge/config/runsa.options HW event-based analysis check Example of analysis types: Microarchitecture Exploration Collection: Fail vtune: Error: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. ================================================================================ HW event-based analysis with uncore events... Command line: /opt/intel/oneapi/vtune/2024.0/bin64/vtune -collect memory-access -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ma -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/matrix Stderr: vtune: Error: Cannot collect memory bandwidth data. Make sure the sampling driver is installed and enabled on your system. See the Sampling Drivers help topic for more details. Note that memory bandwidth collection is not possible if you are profiling inside a virtualized environment. Cannot find 'runsa.options' by path: /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ma/config/runsa.options HW event-based analysis with uncore events Example of analysis types: Memory Access Collection: Fail vtune: Error: Cannot collect memory bandwidth data. Make sure the sampling driver is installed and enabled on your system. See the Sampling Drivers help topic for more details. Note that memory bandwidth collection is not possible if you are profiling inside a virtualized environment. ================================================================================ HW event-based analysis with stacks... Command line: /opt/intel/oneapi/vtune/2024.0/bin64/vtune -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/matrix Stderr: vtune: Warning: Unlimited stack size (0) not allowed if the VTune Profiler sampling driver is not loaded. Stack size option will be changed to 1024 during data collection. vtune: Error: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. Cannot find 'runsa.options' by path: /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/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: Unlimited stack size (0) not allowed if the VTune Profiler sampling driver is not loaded. Stack size option will be changed to 1024 during data collection. vtune: Error: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. ================================================================================ HW event-based analysis with context switches... Command line: /opt/intel/oneapi/vtune/2024.0/bin64/vtune -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_th -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2024.0/samples/en/C++/matrix/matrix Stderr: vtune: Error: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. vtune: Warning: Cannot collect context switch data in Perf-based driverless mode if the value of /proc/sys/kernel/perf_event_paranoid is greater than 1. Cannot find 'runsa.options' by path: /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/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: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. vtune: Warning: Cannot collect context switch data in Perf-based driverless mode if the value of /proc/sys/kernel/perf_event_paranoid is greater than 1. Getting available devices: Command line: sycl-ls Exception: [Errno 2] No such file or directory: 'sycl-ls' Checking DPC++ application as prerequisite for GPU analyses... Setting envirnoment variable: ONEAPI_DEVICE_SELECTOR=opencl:gpu Command line: /opt/intel/oneapi/vtune/2024.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stdout: Address of buf1 = 0x7f9379bff010 Offset of buf1 = 0x7f9379bff180 Address of buf2 = 0x7f93793fe010 Offset of buf2 = 0x7f93793fe1c0 Address of buf3 = 0x7f9378bfd010 Offset of buf3 = 0x7f9378bfd100 Address of buf4 = 0x7f93783fc010 Offset of buf4 = 0x7f93783fc140 Using multiply kernel: multiply1 Available devices: Intel(R) Arc(TM) A770 Graphics Intel(R) UHD Graphics 770 ***** * Running on Intel(R) Arc(TM) A770 Graphics ***** No subdevices available, using the whole device ***** * Running on Intel(R) UHD Graphics 770 ***** No subdevices available, using the whole device ************ * Finished * ************ Elapsed Time: 0.386984s Stderr: SYCL_PI_TRACE[basic]: Plugin found and successfully loaded: libpi_opencl.so [ PluginVersion: 14.37.1 ] SYCL_PI_TRACE[basic]: Plugin found and successfully loaded: libpi_unified_runtime.so [ PluginVersion: 14.37.1 ] Setting envirnoment variable: ONEAPI_DEVICE_SELECTOR=level_zero:gpu Command line: /opt/intel/oneapi/vtune/2024.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stdout: Address of buf1 = 0x7f56d25ff010 Offset of buf1 = 0x7f56d25ff180 Address of buf2 = 0x7f56d1dfe010 Offset of buf2 = 0x7f56d1dfe1c0 Address of buf3 = 0x7f56d15fd010 Offset of buf3 = 0x7f56d15fd100 Address of buf4 = 0x7f56d0dfc010 Offset of buf4 = 0x7f56d0dfc140 Using multiply kernel: multiply1 Available devices: Intel(R) Arc(TM) A770 Graphics Intel(R) UHD Graphics 770 ***** * Running on Intel(R) Arc(TM) A770 Graphics ***** No subdevices available, using the whole device ***** * Running on Intel(R) UHD Graphics 770 ***** No subdevices available, using the whole device ************ * Finished * ************ Elapsed Time: 0.25866s Stderr: SYCL_PI_TRACE[basic]: Plugin found and successfully loaded: libpi_level_zero.so [ PluginVersion: 14.37.1 ] SYCL_PI_TRACE[basic]: Plugin found and successfully loaded: libpi_unified_runtime.so [ PluginVersion: 14.37.1 ] Setting envirnoment variable: ZES_ENABLE_SYSMAN=1 Command line: /opt/intel/oneapi/vtune/2024.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stdout: Address of buf1 = 0x7fce661ff010 Offset of buf1 = 0x7fce661ff180 Address of buf2 = 0x7fce659fe010 Offset of buf2 = 0x7fce659fe1c0 Address of buf3 = 0x7fce651fd010 Offset of buf3 = 0x7fce651fd100 Address of buf4 = 0x7fce649fc010 Offset of buf4 = 0x7fce649fc140 Using multiply kernel: multiply1 Available devices: Intel(R) Arc(TM) A770 Graphics Intel(R) UHD Graphics 770 ***** * Running on Intel(R) Arc(TM) A770 Graphics ***** No subdevices available, using the whole device ***** * Running on Intel(R) UHD Graphics 770 ***** No subdevices available, using the whole device ************ * Finished * ************ Elapsed Time: 0.233982s Stderr: SYCL_PI_TRACE[basic]: Plugin found and successfully loaded: libpi_level_zero.so [ PluginVersion: 14.37.1 ] SYCL_PI_TRACE[basic]: Plugin found and successfully loaded: libpi_unified_runtime.so [ PluginVersion: 14.37.1 ] Checking DPC++ application as prerequisite for GPU analyses: Ok ================================================================================ GPU HW event-based analysis with runtime tracing... Command line: /opt/intel/oneapi/vtune/2024.0/bin64/vtune -collect gpu-hotspots -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_gh -data-limit 0 -finalization-mode none -- /opt/intel/oneapi/vtune/2024.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stderr: vtune: Error: Cannot collect GPU hardware metrics due to a lack of permissions. Use root privileges (recommended) or re-configure your current permissions to make sure you are a member of the video user group and /proc/sys/dev/i915/perf_stream_paranoid value is set to 0. vtune: Error: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. GPU HW event-based analysis with runtime tracing Example of analysis types: GPU Compute/Media Hotspots (characterization mode) Collection: Fail vtune: Error: Cannot collect GPU hardware metrics due to a lack of permissions. Use root privileges (recommended) or re-configure your current permissions to make sure you are a member of the video user group and /proc/sys/dev/i915/perf_stream_paranoid value is set to 0. vtune: Error: Current OS kernel does not support driverless collection on hybrid CPUs. Consider loading the VTune Profiler sampling driver using root credentials or updating the OS kernel. vtune: Warning: Access to /proc/kallsyms file is limited. Consider changing /proc/sys/kernel/kptr_restrict to 0 to enable resolution of OS kernel and kernel module symbols. ================================================================================ GPU software event-based analysis with runtime tracing... Command line: /opt/intel/oneapi/vtune/2024.0/bin64/vtune -collect gpu-hotspots -knob profiling-mode=source-analysis -knob source-analysis=bb-latency -r /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/result_gh_src -data-limit 0 -finalization-mode none -- /opt/intel/oneapi/vtune/2024.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp Stderr: vtune: Error: Cannot start data collection because the scope of ptrace system call is limited. To enable profiling, please set /proc/sys/kernel/yama/ptrace_scope to 0. To make this change permanent, set kernel.yama.ptrace_scope to 0 in /etc/sysctl.d/10-ptrace.conf and reboot the machine. GPU software event-based analysis with runtime tracing Example of analysis types: GPU Compute/Media Hotspots (source analysis mode) Collection: Fail vtune: Error: Cannot start data collection because the scope of ptrace system call is limited. To enable profiling, please set /proc/sys/kernel/yama/ptrace_scope to 0. To make this change permanent, set kernel.yama.ptrace_scope to 0 in /etc/sysctl.d/10-ptrace.conf and reboot the machine. 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 The following analyses have failed on the system: * Hotspots and Threading with user-mode sampling * Hotspots with HW event-based sampling, HPC Performance Characterization, etc. * Microarchitecture Exploration * Memory Access * Hotspots with HW event-based sampling and call stacks * Threading with HW event-based sampling * GPU Compute/Media Hotspots (characterization mode) * GPU Compute/Media Hotspots (source analysis mode) Log location: /tmp/vtune-tmp-david/self-checker-2024.03.27_01.32.49/log.txt