summaryrefslogtreecommitdiff
path: root/CREDITS
diff options
context:
space:
mode:
authorMatthew Auld <matthew.auld@intel.com>2022-06-22 16:59:19 +0100
committerJani Nikula <jani.nikula@intel.com>2022-06-27 18:12:10 +0300
commit79538490fd7ade244dba400923e792519a2bdfea (patch)
tree6f77afcda0f6e150d3bf8c6e1db89d9fcb67d9ce /CREDITS
parent7d23a80dc9720a378707edc03a7275d5a372355f (diff)
drm/i915: tweak the ordering in cpu_write_needs_clflushdrm-intel-fixes-2022-06-29
For imported dma-buf objects we leave the object as cache_coherent = 0 across all platforms, which is reasonable given that have no clue what the memory underneath is, and its not like the driver can ever manually clflush the pages anyway (like with i915_gem_clflush_object) for such objects. However on discrete we choose to treat cache_dirty = true as a programmer error, leading to a warning. The simplest fix looks to be to just change the ordering in cpu_write_needs_clflush to prevent ever setting cache_dirty for dma-buf objects on discrete. Fixes: d028a7690d87 ("drm/i915/dmabuf: Fix prime_mmap to work when using LMEM") Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/5266 Signed-off-by: Matthew Auld <matthew.auld@intel.com> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com> Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com> Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20220622155919.355081-1-matthew.auld@intel.com (cherry picked from commit 563aaf4a928def2d36d1b3de0a4b515e2477b4da) Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions