From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: xinhui pan <xinhui.pan@amd.com>, amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, christian.koenig@amd.com, leo.liu@amd.com
Subject: Re: [PATCH] drm/amdgpu: Fix uvd ib test timeout when use pre-allocated BO
Date: Thu, 16 Sep 2021 08:28:30 +0200 [thread overview]
Message-ID: <cb57ce4f-559d-1af4-e11b-77b195974b6c@gmail.com> (raw)
In-Reply-To: <20210916061907.12347-1-xinhui.pan@amd.com>
Am 16.09.21 um 08:19 schrieb xinhui pan:
> Now we use same BO for create/destroy msg. So destroy will wait for the
> fence returned from create to be signaled. The default timeout value in
> destroy is 10ms which is too short.
>
> Lets wait both fences with the specific timeout.
>
> Signed-off-by: xinhui pan <xinhui.pan@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c
> index b6e2abf26e18..8a26459bd80b 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c
> @@ -1336,10 +1336,17 @@ int amdgpu_uvd_ring_test_ib(struct amdgpu_ring *ring, long timeout)
> struct dma_fence *fence;
> long r;
>
> - r = amdgpu_uvd_get_create_msg(ring, 1, NULL);
> + r = amdgpu_uvd_get_create_msg(ring, 1, &fence);
> if (r)
> goto error;
>
> + r = dma_fence_wait_timeout(fence, false, timeout);
> + dma_fence_put(fence);
> + if (r == 0)
> + r = -ETIMEDOUT;
> + if (r < 0)
> + goto error;
> +
> r = amdgpu_uvd_get_destroy_msg(ring, 1, true, &fence);
> if (r)
> goto error;
prev parent reply other threads:[~2021-09-16 6:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 6:19 [PATCH] drm/amdgpu: Fix uvd ib test timeout when use pre-allocated BO xinhui pan
2021-09-16 6:28 ` 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=cb57ce4f-559d-1af4-e11b-77b195974b6c@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=leo.liu@amd.com \
--cc=xinhui.pan@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