diff options
| author | Richard Zhao <rizhao@nvidia.com> | 2017-11-13 18:22:13 -0500 |
|---|---|---|
| committer | mobile promotions <svcmobile_promotions@nvidia.com> | 2017-11-16 15:38:54 -0500 |
| commit | 42bc87167ad6eac96ff362bea82bcfdc9730e2ec (patch) | |
| tree | 01e5ef1347adf590769dcf85a6ad96d3d22a2abd /drivers/gpu/nvgpu/gk20a/hal.c | |
| parent | 326f97187a7757fbf388bebad1b3cc8520593ee7 (diff) | |
gpu: nvgpu: vgpu: abort the channel right after force reset it
For gp10b and previous chips, RM server will issue fake mmu fault to
reset the channel. And the mmu fault event will be sent to vgpu client,
which will cause the client to abort the channel or tsg.
But on gv11b, RM server doesn't issue fake mmu fault any more. So I need
to abort it right after the force reset is finished.
Jira EVLR-1671
Change-Id: I11399fda84d31086ba1d4ffde5948e409cde2a28
Signed-off-by: Richard Zhao <rizhao@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1597378
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/gk20a/hal.c')
0 files changed, 0 insertions, 0 deletions