• State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 120 subscribers
  • Views 3429 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Streamline with Mali400 - There are no mali devices to create readers

MartinH

Hello Forum,

I am running the Xilinx ZynqMP+ platform with Cortex-A53 and Mali-400MP2. When trying to run performance analysis with ARM Streamline 7.8.0 using gator daemon prebuild 7.8.0 I get the following error:

./gatord -d
[...]
[4605.8953405] INFO: MaliHwCntrDriver(mali_userspace/MaliHwCntrDriver.cpp:20): There are no mali devices to create readers
[...]

Root cause is that my device only has a "/dev/mali" entry, but gatord searches for "/dev/mali0" (and higher). If I create a symlink I get one step further and get this error message:

ln -s /dev/mali /dev/mali0
./gatord -d
[...]
[3240.0390221] INFO: probe(mali_userspace/MaliDeviceApi.cpp:233): MaliDeviceApi: Failed setting ABI version ioctl - may be r21p0 or later...
[3240.0393474] INFO: probe(mali_userspace/MaliDeviceApi.cpp:535): MaliDeviceApi: Failed setting ABI version ioctl for JM based ddk. Trying with CSF ioctl version
[3240.0393969] INFO: probe(mali_userspace/MaliDeviceApi.cpp:540): MaliDeviceApi: Failed setting ABI version ioctl for CSF based ddk
[3240.0399230] INFO: MaliHwCntrDriver(mali_userspace/MaliHwCntrDriver.cpp:20): There are no mali devices to create readers
[...]

Checking with lsmod the kernel module "mali" is successfully loaded, and tools like glmark2 run without troubles.

root@device:/# lsmod
Module                  Size  Used by
[...]
mali                  356352  0
[...]

As this Xilinx chip still uses Mali drivers DX910-SW-99002-r9p0-01rel0 from 2018, I also tried to go back in time and use gatord prebuild 6.9 (release 2019.0) and 6.8 (release 2018.0). Same problem, slightly different error messages.

Any clues what is going wrong here? Thanks!

Parents
  • 0 in reply to Peter Harris

    To make matters worse, gator.ko sources in version 6.8 need some kernel API, that has changed in kernel 4.14.

    The same applies to the mali kernel driver (mali.ko, DX910-SW-99002-r9p0-01rel0), the Xilinx reference distribution for this chip is already on linux kernel 5.x, and Xilinx has to patch the mali.ko sources to still run this version.

    So I get the feeling I have to enable Mali400_profiling in mali.ko, and then fix gator.ko to run with the new kernel...

Reply
  • 0 in reply to Peter Harris

    To make matters worse, gator.ko sources in version 6.8 need some kernel API, that has changed in kernel 4.14.

    The same applies to the mali kernel driver (mali.ko, DX910-SW-99002-r9p0-01rel0), the Xilinx reference distribution for this chip is already on linux kernel 5.x, and Xilinx has to patch the mali.ko sources to still run this version.

    So I get the feeling I have to enable Mali400_profiling in mali.ko, and then fix gator.ko to run with the new kernel...

Children
No data