summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/i915_guc_reg.h
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2016-08-04 07:52:27 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2016-08-04 08:09:18 +0100
commitaa653a685d816648dd903f76c14a30d8baa23933 (patch)
treeeeb146f9540630bd73dc9eb4e66905a20c65c14e /drivers/gpu/drm/i915/i915_guc_reg.h
parent15717de219f2ea4792d27ff62c29d08e46cda7f8 (diff)
downloadlinux-aa653a685d816648dd903f76c14a30d8baa23933.tar.gz
linux-aa653a685d816648dd903f76c14a30d8baa23933.tar.bz2
linux-aa653a685d816648dd903f76c14a30d8baa23933.zip
drm/i915: Be more careful when unbinding vma
When we call i915_vma_unbind(), we will wait upon outstanding rendering. This will also trigger a retirement phase, which may update the object lists. If, we extend request tracking to the VMA itself (rather than keep it at the encompassing object), then there is a potential that the obj->vma_list be modified for other elements upon i915_vma_unbind(). As a result, if we walk over the object list and call i915_vma_unbind(), we need to be prepared for that list to change. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/1470293567-10811-8-git-send-email-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/i915_guc_reg.h')
0 files changed, 0 insertions, 0 deletions