From: "Christian König" <christian.koenig@amd.com>
To: Icenowy Zheng <uwu@icenowy.me>,
Alex Deucher <alexander.deucher@amd.com>,
Pan Xinhui <Xinhui.Pan@amd.com>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev
Subject: Re: [PATCH 1/2] drm/amdgpu: make duplicated EOP packet for GFX7/8 have real content
Date: Mon, 17 Jun 2024 14:35:59 +0200 [thread overview]
Message-ID: <88337509-3ad7-47aa-b70f-5294f7f1e486@amd.com> (raw)
In-Reply-To: <20240617105846.1516006-2-uwu@icenowy.me>
Am 17.06.24 um 12:58 schrieb Icenowy Zheng:
> The duplication of EOP packets for GFX7/8, with the former one have
> seq-1 written and the latter one have seq written, seems to confuse some
> hardware platform (e.g. Loongson 7A series PCIe controllers).
>
> Make the content of the duplicated EOP packet the same with the real
> one, only masking any possible interrupts.
Well completely NAK to that, exactly that disables the workaround.
The CPU needs to see two different values written here.
Regards,
Christian.
>
> Fixes: bf26da927a1c ("drm/amdgpu: add cache flush workaround to gfx8 emit_fence")
> Fixes: a2e73f56fa62 ("drm/amdgpu: Add support for CIK parts")
> Signed-off-by: Icenowy Zheng <uwu@icenowy.me>
> ---
> drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c | 12 +++++-------
> drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c | 12 ++++--------
> 2 files changed, 9 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c
> index 541dbd70d8c75..778f27f1a34fe 100644
> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c
> @@ -2117,9 +2117,8 @@ static void gfx_v7_0_ring_emit_fence_gfx(struct amdgpu_ring *ring, u64 addr,
> {
> bool write64bit = flags & AMDGPU_FENCE_FLAG_64BIT;
> bool int_sel = flags & AMDGPU_FENCE_FLAG_INT;
> - /* Workaround for cache flush problems. First send a dummy EOP
> - * event down the pipe with seq one below.
> - */
> +
> + /* Workaround for cache flush problems, send EOP twice. */
> amdgpu_ring_write(ring, PACKET3(PACKET3_EVENT_WRITE_EOP, 4));
> amdgpu_ring_write(ring, (EOP_TCL1_ACTION_EN |
> EOP_TC_ACTION_EN |
> @@ -2127,11 +2126,10 @@ static void gfx_v7_0_ring_emit_fence_gfx(struct amdgpu_ring *ring, u64 addr,
> EVENT_INDEX(5)));
> amdgpu_ring_write(ring, addr & 0xfffffffc);
> amdgpu_ring_write(ring, (upper_32_bits(addr) & 0xffff) |
> - DATA_SEL(1) | INT_SEL(0));
> - amdgpu_ring_write(ring, lower_32_bits(seq - 1));
> - amdgpu_ring_write(ring, upper_32_bits(seq - 1));
> + DATA_SEL(write64bit ? 2 : 1) | INT_SEL(0));
> + amdgpu_ring_write(ring, lower_32_bits(seq));
> + amdgpu_ring_write(ring, upper_32_bits(seq));
>
> - /* Then send the real EOP event down the pipe. */
> amdgpu_ring_write(ring, PACKET3(PACKET3_EVENT_WRITE_EOP, 4));
> amdgpu_ring_write(ring, (EOP_TCL1_ACTION_EN |
> EOP_TC_ACTION_EN |
> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c
> index 2f0e72caee1af..39a7d60f1fd69 100644
> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c
> @@ -6153,9 +6153,7 @@ static void gfx_v8_0_ring_emit_fence_gfx(struct amdgpu_ring *ring, u64 addr,
> bool write64bit = flags & AMDGPU_FENCE_FLAG_64BIT;
> bool int_sel = flags & AMDGPU_FENCE_FLAG_INT;
>
> - /* Workaround for cache flush problems. First send a dummy EOP
> - * event down the pipe with seq one below.
> - */
> + /* Workaround for cache flush problems, send EOP twice. */
> amdgpu_ring_write(ring, PACKET3(PACKET3_EVENT_WRITE_EOP, 4));
> amdgpu_ring_write(ring, (EOP_TCL1_ACTION_EN |
> EOP_TC_ACTION_EN |
> @@ -6164,12 +6162,10 @@ static void gfx_v8_0_ring_emit_fence_gfx(struct amdgpu_ring *ring, u64 addr,
> EVENT_INDEX(5)));
> amdgpu_ring_write(ring, addr & 0xfffffffc);
> amdgpu_ring_write(ring, (upper_32_bits(addr) & 0xffff) |
> - DATA_SEL(1) | INT_SEL(0));
> - amdgpu_ring_write(ring, lower_32_bits(seq - 1));
> - amdgpu_ring_write(ring, upper_32_bits(seq - 1));
> + DATA_SEL(write64bit ? 2 : 1) | INT_SEL(0));
> + amdgpu_ring_write(ring, lower_32_bits(seq));
> + amdgpu_ring_write(ring, upper_32_bits(seq));
>
> - /* Then send the real EOP event down the pipe:
> - * EVENT_WRITE_EOP - flush caches, send int */
> amdgpu_ring_write(ring, PACKET3(PACKET3_EVENT_WRITE_EOP, 4));
> amdgpu_ring_write(ring, (EOP_TCL1_ACTION_EN |
> EOP_TC_ACTION_EN |
next prev parent reply other threads:[~2024-06-17 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 10:58 [PATCH 0/2] Fixes of AMD GFX7/8 hang on Loongson platforms Icenowy Zheng
2024-06-17 10:58 ` [PATCH 1/2] drm/amdgpu: make duplicated EOP packet for GFX7/8 have real content Icenowy Zheng
2024-06-17 12:35 ` Christian König [this message]
2024-06-17 13:03 ` Icenowy Zheng
2024-06-17 13:09 ` Christian König
2024-06-17 13:43 ` Icenowy Zheng
2024-06-17 13:59 ` Christian König
2024-06-17 14:30 ` Icenowy Zheng
[not found] ` <e7a814fc-7b1a-4e32-8868-292be004f920@amd.com>
2024-06-17 14:57 ` Icenowy Zheng
2024-06-17 15:35 ` Xi Ruoyao
2024-06-17 15:53 ` Christian König
2024-06-17 16:09 ` Icenowy Zheng
2024-06-17 10:58 ` [PATCH 2/2] drm/radeon: repeat the same EOP packet for EOP workaround on CIK Icenowy Zheng
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=88337509-3ad7-47aa-b70f-5294f7f1e486@amd.com \
--to=christian.koenig@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chenhuacai@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=uwu@icenowy.me \
/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®