From: Simon Marchi <simark@simark.ca>
To: Tankut Baris Aktemur <tankutbaris.aktemur@amd.com>,
gdb-patches@sourceware.org
Cc: lancelot.six@amd.com
Subject: Re: [PATCH 2/2] gdb, amd-dbgapi-target: split wave_coordinates::to_string
Date: Fri, 3 Jul 2026 09:16:58 -0400 [thread overview]
Message-ID: <0d201386-8f2d-4489-ba37-ca8835f07631@simark.ca> (raw)
In-Reply-To: <20260703125058.1828518-2-tankutbaris.aktemur@amd.com>
On 7/3/26 8:50 AM, Tankut Baris Aktemur wrote:
> wave_coordinates::to_string() produces a string in the following format:
>
> AMDGPU Wave a:q:d:w (x,y,z)/i
>
> Split the method into smaller pieces:
>
> a:q:d:w : hierarchy_str
> (x,y,z) : workgroup_coord_str
> (x,y,z)/i : dispatch_pos_str
>
> This is a refactoring to allow reusing pieces. Currently the reuse
> opportunity exists in the downstream debugger.
I think this is a nice change even for upstream, as it helps document
what the numbers mean. Assuming Lancelot is already fine with the
change:
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Just one formatting comment below.
> ---
> gdb/amd-dbgapi-target.c | 55 +++++++++++++++++++++++++++++++++--------
> 1 file changed, 45 insertions(+), 10 deletions(-)
>
> diff --git a/gdb/amd-dbgapi-target.c b/gdb/amd-dbgapi-target.c
> index 923b790664e..33512695fb5 100644
> --- a/gdb/amd-dbgapi-target.c
> +++ b/gdb/amd-dbgapi-target.c
> @@ -147,6 +147,17 @@ struct wave_coordinates
> : wave_id (wave_id)
> {}
>
> + /* Return the string showing the agent -> queue -> dispatch -> wave
> + hierarchy. */
> + std::string hierarchy_str () const;
> +
> + /* Return the workgroup coordinates as a string. */
> + std::string workgroup_coord_str () const;
> +
> + /* Return the dispatch position string for the wave this
> + wave_coordinates is for. */
> + std::string dispatch_pos_str () const;
> +
> /* Return the target ID string for the wave this wave_coordinates is
> for. */
> std::string to_string () const;
> @@ -387,13 +398,12 @@ get_amd_dbgapi_inferior_info (inferior *inferior)
> static async_event_handler *amd_dbgapi_async_event_handler = nullptr;
>
> std::string
> -wave_coordinates::to_string () const
> +wave_coordinates::hierarchy_str () const
> {
> - std::string str = "AMDGPU Wave";
> -
> - str += (agent_id != AMD_DBGAPI_AGENT_NONE
> - ? string_printf (" %s", pulongest (agent_id.handle))
> - : " ?");
> + std::string str
> + = (agent_id != AMD_DBGAPI_AGENT_NONE
> + ? string_printf (" %s", pulongest (agent_id.handle))
> + : "?");
>
> str += (queue_id != AMD_DBGAPI_QUEUE_NONE
> ? string_printf (":%s", pulongest (queue_id.handle))
> @@ -405,11 +415,25 @@ wave_coordinates::to_string () const
>
> str += string_printf (":%s", pulongest (wave_id.handle));
>
> - str += (group_ids[0] != UINT32_MAX
> - ? string_printf (" (%u,%u,%u)", group_ids[0], group_ids[1],
> - group_ids[2])
> - : " (?,?,?)");
> + return str;
> +}
> +
> +std::string
> +wave_coordinates::workgroup_coord_str () const
> +{
> + std::string str
> + = (group_ids[0] != UINT32_MAX
> + ? string_printf ("(%u,%u,%u)", group_ids[0], group_ids[1],
> + group_ids[2])
group_ids[2] could go on the previous line, for one less line wrap.
Simon
next prev parent reply other threads:[~2026-07-03 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 12:50 [PATCH 1/2] gdb, amd-dbgapi-target: use '%u' instead of '%d' in wave_coordinates::to_string Tankut Baris Aktemur
2026-07-03 12:50 ` [PATCH 2/2] gdb, amd-dbgapi-target: split wave_coordinates::to_string Tankut Baris Aktemur
2026-07-03 13:16 ` Simon Marchi [this message]
2026-07-06 10:45 ` Lancelot SIX
2026-07-03 13:12 ` [PATCH 1/2] gdb, amd-dbgapi-target: use '%u' instead of '%d' in wave_coordinates::to_string Simon Marchi
2026-07-03 13:27 ` Aktemur, Baris
2026-07-03 13:42 ` [PATCH v2 1/2] gdb, amd-dbgapi-target: use pulongest more Tankut Baris Aktemur
2026-07-06 10:31 ` Lancelot SIX
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=0d201386-8f2d-4489-ba37-ca8835f07631@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=tankutbaris.aktemur@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