From: Alex Deucher <alexander.deucher@amd.com>
To: <amd-gfx@lists.freedesktop.org>, <christian.koenig@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [PATCH 0/8] Improvements for IB handling V9
Date: Mon, 16 Feb 2026 16:13:32 -0500 [thread overview]
Message-ID: <20260216211340.16364-1-alexander.deucher@amd.com> (raw)
This set contains a number of bug fixes and cleanups for
IB handling that I worked on over the holidays. Many of
the original patches have landed now. These are the
remaining patches.
Patch 1:
Rework the backup and reemit code for per ring reset so that
we can safely reemit repeatedly. This removes the current
single reemit limit currently in place. V9 moves this to the start
of the series as its dependencies have been reviewed and
applied.
Patches 2-4:
Removes the direct submit path for IBs and requires
that all IB submissions use a job structure. This
greatly simplifies the IB submission code. V2 uses
GFP_ATOMIC when in reset. V3 sqaushes all of the
IP changes into one patch. Not sure there is much
value breaking this out per IP. V4 uses the pool type
to determine the alloc flags. No changes in V8.
V9 fixes some typos in the gfx9 RAS IB handling.
Patches 5-8:
Improvements for adapter resets. Properly add the bad job
back to the pending list so we can stop calling
drm_sched_stop/start(). Return the proper error number
in the CS IOCTL when the context is guilty. Now that that
is handled properly we can call drm_sched_increase_karma()
for ring resets as well. Properly set the error on the the
timedout fence for adapter resets. These changes also resulted
in a small clean up the the VCN reset helpler. No changes in
V9.
Alex Deucher (8):
drm/amdgpu: rework ring reset backup and reemit v9
drm/amdgpu/job: use GFP_ATOMIC while in gpu reset
drm/amdgpu: switch all IPs to using job for IBs
drm/amdgpu: require a job to schedule an IB
drm/amdgpu: plumb timedout fence through to force completion
drm/amdgpu: simplify VCN reset helper
drm/amdgpu/cs: return -ETIME for guilty contexts
drm/amdgpu: Call drm_sched_increase_karma() for ring resets
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c | 4 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 4 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 6 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 125 +++++++++---------
drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c | 127 ++++++++----------
drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 20 +--
drivers/gpu/drm/amd/amdgpu/amdgpu_job.h | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_object.h | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c | 46 ++-----
drivers/gpu/drm/amd/amdgpu/amdgpu_ring.h | 26 ++--
drivers/gpu/drm/amd/amdgpu/amdgpu_sa.c | 5 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_sdma.c | 4 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c | 52 +++-----
drivers/gpu/drm/amd/amdgpu/amdgpu_vpe.c | 37 +++---
drivers/gpu/drm/amd/amdgpu/cik_sdma.c | 31 +++--
drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c | 29 ++--
drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 29 ++--
drivers/gpu/drm/amd/amdgpu/gfx_v12_0.c | 29 ++--
drivers/gpu/drm/amd/amdgpu/gfx_v12_1.c | 29 ++--
drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c | 24 ++--
drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c | 25 ++--
drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c | 139 ++++++++++----------
drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 139 ++++++++++----------
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_2.c | 27 ++--
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c | 29 ++--
drivers/gpu/drm/amd/amdgpu/sdma_v2_4.c | 38 +++---
drivers/gpu/drm/amd/amdgpu/sdma_v3_0.c | 38 +++---
drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c | 38 +++---
drivers/gpu/drm/amd/amdgpu/sdma_v4_4_2.c | 38 +++---
drivers/gpu/drm/amd/amdgpu/sdma_v5_0.c | 37 +++---
drivers/gpu/drm/amd/amdgpu/sdma_v5_2.c | 36 ++---
drivers/gpu/drm/amd/amdgpu/sdma_v6_0.c | 36 ++---
drivers/gpu/drm/amd/amdgpu/sdma_v7_0.c | 36 ++---
drivers/gpu/drm/amd/amdgpu/sdma_v7_1.c | 36 ++---
drivers/gpu/drm/amd/amdgpu/si_dma.c | 29 ++--
drivers/gpu/drm/amd/amdgpu/vcn_v4_0_3.c | 2 +-
drivers/gpu/drm/amd/amdgpu/vcn_v5_0_1.c | 2 +-
39 files changed, 689 insertions(+), 671 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-16 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 21:13 Alex Deucher [this message]
2026-02-16 21:13 ` [PATCH 1/8] drm/amdgpu: rework ring reset backup and reemit v9 Alex Deucher
2026-02-16 21:13 ` [PATCH 2/8] drm/amdgpu/job: use GFP_ATOMIC while in gpu reset Alex Deucher
2026-02-16 21:13 ` [PATCH 3/8] drm/amdgpu: switch all IPs to using job for IBs Alex Deucher
2026-02-16 21:13 ` [PATCH 4/8] drm/amdgpu: require a job to schedule an IB Alex Deucher
2026-02-16 21:13 ` [PATCH 5/8] drm/amdgpu: plumb timedout fence through to force completion Alex Deucher
2026-02-16 21:13 ` [PATCH 6/8] drm/amdgpu: simplify VCN reset helper Alex Deucher
2026-02-16 21:13 ` [PATCH 7/8] drm/amdgpu/cs: return -ETIME for guilty contexts Alex Deucher
2026-02-16 21:13 ` [PATCH 8/8] drm/amdgpu: Call drm_sched_increase_karma() for ring resets 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=20260216211340.16364-1-alexander.deucher@amd.com \
--to=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@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