summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/omapdrm
diff options
context:
space:
mode:
authorIlia Mirkin <imirkin@alum.mit.edu>2015-10-20 01:15:39 -0400
committerBen Skeggs <bskeggs@redhat.com>2015-10-22 09:10:52 +1000
commit2a6c521bb41ce862e43db46f52e7681d33e8d771 (patch)
tree4ee9f116d3adc5aeec6b9462902c5755590c5e3b /drivers/gpu/drm/omapdrm
parent25d295882a1adfcdaaad85369289677b87c7c8f0 (diff)
downloadlinux-2a6c521bb41ce862e43db46f52e7681d33e8d771.tar.gz
linux-2a6c521bb41ce862e43db46f52e7681d33e8d771.tar.bz2
linux-2a6c521bb41ce862e43db46f52e7681d33e8d771.zip
drm/nouveau/gem: return only valid domain when there's only one
On nv50+, we restrict the valid domains to just the one where the buffer was originally created. However after the buffer is evicted to system memory, we might move it back to a different domain that was not originally valid. When sharing the buffer and retrieving its GEM_INFO data, we still want the domain that will be valid for this buffer in a pushbuf, not the one where it currently happens to be. This resolves fdo#92504 and several others. These are due to suspend evicting all buffers, making it more likely that they temporarily end up in the wrong place. Cc: stable@vger.kernel.org Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92504 Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/omapdrm')
0 files changed, 0 insertions, 0 deletions