On Tue, Aug 27, 2024 at 03:01:54PM +0000, Deucher, Alexander wrote:
[Public]
-----Original Message----- From: Greg KH gregkh@linuxfoundation.org Sent: Tuesday, August 27, 2024 10:21 AM To: Deucher, Alexander Alexander.Deucher@amd.com Cc: stable@vger.kernel.org; sashal@kernel.org; Xiao, Jack Jack.Xiao@amd.com Subject: Re: [PATCH] drm/amdgpu/mes: fix mes ring buffer overflow
On Tue, Aug 27, 2024 at 10:10:25AM -0400, Alex Deucher wrote:
From: Jack Xiao Jack.Xiao@amd.com
wait memory room until enough before writing mes packets to avoid ring buffer overflow.
v2: squash in sched_hw_submission fix
Backport from 6.11.
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3571 Fixes: de3246254156 ("drm/amdgpu: cleanup MES11 command
submission")
Fixes: fffe347e1478 ("drm/amdgpu: cleanup MES12 command submission")
These commits are in 6.11-rc1.
de3246254156 ("drm/amdgpu: cleanup MES11 command submission") was ported to 6.10 as well: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/driv... So this fix is applicable there.
No, commit e356d321d024 ("drm/amdgpu: cleanup MES11 command submission") is in the 6.10 release, but commit de3246254156 ("drm/amdgpu: cleanup MES11 command submission") is in 6.11-rc1!
So how in the world are we supposed to know anything here?
See how broken this all is?
I give up.
If you all want any AMD patches applied to stable trees, manually send us a set of backported patches, AND be sure to get the git ids right.
I'll leave what I have right now in the queues, but after this round of -rc releases, all AMD patches with cc: stable are going to be automatically dropped and ignored. I NEED you all to manually send them to me now as this is just insane.
Time to go buy a Intel gpu card as there's no way this is going to work out well over time...
{sigh}
greg k-h