Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
5334 Discussions

GPU load details not visible

sreerag
Employee
276 Views

Iam using the Vtune profiler on below CPU and it is not showing the GPU load details when ran with the  performance-snapshot or with gpu-hotspots

 

CPU: Intel(R) Core(TM) Ultra X7 358H

Vtune version: Intel(R) VTune(TM) Profiler 2026.0.0 (build 631999) Command Line Tool

OS:  Ubuntu 24.04.3 LTS

0 Kudos
3 Replies
Svetlana_K_Intel
Employee
219 Views

@sreerag  do you see any errors? are the gfx drivers for Intel® Arc™ B390 GPU installed according to the recommendations? https://dgpu-docs.intel.com/overview/supported-hardware/xe-driver-gpus.html 

0 Kudos
sreerag
Employee
200 Views

I am not encountering any errors when running VTune or APS. However, when I ran the VTune Self Checker, it reported some errors. I have attached the logs for reference.

To further verify the DPC++ GPU setup, I ran a C++ test program. The application executed successfully, and I was able to retrieve the expected GPU driver details. 

Code:- 

#include <sycl/sycl.hpp>
#include <iostream>

int main()
{
    sycl::queue q{sycl::gpu_selector_v};

    std::cout << q.get_device()
                     .get_info<sycl::info::device::name>()
              << std::endl;

    return 0;
}

 

Output:- 

sdp@sdp:~/sreerag$ icpx -fsycl test_gpu.cpp -o test_gpu
sdp@sdp:~/sreerag$ ONEAPI_DEVICE_SELECTOR=level_zero:gpu ./test_gpu
Intel(R) Arc(TM) B390 GPU

 

0 Kudos
Svetlana_K_Intel
Employee
161 Views

from self-check I'm seeing 2 problems: 1st it says vtune sampling driver is loaded with "wrong permissions" - I'm suspecting it means it's loaded for default 'vtune' group, and the user is not in this group... anyways it suggests looking into this help page to make sure drivers are installed correctly https://www.intel.com/content/www/us/en/docs/vtune-profiler/user-guide/2025-1/build-install-sampling-drivers-for-linux-targets.html
the second problem is 'Error: Cannot stop collection of GPU events' - that one is most probably resulting in no GPU-related info. here our diagnostics could be better actually, but for the start, can you please verify if you ran the `prepare-gpu-hardware-metrics.sh` script with sudo permissions before running vtune? it sets the needed paranoids and makes sure the user is in the groups needed to deal with gpu.

0 Kudos
Reply