diff options
| author | Aparna Das <aparnad@nvidia.com> | 2018-07-06 13:45:53 -0400 |
|---|---|---|
| committer | mobile promotions <svcmobile_promotions@nvidia.com> | 2018-07-09 19:36:17 -0400 |
| commit | ad3b170f43dbd5ddb2698c5a193968ae1e584491 (patch) | |
| tree | f27b4fd4c695920616ed360df5e95d9b46b88a95 /drivers/gpu/nvgpu/gv11b/fb_gv11b.c | |
| parent | 0ddd219697155bcb64aaa04544108519686e16cc (diff) | |
gpu: nvgpu: vgpu: ring doorbell after enabling TSG
In some use cases client will disable and preempt TSG and then re-enable it
using IOCTLs provided
In case there is only one context getting re-enabled and there is no other job
submission in parallel runlist fetcher will just sleep until doorbell is
received next time
This causes above mentioned test cases to stall after re-enabling TSG
until some one submits a new job and triggers a doorbell
Fix this by explicitly triggering doorbell in vgpu code
after we enable all channels in TSG.
Bug 2205192
Change-Id: I25d643e06152adc6aaf874baf610316f6cd8f13f
Signed-off-by: Aparna Das <aparnad@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1772948
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/gv11b/fb_gv11b.c')
0 files changed, 0 insertions, 0 deletions