summaryrefslogtreecommitdiff
path: root/init/init_task.c
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2013-08-06 18:01:14 (GMT)
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-08-18 17:37:41 (GMT)
commit884020bf3d2a3787a1cc6df902e98e0eec60330b (patch)
treedc65ac88ef7c7a15e1f773c0f5255178e392b4cd /init/init_task.c
parent63b66e5ba54b15a6592be00555d762db6db739ce (diff)
downloadlinux-884020bf3d2a3787a1cc6df902e98e0eec60330b.tar.xz
drm/i915: Invalidate TLBs for the rings after a reset
After any "soft gfx reset" we must manually invalidate the TLBs associated with each ring. Empirically, it seems that a suspend/resume or D3-D0 cycle count as a "soft reset". The symptom is that the hardware would fail to note the new address for its status page, and so it would continue to write the shadow registers and breadcrumbs into the old physical address (now used by something completely different, scary). Whereas the driver would read the new status page and never see any progress, it would appear that the GPU hung immediately upon resume. Based on a patch by naresh kumar kachhi <naresh.kumar.kacchi@intel.com> Reported-by: Thiago Macieira <thiago@kde.org> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=64725 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Tested-by: Thiago Macieira <thiago@kde.org> Cc: stable@vger.kernel.org Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'init/init_task.c')
0 files changed, 0 insertions, 0 deletions