Panthor DRM client usage stats implementation¶

The drm/Panthor driver implements the DRM client usage stats specification asdocumented inDRM client usage stats.

Example of the output showing the implemented key value pairs and entirety ofthe currently possible format options:

::

pos: 0flags: 02400002mnt_id: 29ino: 491drm-driver: panthordrm-client-id: 10drm-engine-panthor: 111110952750 nsdrm-cycles-panthor: 94439687187drm-maxfreq-panthor: 1000000000 Hzdrm-curfreq-panthor: 1000000000 Hzpanthor-resident-memory: 10396 KiBpanthor-active-memory: 10396 KiBdrm-total-memory: 16480 KiBdrm-shared-memory: 0drm-active-memory: 16200 KiBdrm-resident-memory: 16480 KiBdrm-purgeable-memory: 0

Possibledrm-engine- key names are:panthor.drm-curfreq- values convey the current operating frequency for that engine.

Users must bear in mind that engine and cycle sampling are disabled by default,because of power saving concerns.fdinfo users and benchmark applications whichquery the fdinfo file must make sure to toggle the job profiling status of thedriver by writing into the appropriate sysfs node:

echo <N> > /sys/bus/platform/drivers/panthor/[a-f0-9]*.gpu/profiling

WhereN is a bit mask where cycle and timestamp sampling are respectivelyenabled by the first and second bits.

Possiblepanthor-*-memory keys are:active andresident.These values convey the sizes of the internal driver-owned shmem BO’s thataren’t exposed to user-space through a DRM handle, like queue ring buffers,sync object arrays and heap chunks. Because they are all allocated and pinnedat creation time, onlypanthor-resident-memory is necessary to tell us theirsize.panthor-active-memory shows the size of kernel BO’s associated withVM’s and groups currently being scheduled for execution by the GPU.