From: "Christian König" <christian.koenig@amd.com>
To: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/6] drm/amdgpu: move devcoredump generation to a worker
Date: Tue, 3 Mar 2026 10:40:20 +0100 [thread overview]
Message-ID: <03f173aa-eb64-43e9-aa1a-570b3dce4b9a@amd.com> (raw)
In-Reply-To: <20260226093727.2584-2-pierre-eric.pelloux-prayer@amd.com>
On 2/26/26 10:37, Pierre-Eric Pelloux-Prayer wrote:
> Update the way drm_coredump_printer is used based on its documentation
> and Xe's code: the main idea is to generate the final version in one go
> and then use memcpy to return the chunks requested by the caller of
> amdgpu_devcoredump_read.
>
> The generation is moved to a separate worker thread.
>
> This cuts the time to copy the dump from 40s to ~0s on my machine.
>
> Signed-off-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>
> Acked-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 5 ++
> .../gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c | 66 +++++++++++++++++--
> .../gpu/drm/amd/amdgpu/amdgpu_dev_coredump.h | 9 +++
> 3 files changed, 74 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h b/drivers/gpu/drm/amd/amdgpu/amdgpu.h
> index 057c8bd2ad89..ae81a428cfb5 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu.h
> @@ -1200,6 +1200,11 @@ struct amdgpu_device {
>
> struct amdgpu_reset_domain *reset_domain;
>
> +#ifdef CONFIG_DEV_COREDUMP
> + /* If a coredump state capture is in progress don't start a new one. */
> + bool coredump_in_progress;
> +#endif
Don't keep that as state around, gather it directly from the work item.
> +
> struct mutex benchmark_mutex;
>
> bool scpm_enabled;
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c
> index 42a969512dcc..0808ca98ccd9 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c
> @@ -34,6 +34,8 @@ void amdgpu_coredump(struct amdgpu_device *adev, bool skip_vram_check,
> }
> #else
>
> +#define AMDGPU_CORE_DUMP_SIZE_MAX (256 * 1024 * 1024)
> +
> const char *hw_ip_names[MAX_HWIP] = {
> [GC_HWIP] = "GC",
> [HDP_HWIP] = "HDP",
> @@ -196,11 +198,9 @@ static void amdgpu_devcoredump_fw_info(struct amdgpu_device *adev,
> }
>
> static ssize_t
> -amdgpu_devcoredump_read(char *buffer, loff_t offset, size_t count,
> - void *data, size_t datalen)
> +amdgpu_devcoredump_format(char *buffer, size_t count, struct amdgpu_coredump_info *coredump)
> {
> struct drm_printer p;
> - struct amdgpu_coredump_info *coredump = data;
> struct drm_print_iterator iter;
> struct amdgpu_vm_fault_info *fault_info;
> struct amdgpu_ip_block *ip_block;
> @@ -208,7 +208,6 @@ amdgpu_devcoredump_read(char *buffer, loff_t offset, size_t count,
>
> iter.data = buffer;
> iter.offset = 0;
> - iter.start = offset;
> iter.remain = count;
>
> p = drm_coredump_printer(&iter);
> @@ -323,11 +322,60 @@ amdgpu_devcoredump_read(char *buffer, loff_t offset, size_t count,
> return count - iter.remain;
> }
>
> +static ssize_t
> +amdgpu_devcoredump_read(char *buffer, loff_t offset, size_t count,
> + void *data, size_t datalen)
> +{
> + struct amdgpu_coredump_info *coredump = data;
> + ssize_t byte_copied;
> +
> + if (!coredump)
> + return -ENODEV;
> +
> + flush_work(&coredump->work);
> +
> + if (!coredump->formatted)
> + return -ENODEV;
> +
> + if (offset >= coredump->formatted_size)
> + return 0;
> +
> + byte_copied = count < coredump->formatted_size - offset ? count :
> + coredump->formatted_size - offset;
> + memcpy(buffer, coredump->formatted + offset, byte_copied);
> +
> + return byte_copied;
> +}
> +
> static void amdgpu_devcoredump_free(void *data)
> {
> + struct amdgpu_coredump_info *coredump = data;
> +
> + cancel_work_sync(&coredump->work);
> + coredump->adev->coredump_in_progress = false;
> + kfree(coredump->formatted);
> kfree(data);
> }
>
> +static void amdgpu_devcoredump_deferred_work(struct work_struct *work)
> +{
> + struct amdgpu_coredump_info *coredump = container_of(work, typeof(*coredump), work);
> +
> + dev_coredumpm(coredump->adev->dev, THIS_MODULE, coredump, 0, GFP_NOWAIT,
> + amdgpu_devcoredump_read, amdgpu_devcoredump_free);
> +
> + /* Do a one-time preparation of the coredump output because
> + * repeatingly calling drm_coredump_printer is very slow.
> + */
> + coredump->formatted_size =
> + amdgpu_devcoredump_format(NULL, AMDGPU_CORE_DUMP_SIZE_MAX, coredump);
> + coredump->formatted = kvzalloc(coredump->formatted_size, GFP_KERNEL);
> + if (!coredump->formatted)
> + return;
> + amdgpu_devcoredump_format(coredump->formatted, coredump->formatted_size, coredump);
> + coredump->adev->coredump_in_progress = false;
> +}
> +
> void amdgpu_coredump(struct amdgpu_device *adev, bool skip_vram_check,
> bool vram_lost, struct amdgpu_job *job)
> {
> @@ -335,10 +383,15 @@ void amdgpu_coredump(struct amdgpu_device *adev, bool skip_vram_check,
> struct amdgpu_coredump_info *coredump;
> struct drm_sched_job *s_job;
>
> + if (adev->coredump_in_progress)
> + return;
> +
> coredump = kzalloc(sizeof(*coredump), GFP_NOWAIT);
> if (!coredump)
> return;
>
> + adev->coredump_in_progress = true;
That is racy, clearly don't do that.
Regards,
Christian.
> +
> coredump->skip_vram_check = skip_vram_check;
> coredump->reset_vram_lost = vram_lost;
>
> @@ -361,8 +414,9 @@ void amdgpu_coredump(struct amdgpu_device *adev, bool skip_vram_check,
>
> ktime_get_ts64(&coredump->reset_time);
>
> - dev_coredumpm(dev->dev, THIS_MODULE, coredump, 0, GFP_NOWAIT,
> - amdgpu_devcoredump_read, amdgpu_devcoredump_free);
> + /* Kick off coredump formatting to a worker thread. */
> + INIT_WORK(&coredump->work, amdgpu_devcoredump_deferred_work);
> + queue_work(system_unbound_wq, &coredump->work);
>
> drm_info(dev, "AMDGPU device coredump file has been created\n");
> drm_info(dev, "Check your /sys/class/drm/card%d/device/devcoredump/data\n",
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.h b/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.h
> index ef9772c6bcc9..4c37a852b74a 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.h
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.h
> @@ -35,9 +35,18 @@ struct amdgpu_coredump_info {
> struct amdgpu_device *adev;
> struct amdgpu_task_info reset_task_info;
> struct timespec64 reset_time;
> +
> + struct work_struct work;
> +
> bool skip_vram_check;
> bool reset_vram_lost;
> struct amdgpu_ring *ring;
> + /* Readable form of coredevdump, generate once to speed up
> + * reading it (see drm_coredump_printer's documentation).
> + */
> + ssize_t formatted_size;
> + char *formatted;
> +
> };
> #endif
>
next prev parent reply other threads:[~2026-03-03 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 9:37 [PATCH v2 1/6] drm/amdgpu: include ip discovery data in devcoredump Pierre-Eric Pelloux-Prayer
2026-02-26 9:37 ` [PATCH v2 2/6] drm/amdgpu: move devcoredump generation to a worker Pierre-Eric Pelloux-Prayer
2026-03-03 9:40 ` Christian König [this message]
2026-02-26 9:37 ` [PATCH v2 3/6] drm/amdgpu: save ring content before resetting the device Pierre-Eric Pelloux-Prayer
2026-02-26 9:37 ` [PATCH v2 4/6] drm/amdgpu: extract amdgpu_vm_lock_by_pasid from amdgpu_vm_handle_fault Pierre-Eric Pelloux-Prayer
2026-02-26 9:37 ` [PATCH v2 5/6] drm/amdgpu: store ib info for devcoredump Pierre-Eric Pelloux-Prayer
2026-02-26 9:37 ` [PATCH v2 6/6] drm/amdgpu: dump job ibs in the devcoredump Pierre-Eric Pelloux-Prayer
2026-03-02 18:47 ` Alex Deucher
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=03f173aa-eb64-43e9-aa1a-570b3dce4b9a@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.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=pierre-eric.pelloux-prayer@amd.com \
--cc=simona@ffwll.ch \
/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®