diff options
| author | 2022-02-11 16:18:46 -0500 | |
|---|---|---|
| committer | 2022-02-11 16:19:23 -0500 | |
| commit | 461fa7b0ac565ef25c1da0ced31005dd437883a7 (patch) | |
| tree | efff4a96bcb9847a0774c3a579f48dc474255e34 /include/linux/mfd/git:/ssh:/git@git.zx2c4.com | |
| parent | drm/amdgpu: Reset OOB table error count info (diff) | |
| download | linux-dev-461fa7b0ac565ef25c1da0ced31005dd437883a7.tar.xz linux-dev-461fa7b0ac565ef25c1da0ced31005dd437883a7.zip | |
drm/amdgpu: remove ctx->lock
KMD reports a warning on holding a lock from drm_syncobj_find_fence,
when running amdgpu_test case “syncobj timeline test”.
ctx->lock was designed to prevent concurrent "amdgpu_ctx_wait_prev_fence"
calls and avoid dead reservation lock from GPU reset. since no reservation
lock is held in latest GPU reset any more, ctx->lock can be simply removed
and concurrent "amdgpu_ctx_wait_prev_fence" call also can be prevented by
PD root bo reservation lock.
call stacks:
=================
//hold lock
amdgpu_cs_ioctl->amdgpu_cs_parser_init->mutex_lock(&parser->ctx->lock);
…
//report warning
amdgpu_cs_dependencies->amdgpu_cs_process_syncobj_timeline_in_dep \
->amdgpu_syncobj_lookup_and_add_to_sync -> drm_syncobj_find_fence \
-> lockdep_assert_none_held_once
…
amdgpu_cs_ioctl->amdgpu_cs_parser_fini->mutex_unlock(&parser->ctx->lock);
Signed-off-by: Ken Xue <Ken.Xue@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'include/linux/mfd/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions
