From: Felix Kuehling <felix.kuehling@amd.com>
To: Kent Russell <kent.russell@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdkfd: Align unique_id format to match amdgpu
Date: Thu, 14 Sep 2023 13:24:36 -0400 [thread overview]
Message-ID: <2bf0fc75-0ee3-4ee1-678c-e7f26ce781dd@amd.com> (raw)
In-Reply-To: <20230914170906.88487-1-kent.russell@amd.com>
On 2023-09-14 13:09, Kent Russell wrote:
> unique_id is printed as %016llx in amdgpu, but %llu in KFD. Call the
> sysfs_show_gen_prop function directly and use the %016llx format, to
> align with amdgpu. Don't need to add a new macro since this is a one-off.
Doesn't this break the ABI? Any tool currently reading the unique ID
would expect it to be decimal.
Regards,
Felix
>
> Signed-off-by: Kent Russell <kent.russell@amd.com>
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> index c8c75ff7cea8..4dac29cdab20 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> @@ -538,7 +538,7 @@ static ssize_t node_show(struct kobject *kobj, struct attribute *attr,
> dev->node_props.debug_prop);
> sysfs_show_32bit_prop(buffer, offs, "sdma_fw_version",
> dev->gpu->kfd->sdma_fw_version);
> - sysfs_show_64bit_prop(buffer, offs, "unique_id",
> + sysfs_show_gen_prop(buffer, offs, "%s %016llx\n", "unique_id",
> dev->gpu->adev->unique_id);
> sysfs_show_32bit_prop(buffer, offs, "num_xcc",
> NUM_XCC(dev->gpu->xcc_mask));
next prev parent reply other threads:[~2023-09-14 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 17:09 [PATCH] drm/amdkfd: Align unique_id format to match amdgpu Kent Russell
2023-09-14 17:24 ` Felix Kuehling [this message]
2023-09-14 17:36 ` Russell, Kent
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=2bf0fc75-0ee3-4ee1-678c-e7f26ce781dd@amd.com \
--to=felix.kuehling@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=kent.russell@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.