having a look back at the linux source...If you tell me what the api was that you tested that didn't expose the counters I can check if it now exposes the counters.
But Igalia develop the mesa driver, I'm not too familiar with the inner workings.
No doubt if things have changed the changes will be visible through the mesa or kernel git trees.
drivers/gpu/drm/vc4/vc4_perfmon.c implements the vc4 v3d profiling
vc4_gem.c calls bits of it at various points in the rendering, so it can reset and capture the hw counters
"DRM_IOCTL_DEF_DRV(VC4_PERFMON_GET_VALUES, vc4_perfmon_get_values_ioctl, DRM_RENDER_ALLOW)" over in vc4_drv.c then lets userland capture the results
and there is a drivers/gpu/drm/v3d/v3d_perfmon.c that seems to follow nearly the identical structure
git says:
Code:
commit 26a4dc29b74a137f45665089f6d3d633fcc9b662Author: Juan A. Suarez Romero <jasuarez@igalia.com>Date: Tue Jun 8 13:15:41 2021 +0200 drm/v3d: Expose performance counters to userspace The V3D engine has several hardware performance counters that can of interest for userspace performance analysis tools.so that 3 year gap, would explain why i dont remember seeing that support
Statistics: Posted by cleverca22 — Fri Jan 26, 2024 3:49 pm