From: Greg KH <gregkh@linuxfoundation.org>
To: Hans de Goede <johannes.goede@oss.qualcomm.com>
Cc: stable@vger.kernel.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Timur Kristóf" <timur.kristof@gmail.com>
Subject: Re: [PATCH] drm/amdgpu: don't attach the tlb fence for SI
Date: Mon, 15 Dec 2025 10:05:48 +0100 [thread overview]
Message-ID: <2025121500-portside-coleslaw-915b@gregkh> (raw)
In-Reply-To: <b78aadb1-d2ca-459c-8078-b1cd9a500398@oss.qualcomm.com>
On Mon, Dec 15, 2025 at 09:15:17AM +0100, Hans de Goede wrote:
> Hi greg,
>
> On 15-Dec-25 9:12 AM, Greg KH wrote:
> > On Sun, Dec 14, 2025 at 10:53:36AM +0100, Hans de Goede wrote:
> >> From: Alex Deucher <alexander.deucher@amd.com>
> >>
> >> commit eb296c09805ee37dd4ea520a7fb3ec157c31090f upstream.
> >>
> >> SI hardware doesn't support pasids, user mode queues, or
> >> KIQ/MES so there is no need for this. Doing so results in
> >> a segfault as these callbacks are non-existent for SI.
> >>
> >> Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4744
> >> Fixes: f3854e04b708 ("drm/amdgpu: attach tlb fence to the PTs update")
> >> Reviewed-by: Timur Kristóf <timur.kristof@gmail.com>
> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> >> Signed-off-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
> >> ---
> >> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > What kernel tree(s) should this go to?
>
> This fixes a regression introduced in at least 6.17.y (6.17.11)
> and 6.18.y (6.18.1). So it should at least go to those branches.
But that commit is in 6.19-rc1, not anything older.
> If any other branches also have gotten commit f3854e04b708
> backported then those should get this too.
I don't see that commit in any stable tree, what am I missing?
confused,
greg k-h
next prev parent reply other threads:[~2025-12-15 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 9:53 [PATCH] drm/amdgpu: don't attach the tlb fence for SI Hans de Goede
2025-12-15 8:12 ` Greg KH
2025-12-15 8:15 ` Hans de Goede
2025-12-15 9:05 ` Greg KH [this message]
2025-12-15 9:41 ` Hans de Goede
2025-12-19 13:41 ` Viktor Jägersküpper
2026-01-08 10:21 ` Greg KH
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=2025121500-portside-coleslaw-915b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.deucher@amd.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=stable@vger.kernel.org \
--cc=timur.kristof@gmail.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