From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org, sashal@kernel.org, Jack Xiao <Jack.Xiao@amd.com>
Subject: Re: [PATCH] drm/amdgpu/mes: fix mes ring buffer overflow
Date: Tue, 27 Aug 2024 16:21:09 +0200 [thread overview]
Message-ID: <2024082746-amendment-unread-593d@gregkh> (raw)
In-Reply-To: <20240827141025.1329567-1-alexander.deucher@amd.com>
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.
> Signed-off-by: Jack Xiao <Jack.Xiao@amd.com>
> Acked-by: Alex Deucher <alexander.deucher@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> (cherry picked from commit 34e087e8920e635c62e2ed6a758b0cd27f836d13)
> Cc: stable@vger.kernel.org # 6.10.x
So why does this need to go to 6.10.y?
confused,
greg k-h
next prev parent reply other threads:[~2024-08-27 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 14:10 [PATCH] drm/amdgpu/mes: fix mes ring buffer overflow Alex Deucher
2024-08-27 14:21 ` Greg KH [this message]
2024-08-27 15:01 ` Deucher, Alexander
2024-08-27 16:13 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2024-07-19 9:16 Jack Xiao
2024-07-19 13:56 ` Alex Deucher
2024-07-19 15:44 ` Christian König
2024-07-22 3:27 ` Xiao, Jack
2024-07-22 8:20 ` Christian König
2024-07-22 8:46 ` Xiao, Jack
2024-07-22 11:20 ` Christian König
2024-07-22 19:52 ` Alex Deucher
2024-07-23 3:08 ` Xiao, Jack
2024-07-23 8:15 ` Xiao, Jack
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=2024082746-amendment-unread-593d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Jack.Xiao@amd.com \
--cc=alexander.deucher@amd.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.