From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: Alex Deucher <alexander.deucher@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 06/11] drm/amdgpu/gfx10: manually control gfxoff for CS
Date: Tue, 4 Feb 2025 13:00:15 +0530 [thread overview]
Message-ID: <0c86ca08-e651-4e40-94aa-c6958a99e220@amd.com> (raw)
In-Reply-To: <20250203214349.1400867-6-alexander.deucher@amd.com>
On 2/4/2025 3:13 AM, Alex Deucher wrote:
> Manually disallow and then allow gfxoff in begin_use
> and end_use to avoid any potential FW races when
> ringing the doorbell. There are no known issues
> with gfxoff that this solves, but it shouldn't hurt anything
> and shouldn't affect power usage since we are only
> toggling it around the doorbell update.
I think, this path shouldn't be pursued unless there is a bug identified
in specific SOCs. This really needs to be taken care by
hardware/firmware and driver shouldn't be involved. This may only be
employed as a workaround only if a real solution is not available.
Thanks,
Lijo
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c
> index 7b01828eea8dc..96346a19950b9 100644
> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c
> @@ -9826,14 +9826,14 @@ static void gfx_v10_0_ring_emit_cleaner_shader(struct amdgpu_ring *ring)
> static void gfx_v10_0_ring_begin_use(struct amdgpu_ring *ring)
> {
> amdgpu_gfx_profile_ring_begin_use(ring);
> -
> amdgpu_gfx_enforce_isolation_ring_begin_use(ring);
> + amdgpu_gfx_off_ctrl_immediate(ring->adev, false);
> }
>
> static void gfx_v10_0_ring_end_use(struct amdgpu_ring *ring)
> {
> + amdgpu_gfx_off_ctrl_immediate(ring->adev, true);
> amdgpu_gfx_profile_ring_end_use(ring);
> -
> amdgpu_gfx_enforce_isolation_ring_end_use(ring);
> }
>
next prev parent reply other threads:[~2025-02-04 7:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 21:43 [PATCH 01/11] drm/amdgpu/gfx9: manually control gfxoff for CS on RV Alex Deucher
2025-02-03 21:43 ` [PATCH 02/11] drm/amdgpu: bump version for RV/PCO compute fix Alex Deucher
2025-02-03 21:43 ` [PATCH 03/11] drm/amdgpu/gfx: add amdgpu_gfx_off_ctrl_immediate() Alex Deucher
2025-02-03 21:43 ` [PATCH 04/11] drm/amdgpu/gfx9: use amdgpu_gfx_off_ctrl_immediate() for PG Alex Deucher
2025-02-06 14:48 ` Lazar, Lijo
2025-02-03 21:43 ` [PATCH 05/11] drm/amdgpu/sdma5.2: use amdgpu_gfx_off_ctrl_immediate() Alex Deucher
2025-02-05 16:04 ` Alex Deucher
2025-02-06 14:50 ` Lazar, Lijo
2025-02-06 15:25 ` Alex Deucher
2025-02-06 15:36 ` Lazar, Lijo
2025-02-06 15:39 ` Alex Deucher
2025-02-03 21:43 ` [PATCH 06/11] drm/amdgpu/gfx10: manually control gfxoff for CS Alex Deucher
2025-02-04 7:30 ` Lazar, Lijo [this message]
2025-02-03 21:43 ` [PATCH 07/11] drm/amdgpu/gfx11: " Alex Deucher
2025-02-03 21:43 ` [PATCH 08/11] drm/amdgpu/gfx12: " Alex Deucher
2025-02-03 21:43 ` [PATCH 09/11] drm/amdgpu/sdma5.0: " Alex Deucher
2025-02-03 21:43 ` [PATCH 10/11] drm/amdgpu/sdma6.0: " Alex Deucher
2025-02-03 21:43 ` [PATCH 11/11] drm/amdgpu/sdma7.0: " 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=0c86ca08-e651-4e40-94aa-c6958a99e220@amd.com \
--to=lijo.lazar@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
/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