kernel.git/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.h, branch linux-6.17.y

drm/amdgpu: set an error on all fences from a bad context

2025-10-23T14:24:34Z

[ Upstream commit ff780f4f80323148d43198f2052c14160c8428d3 ] When we backup ring contents to reemit after a queue reset, we don't backup ring contents from the bad context. When we signal the fences, we should set an error on those fences as well. v2: misc cleanups v3: add locking for fence error, fix comment (Christian) v4: fix wrap around, locking (Christian) Fixes: 77cc0da39c7c ("drm/amdgpu: track ring state associated with a fence") Reviewed-by: Christian König Signed-off-by: Alex Deucher Signed-off-by: Sasha Levin

drm/amdgpu: Fix allocating extra dwords for rings (v2)

2025-10-15T10:03:58Z

[ Upstream commit ae5c2bee1680436d9bf8bfaca7416496adff0ee0 ] Rename extra_dw to extra_bytes and document what it's for. The value is already used as if it were bytes in vcn_v4_0.c and in amdgpu_ring_init. Just adjust the dword count in jpeg_v1_0.c so that it becomes a byte count. v2: Rename extra_dw to extra_bytes as discussed during review. Fixes: c8c1a1d2ef04 ("drm/amdgpu: define and add extra dword for jpeg ring") Signed-off-by: Timur Kristóf Reviewed-by: Christian König Signed-off-by: Alex Deucher Signed-off-by: Sasha Levin

drm/amdgpu: move reset support type checks into the caller

2025-07-17T16:36:56Z

Rather than checking in the callbacks, check if the reset type is supported in the caller. Reviewed-by: Lijo Lazar Signed-off-by: Alex Deucher

drm/amdgpu: track ring state associated with a fence

2025-07-16T20:14:11Z

We need to know the wptr and sequence number associated with a fence so that we can re-emit the unprocessed state after a ring reset. Pre-allocate storage space for the ring buffer contents and add helpers to save off and re-emit the unprocessed state so that it can be re-emitted after the queue is reset. Reviewed-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: move guilty handling into ring resets

2025-06-30T15:57:36Z

Move guilty logic into the ring reset callbacks. This allows each ring reset callback to better handle fence errors and force completions in line with the reset behavior for each IP. It also allows us to remove the ring guilty callback since that logic now lives in the reset callback. Acked-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: update ring reset function signature

2025-06-30T15:57:16Z

Going forward, we'll need more than just the vmid. Add the guilty amdgpu_fence. Reviewed-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: remove job parameter from amdgpu_fence_emit()

2025-06-30T15:57:06Z

What we actually care about is the amdgpu_fence object so pass that in explicitly to avoid possible mistakes in the future. The job_run_counter handling can be safely removed at this point as we no longer support job resubmission. Reviewed-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: switch job hw_fence to amdgpu_fence

2025-06-18T16:19:21Z

Use the amdgpu fence container so we can store additional data in the fence. This also fixes the start_time handling for MCBP since we were casting the fence to an amdgpu_fence and it wasn't. Fixes: 3f4c175d62d8 ("drm/amdgpu: MCBP based on DRM scheduler (v9)") Reviewed-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: Add documentation to some parts of the AMDGPU ring and wb

2025-05-07T21:41:35Z

Add some random documentation associated with the ring buffer manipulations and writeback. Signed-off-by: Rodrigo Siqueira Signed-off-by: Alex Deucher

drm/amdgpu: add ring flag for no user submissions

2025-04-08T20:48:22Z

This would be set by IPs which only accept submissions from the kernel, not userspace, such as when kernel queues are disabled. Don't expose the rings to userspace and reject any submissions in the CS IOCTL. v2: fix error code (Alex) Reviewed-by: Sunil Khatri Signed-off-by: Alex Deucher