On Tue, 22 Sep 2026 10:24:49 -0300, Maíra Canal wrote:
> The V3D core has a single set of performance counters. So that a perfmon
> only counts the jobs it is attached to, a job carrying a non-global
> perfmon waits for every job still in flight, and while it is in flight
> every later job waits for it. Knowing what is in flight requires every
> job to merge its finished fence into a per-queue accumulator.
>
> That accumulator is maintained unconditionally, so a client pays a fence
> merge on every job even when no dependency can ever be built out of it.
> This series turns the bookkeeping off in the two cases where that holds:
>
> [...]
Applied, thanks!
[1/2] drm/v3d: Skip perfmon serialization while the device has no perfmon
commit: 537684e232fb590659a1448fca8a23d77d948ab1
[2/2] drm/v3d: Skip perfmon serialization while a global perfmon is set
commit: 6e375de99d0c420169481fcd36064177ab55b09d
Best regards,
- Maíra
