On 27/09/2023 07:54, Andi Shyti wrote:
Hi Tvrtko,
Use the newly added drm_print_memory_stats helper to show memory
utilisation of our objects in drm/driver specific fdinfo output.
To collect the stats we walk the per memory regions object lists
and accumulate object size into the respective drm_memory_stats
categories.
v2:
* Only account against the active region.
* Use DMA_RESV_USAGE_BOOKKEEP when testing for active. (Tejas)
v3:
* Update commit text. (Aravind)
* Update to use memory regions uabi names.
Signed-off-by: Tvrtko Ursulin <[email protected]>
Cc: Aravind Iddamsetty <[email protected]>
Cc: Rob Clark <[email protected]>
Cc: Andi Shyti <[email protected]>
Cc: Tejas Upadhyay <[email protected]>
Reviewed-by: Andi Shyti <[email protected]> # v1
Reviewed-by: Aravind Iddamsetty <[email protected]> # v2
Reviewed-by: Andi Shyti <[email protected]>
Thanks guys, just the IGTs remaining now. I've just sent a respin of one
patch in that series which will hopefully fix things up.
* https://patchwork.freedesktop.org/series/124118/
First two patches is what we need to merge the kernel side, while the
rest are intel_gpu_top fixes followed by per client memory support.
Regards,
Tvrtko
