From: Felix Kuehling <felix.kuehling@amd.com>
To: "Srinivasan Shanmugam" <srinivasan.shanmugam@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Lijo Lazar" <lijo.lazar@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdkfd: Fix type of 'dbg_flags' in 'struct kfd_process'
Date: Thu, 21 Dec 2023 13:00:33 -0500 [thread overview]
Message-ID: <257cfdd8-17ea-44ef-bd41-fb2f03232e76@amd.com> (raw)
In-Reply-To: <20231221173949.1403999-1-srinivasan.shanmugam@amd.com>
On 2023-12-21 12:39, Srinivasan Shanmugam wrote:
> dbg_flags looks to be defined with incorrect data type; to process
> multiple debug flag options, and hence defined dbg_flags as u32.
>
> Fixes the below:
>
> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_packet_manager_v9.c:117 pm_map_process_aldebaran() warn: maybe use && instead of &
Please add a Fixes-tag:
Fixes: 0de4ec9a0353 ("drm/amdgpu: prepare map process for multi-process
debug devices")
>
> Suggested-by: Lijo Lazar <lijo.lazar@amd.com>
> Cc: Felix Kuehling <Felix.Kuehling@amd.com>
> Cc: Christian König <christian.koenig@amd.com>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Signed-off-by: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_priv.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_priv.h b/drivers/gpu/drm/amd/amdkfd/kfd_priv.h
> index 45366b4ca976..745024b31340 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_priv.h
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_priv.h
> @@ -970,7 +970,7 @@ struct kfd_process {
> struct work_struct debug_event_workarea;
>
> /* Tracks debug per-vmid request for debug flags */
> - bool dbg_flags;
> + u32 dbg_flags;
For consistency with the rest of this header file, I'd prefer we use
uint32_t here. Other than that, the patch is
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
>
> atomic_t poison;
> /* Queues are in paused stated because we are in the process of doing a CRIU checkpoint */
next prev parent reply other threads:[~2023-12-21 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 17:39 [PATCH] drm/amdkfd: Fix type of 'dbg_flags' in 'struct kfd_process' Srinivasan Shanmugam
2023-12-21 18:00 ` Felix Kuehling [this message]
2023-12-29 9:52 ` SRINIVASAN SHANMUGAM
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=257cfdd8-17ea-44ef-bd41-fb2f03232e76@amd.com \
--to=felix.kuehling@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=lijo.lazar@amd.com \
--cc=srinivasan.shanmugam@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 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.