From: "Christian König" <christian.koenig@amd.com>
To: "John B. Moore" <jbmoore61@gmail.com>,
Alexander Deucher <alexander.deucher@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/amdgpu/gfx9: drop unnecessary 64-bit fence flag check in KIQ
Date: Wed, 29 Apr 2026 10:22:34 +0200 [thread overview]
Message-ID: <af9d66d4-e0c3-4ca2-ae6f-db125c19486c@amd.com> (raw)
In-Reply-To: <20260428163512.9504-1-jbmoore61@gmail.com>
On 4/28/26 18:35, John B. Moore wrote:
> Remove the BUG_ON(flags & AMDGPU_FENCE_FLAG_64BIT) assertion from
> gfx_v9_0_ring_emit_fence_kiq(). The KIQ hardware supports 64-bit
> fence writes; the 32-bit writeback address constraint is an
> upper-layer convention, not a hardware limitation. The check serves
> no purpose and should not be present.
>
> Found by code inspection while investigating related BUG_ON
> assertions in the GFX and compute ring emission paths.
>
> Signed-off-by: John B. Moore <jbmoore61@gmail.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c
> index 47e81c33d..fb2a0f1af 100644
> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c
> @@ -5679,9 +5679,6 @@ static void gfx_v9_0_ring_emit_fence_kiq(struct amdgpu_ring *ring, u64 addr,
> struct amdgpu_device *adev = ring->adev;
>
> - /* we only allocate 32bit for each seq wb address */
> - BUG_ON(flags & AMDGPU_FENCE_FLAG_64BIT);
> -
> /* write fence seq to the "addr" */
> amdgpu_ring_write(ring, PACKET3(PACKET3_WRITE_DATA, 3));
> amdgpu_ring_write(ring, (WRITE_DATA_ENGINE_SEL(0) |
next prev parent reply other threads:[~2026-04-29 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 16:35 [PATCH v3] drm/amdgpu/gfx9: drop unnecessary 64-bit fence flag check in KIQ John B. Moore
2026-04-29 8:22 ` Christian König [this message]
2026-04-29 13:57 ` 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=af9d66d4-e0c3-4ca2-ae6f-db125c19486c@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=jbmoore61@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.