diff options
| author | Deepak Nibade <dnibade@nvidia.com> | 2015-12-10 03:58:32 -0500 |
|---|---|---|
| committer | Terje Bergstrom <tbergstrom@nvidia.com> | 2015-12-10 11:39:42 -0500 |
| commit | c4ac1ed369cb5737de10924908d97be9f11ec875 (patch) | |
| tree | 294d2bc504f16cad8653413d63a6b47c6753adaa /drivers/gpu/nvgpu/vgpu/gk20a | |
| parent | 54f76d1ac6cf0ace524e073076578c891d1b3f79 (diff) | |
gpu: nvgpu: preempt before adjusting fences
Current sequence in gk20a_disable_channel() is
- disable channel in gk20a_channel_abort()
- adjust pending fence in gk20a_channel_abort()
- preempt channel
But this leads to scenarios where syncpoint has
min > max value
Hence to fix this, make sequence in gk20a_disable_channel()
- disable channel in gk20a_channel_abort()
- preempt channel in gk20a_channel_abort()
- adjust pending fence in gk20a_channel_abort()
If gk20a_channel_abort() is called from other API where
preemption is not needed, then use channel_preempt
flag and do not preempt channel in those cases
Bug 1683059
Change-Id: I4d46d4294cf8597ae5f05f79dfe1b95c4187f2e3
Signed-off-by: Deepak Nibade <dnibade@nvidia.com>
Reviewed-on: http://git-master/r/921290
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
Tested-by: Terje Bergstrom <tbergstrom@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/vgpu/gk20a')
0 files changed, 0 insertions, 0 deletions