[PATCH i-g-t] lib/igt_drm_fdinfo: Handle (somewhat) amdgpu memory stats

[Lucas De Marchi]

On Mon, Sep 09, 2024 at 04:38:31PM GMT, Tvrtko Ursulin wrote:
>
>On 09/09/2024 16:27, Kamil Konieczny wrote:
>>Hi Lucas,
>>On 2024-09-05 at 07:55:14 -0500, Lucas De Marchi wrote:
>>>On Wed, Sep 04, 2024 at 04:59:19PM GMT, Tvrtko Ursulin wrote:
>>>>From: Tvrtko Ursulin <tvrtko.ursulin at igalia.com>
>>>>
>>>>Code so far only handles the clients using the common DRM helper.
>>>>
>>>>Handle the amdgpu driver which uses a slightly different set of keys. More
>>>>specifically, outputs drm-memory-<region> instead of drm-resident-<region>.
>>>>
>>>>With this added gputop starts showing resident memory usage for amdgpu.
>>>>
>>>>v2:
>>>>* Semantics of amdgpu drm-memory- are like resident, not total.
>>>>
>>>>Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin at igalia.com>
>>>>Cc: Alex Deucher <alexander.deucher at amd.com>
>>>>Cc: Christian König <christian.koenig at amd.com>
>>>>Cc: Rob Clark <robdclark at chromium.org>
>>>>Cc: Lucas De Marchi <lucas.demarchi at intel.com>
>>>>Reviewed-by: Lucas De Marchi <lucas.demarchi at intel.com> # v1
>>>
>>>my r-b stands.
>>>
>>>Lucas De Marchi
>>
>>Could you look into a regression reported for XeFULL:
>>
>>igt at xe_drm_fdinfo@utilization-single-full-load-destroy-queue:
>>
>>https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11696/shard-lnl-2/igt@xe_drm_fdinfo@utilization-single-full-load-destroy-queue.html
>
>Me? I am not well equipped for that. But I strongly doubt it is 
>related since this patch only adds parsing of drm-memory- and this IGT 
>appears to have failed on an engine busyness test.

I just replied with more details and agree it's not related to your
changes.

Lucas De Marchi