summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/bin/task-analyzer-report
diff options
context:
space:
mode:
authorChristian König <christian.koenig@amd.com>2026-04-16 15:32:11 +0200
committerAlex Deucher <alexander.deucher@amd.com>2026-05-11 17:46:43 -0400
commit44e5bc73bdcbec115cfe1c4b4394d25eb3deaff2 (patch)
tree35ccecd6c9f801b49bebba92636bdc407c9de3dd /tools/perf/scripts/python/bin/task-analyzer-report
parentd5971c5c34303a00bf841a902ca00a703602c500 (diff)
downloadlinux-44e5bc73bdcbec115cfe1c4b4394d25eb3deaff2.tar.gz
linux-44e5bc73bdcbec115cfe1c4b4394d25eb3deaff2.zip
drm/amdgpu: rework amdgpu_userq_signal_ioctl v3
This one was fortunately not looking so bad as the wait ioctl path, but there were still a few things which could be fixed/improved: 1. Allocating with GFP_ATOMIC was quite unnecessary, we can do that before taking the userq_lock. 2. Use a new mutex as protection for the fence_drv_xa so that we can do memory allocations while holding it. 3. Starting the reset timer is unnecessary when the fence is already signaled when we create it. 4. Cleanup error handling, avoid trying to free the queue when we don't even got one. v2: fix incorrect usage of xa_find, destroy the new mutex on error v3: cleanup ref ordering Signed-off-by: Christian König <christian.koenig@amd.com> Reviewed-by: Sunil Khatri <sunil.khatri@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> (cherry picked from commit 1609eb0f81a609d350169839128cecf298c84e7a)
Diffstat (limited to 'tools/perf/scripts/python/bin/task-analyzer-report')
0 files changed, 0 insertions, 0 deletions