All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mario Limonciello (AMD)" <superm1@kernel.org>
To: amd-gfx@lists.freedesktop.org
Cc: "Mario Limonciello (AMD)" <superm1@kernel.org>
Subject: [PATCH v2 0/3] Make device links between KFD and GPU device
Date: Wed, 10 Dec 2025 14:15:07 -0600	[thread overview]
Message-ID: <20251210201510.3000-1-superm1@kernel.org> (raw)

Discovering which KFD device is associated with a GPU is relatively
awkward right now in userspace.

This series creates sysfs links between the devices to simplify it
for userspace.

v2:
 * Add tag
 * Fix case that systems > 1 GPU wouldn't show links due to rebuilding
   topology.

Mario Limonciello (AMD) (3):
  amdkfd: Only ignore -ENOENT for KFD init failuires
  amdkfd: Don't rebuild node tree when calling
    kfd_topology_update_sysfs()
  amdkfd: Add device links between kfd device and amdgpu device

 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c    |  8 ++++
 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h    |  1 +
 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c    |  4 ++
 drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c       |  6 ++-
 drivers/gpu/drm/amd/amdkfd/kfd_topology.c     | 42 +++++++++++++++++--
 .../gpu/drm/amd/include/kgd_kfd_interface.h   |  2 +
 6 files changed, 57 insertions(+), 6 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-12-10 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10 20:15 Mario Limonciello (AMD) [this message]
2025-12-10 20:15 ` [PATCH v2 1/3] amdkfd: Only ignore -ENOENT for KFD init failuires Mario Limonciello (AMD)
2025-12-10 20:15 ` [PATCH v2 2/3] amdkfd: Don't rebuild node tree when calling kfd_topology_update_sysfs() Mario Limonciello (AMD)
2025-12-10 20:40   ` Russell, Kent
2025-12-16  2:42   ` Kasiviswanathan, Harish
2025-12-10 20:15 ` [PATCH v2 3/3] amdkfd: Add device links between kfd device and amdgpu device Mario Limonciello (AMD)
2025-12-10 20:40   ` Russell, Kent
2025-12-16  2:45   ` Kasiviswanathan, Harish
2025-12-16 12:20     ` Mario Limonciello

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=20251210201510.3000-1-superm1@kernel.org \
    --to=superm1@kernel.org \
    --cc=amd-gfx@lists.freedesktop.org \
    /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.