Linux kernel stable tree (mirror) https://git.radix-linux.su/kernel/linux.git/atom?h=v6.19.11 2026-01-21T19:55:56+00:00 2026-01-21T19:55:56+00:00 Alex Deucher alexander.deucher@amd.com 2026-01-16T02:45:43+00:00 urn:sha1:095ca815174e51fc0049771712d5455cabd7231e Needs to be a u64. Fixes: 77cc0da39c7c ("drm/amdgpu: track ring state associated with a fence") Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> (cherry picked from commit 56fff1941abd3ca3b6f394979614ca7972552f7f) 2026-01-05T22:28:45+00:00 Alex Deucher alexander.deucher@amd.com 2025-11-13T19:12:10+00:00 urn:sha1:531b43260928a53f4190f3e61de788551af6157e If when we backup the ring contents for reemit before a ring reset, we skip jobs associated with the bad context, however, we need to make sure the fences are reemited as unprocessed submissions may depend on them. v2: clean up fence handling, make helpers static Reviewed-by: Timur Kristóf <timur.kristof@gmail.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> (cherry picked from commit 155a748f14bc0b72783994dea7c5a12276730342) 2026-01-05T22:28:45+00:00 Alex Deucher alexander.deucher@amd.com 2025-11-13T18:24:10+00:00 urn:sha1:9fc27cbabee6d2e63b0268ca709ad3129b3ac50d If we cancel a bad job and reemit the ring contents, and we get another timeout, cancel everything rather than reemitting. The wptr markers are only relevant for the original emit. If we reemit, the wptr markers are no longer correct. Reviewed-by: Timur Kristóf <timur.kristof@gmail.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> (cherry picked from commit fb62a2067ca4555a6572d911e05919a311c010aa) 2025-10-28T15:31:45+00:00 Sakari Ailus sakari.ailus@linux.intel.com 2025-10-27T13:14:38+00:00 urn:sha1:ef4a4b878124ffe6afac5c7b1716308c6964bbdd pm_runtime_put_autosuspend(), pm_runtime_put_sync_autosuspend(), pm_runtime_autosuspend() and pm_request_autosuspend() now include a call to pm_runtime_mark_last_busy(). Remove the now-redundant explicit call to pm_runtime_mark_last_busy(). Acked-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2025-10-13T18:14:35+00:00 Alex Deucher alexander.deucher@amd.com 2025-08-27T15:34:14+00:00 urn:sha1:db36632ea51e8b02dd637d291c755899b20a5a31 Decouple the amdgpu fence from the amdgpu_job structure. This lets us clean up the separate fence ops for the embedded fence and other fences. This also allows us to allocate the vm fence up front when we allocate the job. v2: Additional cleanup suggested by Christian v3: Additional cleanups suggested by Christian v4: Additional cleanups suggested by David and vm fence fix v5: cast seqno (David) Cc: David.Wu3@amd.com Cc: christian.koenig@amd.com Tested-by: David (Ming Qiang) Wu <David.Wu3@amd.com> Reviewed-by: David (Ming Qiang) Wu <David.Wu3@amd.com> Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2025-10-13T18:14:15+00:00 Alex Deucher alexander.deucher@amd.com 2025-09-03T17:48:23+00:00 urn:sha1: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 <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2025-10-13T18:14:15+00:00 Alex Deucher alexander.deucher@amd.com 2025-09-15T16:37:32+00:00 urn:sha1:1f22fcb88bfef26a966e9eb242c692c6bf253d47 Compare the sequence numbers directly. Fixes: 77cc0da39c7c ("drm/amdgpu: track ring state associated with a fence") Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2025-08-27T17:57:47+00:00 Liao Yuanhong liaoyuanhong@vivo.com 2025-08-19T08:25:21+00:00 urn:sha1:ee6ba1e69dd7d969ab36f16d81c930b1a7fbf61c The amdgpu_fence struct is already zeroed by kzalloc(). It's redundant to initialize am_fence->context to 0. Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Liao Yuanhong <liaoyuanhong@vivo.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2025-08-04T18:27:28+00:00 Srinivasan Shanmugam srinivasan.shanmugam@amd.com 2025-07-21T13:34:34+00:00 urn:sha1:70e33073d941b4fc1e773769bd7d72220c14d41d The initial comment block before amdgpu_fence_driver_guilty_force_completion() incorrectly used '/**' but is not a kernel-doc comment, causing build warnings. Fixes the below with gcc W=1: drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:742: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst * Kernel queue reset handling Cc: Christian König <christian.koenig@amd.com> Cc: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com> Reviewed-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> 2025-07-16T20:14:11+00:00 Alex Deucher alexander.deucher@amd.com 2025-05-28T01:35:00+00:00 urn:sha1:77cc0da39c7ce203cd3ce6bc5696421947a979d7 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 <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>