Re: [PATCH v6 0/2] accel/rocket: Report NPU usage through fdinfo
From: Gyeyoung Baek
Date: Sat Nov 21 2026 - 04:53:16 EST
Hi Sidong,
On Fri, Nov 20, 2026 at 11:12 PM Sidong Yang <sidong.yang@xxxxxxxxxx> wrote:
>
> Report how much of the NPU each client uses through fdinfo. Patch 1
> exports the runtime the scheduler already accounts per entity, and patch
> 2 uses it for rocket's drm-engine-npu key.
>
> v6: Rename the getter to drm_sched_entity_get_runtime_ns() (Maíra
> Canal). Report rdev->num_cores, the cores that are bound, as the
> capacity instead of rdev->max_cores, and skip the key once no core
> is left as a capacity of zero is not allowed (Maíra Canal). Add
> tags.
> v5: Use the entity runtime from the new drm_sched_entity_get_runtime()
> instead of a counter in rocket (Tvrtko Ursulin). Reviewed-by tags
> are not carried as the accounting changed. Based on drm-misc-next.
> v4: Single drm-engine-npu key with drm-engine-capacity-npu, and
> documentation (Tomeu Vizoso).
> v3: Add a rocket_engine_usage_create() helper (Gyeyoung Baek).
> v2: Size the per-core counters by rdev->max_cores.
>
Posted gputop support for accel devices to IGT, which shows the NPU
usage from drm-engine-npu here:
https://lore.kernel.org/igt-dev/20261121094225.628262-1-gye976@xxxxxxxxx/
Tested on RK3588 (Rock 5B+) with rocket and panthor running together.
Tested-by: Gyeyoung Baek <gye976@xxxxxxxxx>
Reviewed-by: Gyeyoung Baek <gye976@xxxxxxxxx>
--
Thanks,
Gyeyoung