summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorMatthew Auld <matthew.auld@intel.com>2021-10-27 19:18:11 +0300
committerMatthew Auld <matthew.auld@intel.com>2021-11-02 12:44:06 +0300
commitc52b3b489783b3b244c8134204d542a4d07030b7 (patch)
treeafbc59ec762794eeb7d46e36559822dfd22c3d92 /tools/perf/scripts/python/exported-sql-viewer.py
parent3ea355b234d7d3e543b89e55c66d57db50ef1581 (diff)
downloadlinux-c52b3b489783b3b244c8134204d542a4d07030b7.tar.xz
drm/i915/clflush: disallow on discrete
We seem to have an unfortunate issue where we arrive from: i915_gem_object_flush_if_display+0x86/0xd0 [i915] intel_user_framebuffer_dirty+0x1a/0x50 [i915] drm_mode_dirtyfb_ioctl+0xfb/0x1b0 which can be before the pages are populated(and pinned for display), and so i915_gem_object_has_struct_page() might still return true, as per the ttm backend. We could re-order the later get_pages() call here, but since on discrete everything should already be coherent, with the exception of the display engine, and even there display surfaces must be allocated in device local-memory anyway, so there should in theory be no conceivable reason to ever call i915_gem_clflush_object() on discrete. References: https://gitlab.freedesktop.org/drm/intel/-/issues/4320 Signed-off-by: Matthew Auld <matthew.auld@intel.com> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20211027161813.3094681-2-matthew.auld@intel.com
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions