From: "Christian König" <christian.koenig@amd.com>
To: Sunil Khatri <sunil.khatri@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Shashank Sharma <shashank.sharma@amd.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: add ring buffer information in devcoredump
Date: Mon, 11 Mar 2024 14:59:27 +0100 [thread overview]
Message-ID: <9e1dbcbc-f00e-417c-995e-d9c539292e03@amd.com> (raw)
In-Reply-To: <20240311122212.13713-1-sunil.khatri@amd.com>
Am 11.03.24 um 13:22 schrieb Sunil Khatri:
> Add relevant ringbuffer information such as
> rptr, wptr, ring name, ring size and also
> the ring contents for each ring on a gpu reset.
>
> Signed-off-by: Sunil Khatri <sunil.khatri@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_reset.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_reset.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_reset.c
> index 6d059f853adc..1992760039da 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_reset.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_reset.c
> @@ -215,6 +215,27 @@ amdgpu_devcoredump_read(char *buffer, loff_t offset, size_t count,
> fault_info->status);
> }
>
> + drm_printf(&p, "Ring buffer information\n");
> + for (int i = 0; i < coredump->adev->num_rings; i++) {
> + int j = 0;
> + struct amdgpu_ring *ring = coredump->adev->rings[i];
> +
> + drm_printf(&p, "ring name: %s\n", ring->name);
> + drm_printf(&p, "Rptr: 0x%llx Wptr: 0x%llx\n",
> + amdgpu_ring_get_rptr(ring) & ring->buf_mask,
> + amdgpu_ring_get_wptr(ring) & ring->buf_mask);
Don't apply the mask here. We do have some use cases where the rptr and
wptr are outside the ring buffer.
> + drm_printf(&p, "Ring size in dwords: %d\n",
> + ring->ring_size / 4);
Rather print the mask as additional value here.
> + drm_printf(&p, "Ring contents\n");
> + drm_printf(&p, "Offset \t Value\n");
> +
> + while (j < ring->ring_size) {
> + drm_printf(&p, "0x%x \t 0x%x\n", j, ring->ring[j/4]);
> + j += 4;
> + }
> + drm_printf(&p, "Ring dumped\n");
That seems superfluous.
Regards,
Christian.
> + }
> +
> if (coredump->reset_vram_lost)
> drm_printf(&p, "VRAM is lost due to GPU reset!\n");
> if (coredump->adev->reset_info.num_regs) {
next prev parent reply other threads:[~2024-03-11 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 12:22 Sunil Khatri
2024-03-11 13:59 ` Christian König [this message]
2024-03-11 14:48 ` Khatri, Sunil
2024-03-11 16:27 ` Christian König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e1dbcbc-f00e-417c-995e-d9c539292e03@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shashank.sharma@amd.com \
--cc=sunil.khatri@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®