From: "Christian König" <christian.koenig@amd.com>
To: 2564278112@qq.com, alexander.deucher@amd.com
Cc: airlied@gmail.com, simona@ffwll.ch,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Wang Jiang <jiangwang@kylinos.cn>,
Philipp Stanner <phasta@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH] drm/radeon: restore hardware polling in fence_is_signaled to fix performance regression
Date: Wed, 5 Aug 2026 10:34:33 +0200 [thread overview]
Message-ID: <baa434d9-e0a9-482d-a071-42d204b82126@amd.com> (raw)
In-Reply-To: <tencent_BB2A7CAE632BA0AC08D9296E78A15786200A@qq.com>
On 7/29/26 12:26, 2564278112@qq.com wrote:
> From: Wang Jiang <jiangwang@kylinos.cn>
>
> Commit 9eb00b5f5697b ("drm/radeon: delete radeon_fence_process in
> is_signaled, no deadlock") removed the hardware polling from
> radeon_fence_is_signaled() to fix a self-deadlock caused by
> wake_up_all(&rdev->fence_queue) being called with the fence queue
> lock held.
>
> However, removing the polling entirely causes significant performance
> regression (e.g. glxgears FPS drop) because the fence signaled check
> becomes purely passive — it only reads the cached last_seq without
> probing the GPU, so completed GPU work is not detected in time,
> causing unnecessary CPU stalls in sync-heavy workloads.
>
> Fix this by calling radeon_fence_activity() directly instead of
> radeon_fence_process(). radeon_fence_activity() reads the hardware
> fence counter and updates last_seq via atomic ops without calling
> wake_up_all(), thus avoiding the deadlock while restoring timely
> fence detection.
Yeah I already feared that removing this in commit 9eb00b5f5697b could cause issues.
Adding Philip and Danilo since we recently had a discussion about the necessity of this.
> Fixes: 9eb00b5f5697b ("drm/radeon: delete radeon_fence_process in is_signaled, no deadlock")
> Signed-off-by: Wang Jiang <jiangwang@kylinos.cn>
As far as I remember the radeon code the solution should work, but I don't have time to double check.
Acked-by: Christian König <christian.koenig@amd.com>
Thanks,
Christian.
> ---
> drivers/gpu/drm/radeon/radeon_fence.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_fence.c b/drivers/gpu/drm/radeon/radeon_fence.c
> index 02a40e4750c7..299865569252 100644
> --- a/drivers/gpu/drm/radeon/radeon_fence.c
> +++ b/drivers/gpu/drm/radeon/radeon_fence.c
> @@ -360,6 +360,13 @@ static bool radeon_fence_is_signaled(struct dma_fence *f)
> if (atomic64_read(&rdev->fence_drv[ring].last_seq) >= seq)
> return true;
>
> + if (down_read_trylock(&rdev->exclusive_lock)) {
> + radeon_fence_activity(rdev, ring);
> + up_read(&rdev->exclusive_lock);
> +
> + if (atomic64_read(&rdev->fence_drv[ring].last_seq) >= seq)
> + return true;
> + }
> return false;
> }
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2026-08-05 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 10:26 2564278112
2026-08-05 8:34 ` Christian König [this message]
2026-08-05 9:12 ` Philipp Stanner
2026-08-05 13:39 ` Alex Deucher
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=baa434d9-e0a9-482d-a071-42d204b82126@amd.com \
--to=christian.koenig@amd.com \
--cc=2564278112@qq.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jiangwang@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=phasta@kernel.org \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®