drm/amdkfd: Rework kfd_locked handling

Browse source

Currently, even if kfd_locked is set, a process is first
created and then removed to work around a race condition
in updating kfd_locked flag. Rework kfd_locked handling to
ensure no processes is created if kfd_locked is set. This
is achieved by updating kfd_locked under kfd_processes_mutex.
With this there is no need for kfd_locked to be an atomic
counter. Instead, it can be a regular integer.

Signed-off-by: Mukul Joshi <mukul.joshi@amd.com>
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

...

This commit is contained in:

Mukul Joshi 2022-05-31 14:39:36 -04:00 • committed by Alex Deucher

parent 6b22ef2574

commit fe1f05df59

4 changed files with 25 additions and 13 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

7

drivers/gpu/drm/amd/amdkfd/kfd_chardev.c

View file

21

drivers/gpu/drm/amd/amdkfd/kfd_device.c

View file

2

drivers/gpu/drm/amd/amdkfd/kfd_priv.h

View file

8

drivers/gpu/drm/amd/amdkfd/kfd_process.c

View file