From: Philip Yang <yangp@amd.com>
To: Brian Kocoloski <brian.kocoloski@amd.com>, amd-gfx@lists.freedesktop.org
Cc: Philip.Yang@amd.com, Brian Kocoloski <bkocolos@amd.com>
Subject: Re: [PATCH] drm/amdkfd: Fix improper NULL termination of queue restore SMI event string
Date: Mon, 1 Dec 2025 16:46:59 -0500 [thread overview]
Message-ID: <80b9b439-20bf-464c-8a4e-e0bed18627a3@amd.com> (raw)
In-Reply-To: <20251201210008.40096-1-brian.kocoloski@amd.com>
On 2025-12-01 16:00, Brian Kocoloski wrote:
> From: Brian Kocoloski <bkocolos@amd.com>
>
> Pass character "0" rather than NULL terminator to properly format
> queue restoration SMI events. Currently, the NULL terminator precedes
> the newline character that is intended to delineate separate events
> in the SMI event buffer, which can break userspace parsers.
>
> Signed-off-by: Brian Kocoloski <brian.kocoloski@amd.com>
Reviewed-by: Philip Yang <Philip.Yang@amd.com>
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c b/drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c
> index a499449fcb06..d2bc169e84b0 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c
> @@ -312,7 +312,7 @@ void kfd_smi_event_queue_restore(struct kfd_node *node, pid_t pid)
> {
> kfd_smi_event_add(pid, node, KFD_SMI_EVENT_QUEUE_RESTORE,
> KFD_EVENT_FMT_QUEUE_RESTORE(ktime_get_boottime_ns(), pid,
> - node->id, 0));
> + node->id, '0'));
> }
>
> void kfd_smi_event_queue_restore_rescheduled(struct mm_struct *mm)
next prev parent reply other threads:[~2025-12-01 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 21:00 [PATCH] drm/amdkfd: Fix improper NULL termination of queue restore SMI event string Brian Kocoloski
2025-12-01 21:46 ` Philip Yang [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 19:12 Brian Kocoloski
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=80b9b439-20bf-464c-8a4e-e0bed18627a3@amd.com \
--to=yangp@amd.com \
--cc=Philip.Yang@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bkocolos@amd.com \
--cc=brian.kocoloski@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