From: "Timur Kristóf" <timur.kristof@gmail.com>
To: Alex Deucher <alexander.deucher@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: don't attach the tlb fence for SI
Date: Wed, 03 Dec 2025 13:19:53 +0100 [thread overview]
Message-ID: <d8731e63e9a412f8b6100b140db8fda619bd79db.camel@gmail.com> (raw)
In-Reply-To: <20251202192932.2038495-1-alexander.deucher@amd.com>
On Tue, 2025-12-02 at 14:29 -0500, Alex Deucher wrote:
> 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")
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Thank you Alex!
Reviewed-by: Timur Kristóf <timur.kristof@gmail.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index 6a2ea200d90c8..0eccb31793ca7 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -1069,7 +1069,9 @@ amdgpu_vm_tlb_flush(struct
> amdgpu_vm_update_params *params,
> }
>
> /* Prepare a TLB flush fence to be attached to PTs */
> - if (!params->unlocked) {
> + if (!params->unlocked &&
> + /* SI doesn't support pasid or KIQ/MES */
> + params->adev->family > AMDGPU_FAMILY_SI) {
> amdgpu_vm_tlb_fence_create(params->adev, vm, fence);
>
> /* Makes sure no PD/PT is freed before the flush */
prev parent reply other threads:[~2025-12-03 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 19:29 [PATCH] drm/amdgpu: don't attach the tlb fence for SI Alex Deucher
2025-12-03 12:19 ` Timur Kristóf [this message]
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=d8731e63e9a412f8b6100b140db8fda619bd79db.camel@gmail.com \
--to=timur.kristof@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox