performance studio tell that : https://developer.arm.com/Tools%20and%20Software/Arm%20Development%20Studio#Supported-Devices
streamline can collect openCL timeline .
but when i select counters it warn that : GPU frequency counters not available for GPU.
it can not capture mali timeline
streamline user guild tell that :"Mali Timeline Events requires your device to Have a Mali device driver version r40p0"
i get my driver version through openCL clGetDeviceInfo(device CL_DRIVER_VERSION) it return my device driver version is 3.0
and clGetDeviceInfo(Device cl_DEVICE_NAME) it return my device name : Mali-G610 r0p0
it seem that my device driver is dissatisfy.
so how should i do can profile my openCL code .
The value returned for CL_DRIVER_VERSION is the version number for just the OpenCL driver implementation. The version number you found in the Streamline User Guide refers to the overall GPU driver. If you have Chrome installed you can browse to "chrome://gpu" and check the string next to "GPU0", in the "Driver Information" table. Another way of doing this, if you have access to the dmesg command, is to run 'dmesg | grep DDK' and see if the version string is printed there. Please note that driver version r43p0 is required to display OpenCL events in the Mali Timeline.
If your driver does not support OpenCL timeline events you may still be able to profile your workload by using the other Mali hardware counters in Streamline.
Using CL_DEVICE_VERSION should give you the rXpY version number, in addition to other version information.
thank you for your reply. I had inquired that the driver version of my GPU is satisfy the tool requirement.
and streamline and offline complier are all state that they support Mali-G610 in openCL profiler.
https://developer.arm.com/Tools%20and%20Software/Arm%20Development%20Studio#Supported-Devices
and offline compiler guild tell me that they support Mali-G610
but when i run the tool they all tell me that they do not support collect mali time line and openCL mode.
so could you tell me an confirmed information that :" is performance studio support Mali-G610".
I still doubt that I improper use these tool.
thank you for your reply
could you tell me what other profile tool could support my work.
and i had try command dmesg | grep DDk, but my device return NULL.
and could you tell if openCL mode support Mali-G710
Please let us know what value is returned from clGetDeviceInfo(CL_DEVICE_VERSION).
Also, specifically what device and OS are you running on? For CSF GPUs OpenCL timeline support relies on the Android Perfetto trace daemon for data transport, so it needs a device where this is available and running.
thank you for your reply.
the value of "CL_DEVICE_VERSION" is OpenCL 3.0 v1.g11p0-01eac0.261843d4a0421aa5b9fla9c5e69b0816。
i have two device
one device is vivo pad2 , its OS is originOS 3 base on android 13 .its SOC is Dimensity 9000 with Mali-G710
and my second device is an Embedded Development Board ,its os is android 12 . it soc is Rockchip 3588 with Mali-G610.
they all can not collect openCL timeline.
i also had read that G610 is not support by mobile studio
https://community.arm.com/support-forums/f/armds-forum/54310/how-to-configure-opencl-mode-in-streamline/180467#180467.
so try performance studio ,and it tell that https://developer.arm.com/Tools%20and%20Software/Arm%20Development%20Studio#Supported-Devices ,performance studio support openCL mode on Mali G610.
I don't have access to this specific Vivo device, but they have disabled the Perfetto trace daemon by default on a few of the other devices we use. Try enabling it by running:
adb shell setprop persist.traced.enable 1
... although I don't know if it will work. There is a chance they may completely removed the Perfetto components if it's not enabled by default.
Your dev board will need to include the Perfetto compoenents, and you will need to ensure traced is running before you try to capture a profile.
HTH,
Pete
i had try
but i does not work.
and i sure that , there is perfetto compoenents within my board,but I can't guarantee that the perfetto component will work when I do the profile.