[PATCH 2/3] drm/amdgpu: report more amdgpu_fence_info v2
Christian König
christian.koenig at amd.com
Tue Oct 17 07:03:19 UTC 2017
Am 17.10.2017 um 08:37 schrieb Pixel Ding:
> From: pding <Pixel.Ding at amd.com>
>
> Only for GFX ring. This can help checking MCBP feature.
>
> v2: report more fence offs.
>
> The fence at the end of the frame will indicate the completion status.
> If the frame completed normally, the fence is written to the address
> given in the EVENT_WRITE_EOP packet. If preemption occurred in the
> previous IB the address is adjusted by 2 DWs. If work submitted in the
> frame was reset before completion, the fence address is adjusted by
> four DWs. In the case that preemption occurred, and before preemption
> completed a reset was initiated, the address will be adjusted with six
> DWs
>
> Signed-off-by: pding <Pixel.Ding at amd.com>
Reviewed-by: Christian König <christian.koenig at amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> index 09d5a5c..688740e 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> @@ -645,6 +645,19 @@ static int amdgpu_debugfs_fence_info(struct seq_file *m, void *data)
> atomic_read(&ring->fence_drv.last_seq));
> seq_printf(m, "Last emitted 0x%08x\n",
> ring->fence_drv.sync_seq);
> +
> + if (ring->funcs->type != AMDGPU_RING_TYPE_GFX)
> + continue;
> +
> + /* set in CP_VMID_PREEMPT and preemption occurred */
> + seq_printf(m, "Last preempted 0x%08x\n",
> + le32_to_cpu(*(ring->fence_drv.cpu_addr + 2)));
> + /* set in CP_VMID_RESET and reset occurred */
> + seq_printf(m, "Last reset 0x%08x\n",
> + le32_to_cpu(*(ring->fence_drv.cpu_addr + 4)));
> + /* Both preemption and reset occurred */
> + seq_printf(m, "Last both 0x%08x\n",
> + le32_to_cpu(*(ring->fence_drv.cpu_addr + 6)));
> }
> return 0;
> }
More information about the amd-gfx
mailing list