AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <Trigger.Huang@amd.com>
To: <amd-gfx@lists.freedesktop.org>
Cc: <sunil.khatri@amd.com>, <alexander.deucher@amd.com>,
	Trigger Huang <Trigger.Huang@amd.com>
Subject: [PATCH 0/3] Improve the dev coredump
Date: Thu, 15 Aug 2024 19:38:33 +0800	[thread overview]
Message-ID: <20240815113836.399377-1-Trigger.Huang@amd.com> (raw)

From: Trigger Huang <Trigger.Huang@amd.com>

The current dev coredump implementation sometimes cannot fully satisfy customer's requirements due to:
1, The enablement of dev coredump is under the control of gpu_recovery. Customer can not do dev coredump with gpu_recovery disabled
2, When job timeout happened, the dump GPU status will be happened after a lot of operations, like soft_reset. The concern here is that the status is not so close to the real GPU's error status.

So we introduced a new solution
1, A new parameter, gpu_coredump, is added to decouple the coredump and gpu reset
2, Do the coredump immediately after a job timeout

Trigger Huang (3):
  drm/amdgpu: Add gpu_coredump parameter
  drm/amdgpu: introduce new API for GPU core dump
  drm/amdgpu: Change the timing of doing coredump

 drivers/gpu/drm/amd/amdgpu/amdgpu.h        |  3 +
 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 89 ++++++++++++++++++----
 drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c    |  8 ++
 drivers/gpu/drm/amd/amdgpu/amdgpu_job.c    | 10 +++
 4 files changed, 97 insertions(+), 13 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-08-15 11:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 11:38 Trigger.Huang [this message]
2024-08-15 11:38 ` [PATCH 1/3] drm/amdgpu: Add gpu_coredump parameter Trigger.Huang
2024-08-15 16:01   ` Alex Deucher
2024-08-16  6:36     ` Huang, Trigger
2024-08-16  6:39       ` Huang, Trigger
2024-08-16 13:43       ` Alex Deucher
2024-08-19  9:29         ` Huang, Trigger
2024-08-15 11:38 ` [PATCH 2/3] drm/amdgpu: introduce new API for GPU core dump Trigger.Huang
2024-08-15 11:38 ` [PATCH 3/3] drm/amdgpu: Change the timing of doing coredump Trigger.Huang
2024-08-15 16:09   ` Alex Deucher
2024-08-16  6:37     ` Huang, Trigger

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=20240815113836.399377-1-Trigger.Huang@amd.com \
    --to=trigger.huang@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --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