projects / GitHub / LineageOS / android_kernel_motorola_exynos9610.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3c0556e) | patch
drm/nv50-nvc0: make sure vma is definitely unmapped when destroying bo
authorBen Skeggs <bskeggs@redhat.com>
Mon, 28 Feb 2011 04:22:12 +0000 (14:22 +1000)
committerBen Skeggs <bskeggs@redhat.com>
Mon, 28 Feb 2011 05:00:16 +0000 (15:00 +1000)
commit7db26623257a16c901a4b77bfc5096ee05304932
tree6c92f51db3b30ed6089f25b80e21d296bb4639a5tree | snapshot (tar.gz zip)
parent3c0556e9673f79e386b27768e27d18b3ce29e40ecommit | diff
drm/nv50-nvc0: make sure vma is definitely unmapped when destroying bo

Somehow fixes a misrendering + hang at GDM startup on my NVA8...

My first guess would have been stale TLB entries laying around that a new
bo then accidentally inherits.  That doesn't make a great deal of sense
however, as when we mapped the pages for the new bo the TLBs would've
gotten flushed anyway.

Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
drivers/gpu/drm/nouveau/nouveau_bo.c diff | blob | blame | history