diff options
| author | Deepak Nibade <dnibade@nvidia.com> | 2016-01-07 04:01:12 -0500 |
|---|---|---|
| committer | Terje Bergstrom <tbergstrom@nvidia.com> | 2016-01-11 12:06:31 -0500 |
| commit | 0ce201e8de6a320b70f1f34d05202650b9b5a046 (patch) | |
| tree | 81898989fe240bf10190d15887cbfc98fbc45fa3 /drivers/gpu/nvgpu/gk20a/gr_gk20a.h | |
| parent | 9713e3572a740216c6ecbc2257349be51c204a67 (diff) | |
gpu: nvgpu: stop timer on failing channel
In gk20a_channel_timeout_handler(), below deadlock scenario
is possible :
thread 1:
- take global lock g->ch_wdt_lock
- identify timed out channel (as ch1)
- check engine status which is stuck
- identify failing channel on engine as ch2
- we need to trigger recovery with ch2
- as part of recovery, call channel_abort() for ch2
- in channel_abort(), we wait to cancel the timer wq
- but timer wq for ch2 never completes due to thread 2
thread 2:
- ch2 has already timed out
- to process, we wait for global lock g->ch_wdt_lock
- this lock needs to be released by thread 1
To fix this, cancel the timer (through flag) of ch2
(failing channel on engine) before triggering recovery
on that channel
Bug 200164753
Change-Id: Idb42d01c8440a53f43cb5e87e41f1c283f7e8fcf
Signed-off-by: Deepak Nibade <dnibade@nvidia.com>
Reviewed-on: http://git-master/r/929924
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
Tested-by: Terje Bergstrom <tbergstrom@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/gk20a/gr_gk20a.h')
0 files changed, 0 insertions, 0 deletions