summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorIlia Mirkin <imirkin@alum.mit.edu>2015-10-20 08:15:39 +0300
committerBen Skeggs <bskeggs@redhat.com>2015-11-03 07:56:06 +0300
commit04b8a4bd8e01e25b9fa9fa7b1c957a7346ae83c1 (patch)
tree11d83b2422f5bc487b464b59a78ca8e0ffdf1dd5 /tools/perf/scripts/python/call-graph-from-postgresql.py
parenta76edb8cec0cc864c8b72fa7e84a72336e033e23 (diff)
downloadlinux-04b8a4bd8e01e25b9fa9fa7b1c957a7346ae83c1.tar.xz
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 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions