Intel(R) VTune(TM) Profiler Self Check Utility
Copyright (C) 2009 Intel Corporation. All rights reserved.
Build Number: 629235

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/2025.0/bin64/amplxe-runss --context-value-list
Stdout:
  targetOS: Linux
  OS: Linux
  OSBuildNumber: 0
  OSBitness: 64
  RootPrivileges: false
  isPtraceScopeLimited: false
  isCATSupportedByCPU: true
  isL3CATAvailable: false
  isL2CATAvailable: false
  isL3MonitoringSupportedByCPU: false
  isTSXAvailable: false
  isPTAvailable: true
  isHTEnabled: false
  fpgaOnBoard: Discrete
  omniPathOnBoard: None
  genArchOnBoard: 12
  pciClassParts:
  tidValuesForIO:
  populatedIoParts:
  populatedIoUnits:
  populatedTidValuesForIO:
  memoryType: Unknown
  isSGXAvailable: false
  LinuxRelease: 6.8.0-52-generic
  is3DXPPresent: false
  is3DXP2LMMode: false
  is3DXPAppDirectMode: false
  IsNUMANodeWithoutCPUsPresent: false
  Hypervisor: None
  PerfmonVersion: 6
  isMaxDRAMBandwidthMeasurementSupported: true
  preferedGpuAdapter: 0:0:2.0
  gpuAdapterNameList: 0:0:2.0|Arrow Lake-U [Intel Graphics];
  gpuAdapterTileNameList: 0:0:2.0|Arrow Lake-U [Intel Graphics]|0,;
  gpuOpenCLDeviceOrder: bdf
  gpuAdapterNameAliasList: 0:0:2.0|Arrow Lake-U [Intel Graphics]|GPU 0;
  isEHFIAvailable: true
  isPtraceAvailable: true
  areGpuHardwareMetricsAvailableList: 0:0:2.0|InsufficientPermissions;
  gpuPlatformIndexList: 0:0:2.0|0;
  i915Status: KernelNotPatched
  GPUUserGroups: render
  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: 168
  CPU_NAME: Intel(R) microarchitecture code named Arrowlake-S
  PMU: arrowlake
  referenceFrequency: 3700000000
  isPStateAvailable: true
  isVTSSPPDriverAvailable: true
  isNMIWatchDogTimerRunning: true
  LinuxPerfCredentials: Restricted
  LinuxPerfCapabilities: NotAvailable
  LinuxPerfStackCapabilities: NotAvailable
  areKernelPtrsRestricted: yes
  LinuxPerfMuxIntervalMs: 1
  isPerfPCIeMappingAvailable: false
  isAOCLAvailable: false
  isTPSSAvailable: true
  isPytraceAvailable: true
  isGENDebugInfoAvailableList: 0:0:2.0|true;
  isGTPinCollectionAvailableList: 0:0:2.0|true;
  forceShowInlines: false
  isEnergyCollectionSupported: false
  isSocwatchDriverLoaded: false
  isCPUSupportedBySocwatch: true
  isCpuThrottlingAvailable: false
  isIPMWatchReady: false
  osCountersCollectorAvailability: dstatNotAvailable
  l0LoaderStatus: LibNotFound
  l0DevicesAvailable: false
  l0VPUDevicesAvailable: false
  l0GPUDevicesAvailable: false
  isGpuHwStallReasonCollectionAvailableList: 0:0:2.0|false;
  isXelinkAvailable: false

Getting context values: OK
================================================================================
Check driver:
isSEPDriverAvailable: false
isPAXDriverLoaded: false
Command line:
lsmod
Stdout:
  sep5                 3538944  0
  socperf3             1236992  1 sep5
  pmt_telemetry          16384  3 sep5,socwatch2_15,intel_pmc_core

Is SEP in lsmod: True
vtune: Warning: VTune Profiler driver with insufficient permission is detected on the system.
vtune: Warning: Consider setting proper driver permissions (see the "Sampling Drivers" help topic).
vtune: Warning: Otherwise, the driverless collection with limited analysis support will be enabled by default.
================================================================================
SEP version:
Command line:
/opt/intel/oneapi/vtune/2025.0/bin64/sep -version
Stdout:
  Sampling Enabling Product Version: 5.50 Beta built on Nov 12 2024 11:04:55
  SEP Driver Version: PAX Driver Version: Platform type: 168
  CPU name: Intel(R) microarchitecture code named Arrowlake-S
  PMU: arrowlake
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/2025.0/bin64/vtune -collect performance-snapshot -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_ps -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/matrix
Stdout:
  Addr of buf1 = 0x7102f3200010
  Offs of buf1 = 0x7102f3200180
  Addr of buf2 = 0x7102f1000010
  Offs of buf2 = 0x7102f10001c0
  Addr of buf3 = 0x7102eee00010
  Offs of buf3 = 0x7102eee00100
  Addr of buf4 = 0x7102ecc00010
  Offs of buf4 = 0x7102ecc00140
  Threads #: 16 Pthreads
  Matrix size: 2048
  Using multiply kernel: multiply1
  Execution time = 1.602 seconds
Stderr:
  vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_ps -command stop.
  vtune: Collection stopped.
  vtune: Using result path `/tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_ps'
  
  vtune: Executing actions  0 %
  vtune: Executing actions 100 %
  vtune: Executing actions 100 % done

Cannot find 'runsa.options' by path: /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/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/2025.0/bin64/vtune -finalize -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_ps
Stderr:
  vtune: Using result path `/tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/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-20875-boris-desk.sc' fil
  vtune: Executing actions 25 % Loading 'systemcollector-20875-boris-desk.sc' fil
  vtune: Executing actions 25 % Loading '20875-20880.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 100 % Saving the result
  vtune: Executing actions 100 % done

Finalization: Ok
--------------------------------------------------------------------------------
Command line:
/opt/intel/oneapi/vtune/2025.0/bin64/vtune -R summary -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_ps
Stdout:
  Elapsed Time: 1.624s
  Total Thread Count: 17
  Collection and Platform Info
  Application Command Line: /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/matrix
  Operating System: 6.8.0-52-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.04 DISTRIB_CODENAME=noble DISTRIB_DESCRIPTION="Ubuntu 24.04.1 LTS"
  Computer Name: boris-desk
  Result Size: 3.6 MB
  Collection start time: 05:37:11 21/03/2025 UTC
  Collection stop time: 05:37:13 21/03/2025 UTC
  Collector Type: User-mode sampling and tracing
  CPU
  Name: Intel(R) microarchitecture code named Arrowlake-S
  Frequency: 3.686 GHz
  Logical CPU Count: 24
  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 <my_result_dir>.
  Alternatively, you may view the report in the csv format: vtune -report
  <report_name> -format=csv.
Stderr:
  vtune: Using result path `/tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/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/2025.0/bin64/vtune -collect hotspots -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_tpss -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/matrix
Stdout:
  Addr of buf1 = 0x7c3c9bc00010
  Offs of buf1 = 0x7c3c9bc00180
  Addr of buf2 = 0x7c3c99a00010
  Offs of buf2 = 0x7c3c99a001c0
  Addr of buf3 = 0x7c3c97800010
  Offs of buf3 = 0x7c3c97800100
  Addr of buf4 = 0x7c3c95600010
  Offs of buf4 = 0x7c3c95600140
  Threads #: 16 Pthreads
  Matrix size: 2048
  Using multiply kernel: multiply1
  Execution time = 1.580 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-boris/self-checker-2025.03.21_05.37.09/result_tpss -command stop.
  vtune: Collection stopped.
  vtune: Using result path `/tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/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/2025.0/bin64/vtune -finalize -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_tpss
Stderr:
  vtune: Using result path `/tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/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-20960-boris-desk.sc' fil
  vtune: Executing actions 25 % Loading 'systemcollector-20960-boris-desk.sc' fil
  vtune: Executing actions 25 % Loading '20960-20965.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 41 % Resolving information for `libtpsstool.so'
  vtune: Warning: Cannot locate debugging information for file `/opt/intel/oneapi/vtune/2025.0/lib64/libtpsstool.so'.
  
  vtune: Executing actions 43 % Resolving information for `libtpsstool.so'
  vtune: Executing actions 45 % Resolving information for `libtpsstool.so'
  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 64 % Precomputing frequently used data
  vtune: Executing actions 65 % Precomputing frequently used data
  vtune: Executing actions 68 % 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:
/opt/intel/oneapi/vtune/2025.0/bin64/vtune -limit 5 -format csv -csv-delimiter comma -report hotspots -group-by function -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/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,19.049699,19.049699,0.0,0.0,matrix,multiply1,multiply.c,0x1d10
  __GI___libc_free,0.010000,0.010000,0.0,0.0,libc.so.6,__GI___libc_free,malloc.c,0xadd30
  init_arr,0.010000,0.010000,0.0,0.0,matrix,init_arr,matrix.c,0x14e1
Stderr:
  vtune: Using result path `/tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/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/2025.0/bin64/vtune -collect hotspots -knob sampling-mode=hw -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_ah -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.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-boris/self-checker-2025.03.21_05.37.09/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/2025.0/bin64/vtune -collect uarch-exploration -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_ge -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.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-boris/self-checker-2025.03.21_05.37.09/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/2025.0/bin64/vtune -collect memory-access -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_ma -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.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-boris/self-checker-2025.03.21_05.37.09/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/2025.0/bin64/vtune -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.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: Error: Unlimited stack size (0) not allowed in driverless mode.

Cannot find 'runsa.options' by path: /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/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: 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: Error: Unlimited stack size (0) not allowed in driverless mode.

================================================================================
HW event-based analysis with context switches...
Command line:
/opt/intel/oneapi/vtune/2025.0/bin64/vtune -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/result_th -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.0/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.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: Context switch data cannot be collected in the current driverless mode if the kernel version is less than 4.3 or /proc/sys/kernel/perf_event_paranoid value is greater than 1. Update your system configuration for  or consider switching to the Intel sampling driver by setting an unlimited (0) value for the Stack size option.

Cannot find 'runsa.options' by path: /tmp/vtune-tmp-boris/self-checker-2025.03.21_05.37.09/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: Context switch data cannot be collected in the current driverless mode if the kernel version is less than 4.3 or /proc/sys/kernel/perf_event_paranoid value is greater than 1. Update your system configuration for  or consider switching to the Intel sampling driver by setting an unlimited (0) value for the Stack size option.

vtune: Warning: VTune Profiler driver with insufficient permission is detected on the system.
vtune: Warning: Consider setting proper driver permissions (see the "Sampling Drivers" help topic).
vtune: Warning: Otherwise, the driverless collection with limited analysis support will be enabled by default.

Getting available devices:
Command line:
sycl-ls
Stdout:
  [opencl:cpu][opencl:0] Intel(R) OpenCL, Intel(R) Core(TM) Ultra 9 285K OpenCL 3.0 (Build 0) [2024.18.12.0.05_160000]

Checking DPC++ application as prerequisite for GPU analyses...
Setting envirnoment variable:
ONEAPI_DEVICE_SELECTOR=opencl:gpu
Command line:
/opt/intel/oneapi/vtune/2025.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp
Stdout:
  Address of buf1 = 0x7fdbf9600010
  Offset of buf1 = 0x7fdbf9600180
  Address of buf2 = 0x7fdbf8c00010
  Offset of buf2 = 0x7fdbf8c001c0
  Address of buf3 = 0x7fdbf8200010
  Offset of buf3 = 0x7fdbf8200100
  Address of buf4 = 0x7fdbf7800010
  Offset of buf4 = 0x7fdbf7800140
  Using multiply kernel: multiply1
Stderr:
  SYCL_PI_TRACE has been removed use SYCL_UR_TRACE instead

Setting envirnoment variable:
ONEAPI_DEVICE_SELECTOR=level_zero:gpu
Command line:
/opt/intel/oneapi/vtune/2025.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp
Stdout:
  Address of buf1 = 0x751271200010
  Offset of buf1 = 0x751271200180
  Address of buf2 = 0x751270800010
  Offset of buf2 = 0x7512708001c0
  Address of buf3 = 0x75126fe00010
  Offset of buf3 = 0x75126fe00100
  Address of buf4 = 0x75126f400010
  Offset of buf4 = 0x75126f400140
  Using multiply kernel: multiply1
Stderr:
  SYCL_PI_TRACE has been removed use SYCL_UR_TRACE instead

Setting envirnoment variable:
ZES_ENABLE_SYSMAN=1
Command line:
/opt/intel/oneapi/vtune/2025.0/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp
Stdout:
  Address of buf1 = 0x7c98b4c00010
  Offset of buf1 = 0x7c98b4c00180
  Address of buf2 = 0x7c98b4200010
  Offset of buf2 = 0x7c98b42001c0
  Address of buf3 = 0x7c98b3800010
  Offset of buf3 = 0x7c98b3800100
  Address of buf4 = 0x7c98b2e00010
  Offset of buf4 = 0x7c98b2e00140
  Using multiply kernel: multiply1
Stderr:
  SYCL_PI_TRACE has been removed use SYCL_UR_TRACE instead

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-boris/self-checker-2025.03.21_05.37.09/log.txt