Am 22.04.25 um 15:23 schrieb Prike Liang:
> This debug dump will help on debugging the evf attached gem obj fence
> related issue.
>
> Signed-off-by: Prike Liang <prike.li...@amd.com>
Reviewed-by: Christian König <christian.koe...@amd.com> for both patches.
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> index d09db052e282..1e73ce30d4d7 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> @@ -1675,7 +1675,11 @@ u64 amdgpu_bo_print_info(int id, struct amdgpu_bo *bo,
> struct seq_file *m)
> amdgpu_bo_print_flag(m, bo, VRAM_CONTIGUOUS);
> amdgpu_bo_print_flag(m, bo, VM_ALWAYS_VALID);
> amdgpu_bo_print_flag(m, bo, EXPLICIT_SYNC);
> -
> + /* Add the gem obj resv fence dump*/
> + if (dma_resv_trylock(bo->tbo.base.resv)) {
> + dma_resv_describe(bo->tbo.base.resv, m);
> + dma_resv_unlock(bo->tbo.base.resv);
> + }
> seq_puts(m, "\n");
>
> return size;
