From: "Christian König" <christian.koenig@amd.com>
To: Lang Yu <lang.yu@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: fix invalid fence handling in amdgpu_vm_tlb_flush
Date: Mon, 2 Sep 2024 11:06:58 +0200 [thread overview]
Message-ID: <c94ad3ab-669a-4529-96fa-2dbb28791a6c@amd.com> (raw)
In-Reply-To: <20240902030305.11952-1-lang.yu@amd.com>
Am 02.09.24 um 05:03 schrieb Lang Yu:
> Fixes: 5a1c27951966 ("drm/amdgpu: implement TLB flush fence")
>
> Signed-off-by: Lang Yu <lang.yu@amd.com>
Ah yes, that explains why CPU based updates doesn't work reliable any more.
You need to add some explanation to the commit message, e.g. something
like "CPU based updates doesn't produce a fence."
With that done Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index 1d46a5c81ec4..f93804902fd3 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -908,10 +908,12 @@ amdgpu_vm_tlb_flush(struct amdgpu_vm_update_params *params,
> {
> struct amdgpu_vm *vm = params->vm;
>
> - if (!fence || !*fence)
> + tlb_cb->vm = vm;
> + if (!fence || !*fence) {
> + amdgpu_vm_tlb_seq_cb(NULL, &tlb_cb->cb);
> return;
> + }
>
> - tlb_cb->vm = vm;
> if (!dma_fence_add_callback(*fence, &tlb_cb->cb,
> amdgpu_vm_tlb_seq_cb)) {
> dma_fence_put(vm->last_tlb_flush);
next prev parent reply other threads:[~2024-09-02 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 3:03 [PATCH] drm/amdgpu: fix invalid fence handling in amdgpu_vm_tlb_flush Lang Yu
2024-09-02 9:06 ` Christian König [this message]
2024-09-04 13:14 ` Philip Yang
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=c94ad3ab-669a-4529-96fa-2dbb28791a6c@amd.com \
--to=christian.koenig@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=lang.yu@amd.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;
as well as URLs for NNTP newsgroup(s).