AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Prike Liang <Prike.Liang@amd.com>, amd-gfx@lists.freedesktop.org
Cc: Alexander.Deucher@amd.com, phil@jpmr.org
Subject: Re: [PATCH 1/2] Revert "drm/amdgpu: don't attach the tlb fence for SI"
Date: Fri, 9 Jan 2026 10:08:11 +0100	[thread overview]
Message-ID: <98ab0d09-68af-431e-9a36-3963ec9361bc@amd.com> (raw)
In-Reply-To: <20260109082523.889564-1-Prike.Liang@amd.com>

On 1/9/26 09:25, Prike Liang wrote:
> This reverts commit 47d28900bc2049379b28656cf1e527aa8598925b.
> 
> It’s better to validate VM TLB flushes in the flush‑TLB backend
> rather than in the generic VM layer.
> 
> Signed-off-by: Prike Liang <Prike.Liang@amd.com>

Reviewed-by: Christian König <christian.koenig@amd.com>

> ---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index 0eccb31793ca..6a2ea200d90c 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -1069,9 +1069,7 @@ amdgpu_vm_tlb_flush(struct amdgpu_vm_update_params *params,
>  	}
>  
>  	/* Prepare a TLB flush fence to be attached to PTs */
> -	if (!params->unlocked &&
> -	    /* SI doesn't support pasid or KIQ/MES */
> -	    params->adev->family > AMDGPU_FAMILY_SI) {
> +	if (!params->unlocked) {
>  		amdgpu_vm_tlb_fence_create(params->adev, vm, fence);
>  
>  		/* Makes sure no PD/PT is freed before the flush */


      parent reply	other threads:[~2026-01-09  9:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  8:25 [PATCH 1/2] Revert "drm/amdgpu: don't attach the tlb fence for SI" Prike Liang
2026-01-09  8:25 ` [PATCH 2/2] drm/amdgpu: validate the flush_gpu_tlb_pasid() Prike Liang
2026-01-09  9:09   ` Christian König
2026-01-12  1:56     ` Liang, Prike
2026-01-09  9:08 ` Christian König [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=98ab0d09-68af-431e-9a36-3963ec9361bc@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Prike.Liang@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=phil@jpmr.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