From: Felix Kuehling <felix.kuehling@amd.com>
To: Andrew Martin <andrew.martin@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/amdkfd: Ignored various return code
Date: Fri, 14 Nov 2025 16:58:48 -0500 [thread overview]
Message-ID: <dc1b0471-448b-44a7-b7cf-9f094dbc1545@amd.com> (raw)
In-Reply-To: <20251113183155.1120872-1-andrew.martin@amd.com>
On 2025-11-13 13:31, Andrew Martin wrote:
> The return code of a non void function should not be ignored. In cases
> where we do not care, the code needs to suppress it.
>
> Signed-off-by: Andrew Martin <andrew.martin@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c | 13 ++++++++-----
> drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 3 ++-
> 2 files changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
> index 644f79f3c9af..e4438fca6283 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
> @@ -313,8 +313,10 @@ int amdgpu_amdkfd_post_reset(struct amdgpu_device *adev)
> void amdgpu_amdkfd_gpu_reset(struct amdgpu_device *adev)
> {
> if (amdgpu_device_should_recover_gpu(adev))
> - amdgpu_reset_domain_schedule(adev->reset_domain,
> - &adev->kfd.reset_work);
> + WARN_ONCE(!amdgpu_reset_domain_schedule(adev->reset_domain,
> + &adev->kfd.reset_work),
> + "Failed to queue work! at %s",
> + __func__);
The return value is not an error. It only indicates that reset work was
already queued.
> }
>
> int amdgpu_amdkfd_alloc_gtt_mem(struct amdgpu_device *adev, size_t size,
> @@ -715,9 +717,10 @@ void amdgpu_amdkfd_set_compute_idle(struct amdgpu_device *adev, bool idle)
> if (gfx_block != NULL)
> gfx_block->version->funcs->set_powergating_state((void *)gfx_block, state);
> }
> - amdgpu_dpm_switch_power_profile(adev,
> - PP_SMC_POWER_PROFILE_COMPUTE,
> - !idle);
> + WARN_ONCE(!amdgpu_dpm_switch_power_profile(adev, PP_SMC_POWER_PROFILE_COMPUTE, !idle),
> + "(%s) failed to disable video power profile mode",
> + __func__);
I think 0 means success here. But I agree with Philip that we can
probably ignore errors here. I believe some chips just don't support
power profiles and return an error here.
> +
> }
>
> bool amdgpu_amdkfd_is_kfd_vmid(struct amdgpu_device *adev, u32 vmid)
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c b/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c
> index 22925df6a791..025609a4abcf 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c
> @@ -2780,7 +2780,8 @@ static int runtime_enable(struct kfd_process *p, uint64_t r_debug,
> * saved in MES.
> */
> if (pdd->dev->kfd->shared_resources.enable_mes)
> - kfd_dbg_set_mes_debug_mode(pdd, !kfd_dbg_has_cwsr_workaround(pdd->dev));
> + (void)kfd_dbg_set_mes_debug_mode(pdd,
> + !kfd_dbg_has_cwsr_workaround(pdd->dev));
In this case we could actually handle the error and return an error up
to the caller.
Regards,
Felix
> }
>
> p->runtime_info.runtime_state = DEBUG_RUNTIME_STATE_ENABLED;
prev parent reply other threads:[~2025-11-14 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 18:31 [PATCH v3] drm/amdkfd: Ignored various return code Andrew Martin
2025-11-14 18:53 ` Philip Yang
2025-11-14 19:15 ` Martin, Andrew
2025-11-14 21:58 ` Felix Kuehling [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=dc1b0471-448b-44a7-b7cf-9f094dbc1545@amd.com \
--to=felix.kuehling@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrew.martin@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