summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorMario Limonciello <mario.limonciello@amd.com>2026-09-15 12:51:24 -0500
committerAlex Deucher <alexander.deucher@amd.com>2026-09-17 11:58:04 -0400
commit7f9caa70aef0950e06d395ca0035831214d88187 (patch)
tree2d61a77a5db35669f753793dbe6a0eac5ec6450c /tools/perf/scripts/python
parent0d2f4cfa564355fcbbc71498fd8ec09243036109 (diff)
downloadlinux-next-7f9caa70aef0950e06d395ca0035831214d88187.tar.gz
linux-next-7f9caa70aef0950e06d395ca0035831214d88187.zip
drm/amdgpu: Skip KFD mapping clear before initialization
amdgpu_amdkfd_clear_kfd_mapping() assumes that a non-NULL kfd_dev has a fully populated node array. This is not true when KFD device initialization fails after probe. For example, kgd2kfd_device_init() sets num_nodes before checking PCIe atomics support. On Polaris systems without the required atomics, it returns before allocating nodes[0], but the kfd_dev remains attached to the amdgpu device. A later GPU reset then dereferences nodes[0]->id. Require the authoritative KFD initialization flag before walking the node array, matching the existing KFD reset and teardown paths. Fixes: 70cadefcc616 ("drm/amdgpu: unmap all user mappings of framebuffer and doorbell before mode1 reset") Closes: https://gitlab.freedesktop.org/drm/amd/-/work_items/5833 Reviewed-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> (cherry picked from commit 4ac1835823c47903fbb278bbf474773c46f59edc) Cc: stable@vger.kernel.org
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions