diff options
author | 2025-05-13 10:09:04 +0800 | |
---|---|---|
committer | 2025-05-14 11:29:38 -0400 | |
commit | 96a86dcb5b5ca65564efeaaeecfca669e79a57e1 (patch) | |
tree | 8137929a954283b4720e74ab1e6a6c30d217d434 /scripts/gdb/linux/utils.py | |
parent | drm/amdgpu: read back register after written for VCN v4.0.5 (diff) | |
download | wireguard-linux-96a86dcb5b5ca65564efeaaeecfca669e79a57e1.tar.xz wireguard-linux-96a86dcb5b5ca65564efeaaeecfca669e79a57e1.zip |
drm/amdgpu: Fix circular locking in userq creation
A circular locking dependency was detected between the global
`adev->userq_mutex` and per-file `userq_mgr->userq_mutex` when
creating user queues. The issue occurs because:
1. `amdgpu_userq_suspend()` and `amdgpu_userq_resume` take `adev->userq_mutex` first, then
`userq_mgr->userq_mutex`
2. While `amdgpu_userq_create()` takes them in reverse order
This patch resolves the issue by:
1. Moving the `adev->userq_mutex` lock earlier in `amdgpu_userq_create()`
to cover the `amdgpu_userq_ensure_ev_fence()` call
2. Releasing it after we're done with both queue creation and the
scheduling halt check
v2: remove unused adev->userq_mutex lock (Prike)
Signed-off-by: Jesse Zhang <Jesse.Zhang@amd.com>
Reviewed-by: Prike Liang <Prike.Liang@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions