diff options
| author | Mario Limonciello <mario.limonciello@amd.com> | 2026-09-15 12:51:24 -0500 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2026-09-17 11:38:29 -0400 |
| commit | 4ac1835823c47903fbb278bbf474773c46f59edc (patch) | |
| tree | 7f8a8bbae5166c6f95662836d47e4042ab72ac45 /tools/perf/scripts/python/flamegraph.py | |
| parent | 346d81ef808ba28465a3f19f2a0d63a758e7409c (diff) | |
| download | linux-4ac1835823c47903fbb278bbf474773c46f59edc.tar.gz linux-4ac1835823c47903fbb278bbf474773c46f59edc.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>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions
