From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: Eric Huang <jinhuieric.huang@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdkfd: set uuid for each partition in topology
Date: Fri, 8 Aug 2025 12:29:04 +0530 [thread overview]
Message-ID: <45bded3a-e3c7-421e-8cd9-ec268fca7db7@amd.com> (raw)
In-Reply-To: <20250807204948.286132-1-jinhuieric.huang@amd.com>
On 8/8/2025 2:19 AM, Eric Huang wrote:
> Currently each kfd compute partition/node is sharing
> the same uuid of AID, which doen't meet the CUDA spec
> for visible device, so corresponding XCD id for each
> partition in smu has been assigned to xcp, and exposed
> to kfd topology.
>
> Signed-off-by: Eric Huang <jinhuieric.huang@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 4ec73f33535e..14b5fa670727 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> @@ -530,7 +530,7 @@ static ssize_t node_show(struct kobject *kobj, struct attribute *attr,
> sysfs_show_32bit_prop(buffer, offs, "sdma_fw_version",
> dev->gpu->kfd->sdma_fw_version);
> sysfs_show_64bit_prop(buffer, offs, "unique_id",
> - dev->gpu->adev->unique_id);
> + dev->gpu->xcp->unique_id);
This needs a NULL check. If KFD has xcp, use its id; else show from the
device.
Thanks,
Lijo
> sysfs_show_32bit_prop(buffer, offs, "num_xcc",
> NUM_XCC(dev->gpu->xcc_mask));
> }
prev parent reply other threads:[~2025-08-08 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 20:49 [PATCH] drm/amdkfd: set uuid for each partition in topology Eric Huang
2025-08-08 6:59 ` Lazar, Lijo [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=45bded3a-e3c7-421e-8cd9-ec268fca7db7@amd.com \
--to=lijo.lazar@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=jinhuieric.huang@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.