Commit 681c774d authored Jul 09, 2019 by Chris Wilson

drm/i915/userptr: Don't mark readonly objects as dirty

If we map an object as readonly into the GTT, we know that the GPU
cannot have written to it and so the object is not dirty and we don't
need to flush the writes back to the system.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190709081718.27843-1-chris@chris-wilson.co.uk

parent f7ddc80e

drivers/gpu/drm/i915/gem/i915_gem_userptr.c

+8 −0

Original line number	Diff line number	Diff line
		@@ -663,6 +663,14 @@ i915_gem_userptr_put_pages(struct drm_i915_gem_object *obj,
		__i915_gem_object_release_shmem(obj, pages, true);
		i915_gem_gtt_finish_pages(obj, pages);

		/*
		* We always mark objects as dirty when they are used by the GPU,
		* just in case. However, if we set the vma as being read-only we know
		* that the object will never have been written to.
		*/
		if (i915_gem_object_is_readonly(obj))
		obj->mm.dirty = false;

		for_each_sgt_page(page, sgt_iter, pages) {
		if (obj->mm.dirty)
		/*