diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2016-11-16 19:07:04 +0000 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2016-11-18 11:15:59 +0000 |
commit | 5b8c8aec8e8ef999c8b3eaa699e46ef25550d118 (patch) | |
tree | dce0a2b7b18b8c59bb9c59651d7b0adbc1ee32f2 /drivers/gpu/drm/i915/i915_vma.h | |
parent | d806e6828be36ce21173340ba3d0078345bd12bc (diff) | |
download | linux-stable-5b8c8aec8e8ef999c8b3eaa699e46ef25550d118.tar.gz linux-stable-5b8c8aec8e8ef999c8b3eaa699e46ef25550d118.tar.bz2 linux-stable-5b8c8aec8e8ef999c8b3eaa699e46ef25550d118.zip |
drm/i915: Move frontbuffer CS write tracking from ggtt vma to object
I tried to avoid having to track the write for every VMA by only
tracking writes to the ggtt. However, for the purposes of frontbuffer
tracking this is insufficient as we need to invalidate around writes not
just to the the ggtt but all aliased ppgtt views of the framebuffer. By
moving the critical section to the object and only doing so for
framebuffer writes we can reduce the tracking even further by only
watching framebuffers and not vma.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20161116190704.5293-1-chris@chris-wilson.co.uk
Tested-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Diffstat (limited to 'drivers/gpu/drm/i915/i915_vma.h')
-rw-r--r-- | drivers/gpu/drm/i915/i915_vma.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/gpu/drm/i915/i915_vma.h b/drivers/gpu/drm/i915/i915_vma.h index 2e49f5dd6107..85446f0b0b3f 100644 --- a/drivers/gpu/drm/i915/i915_vma.h +++ b/drivers/gpu/drm/i915/i915_vma.h @@ -80,7 +80,6 @@ struct i915_vma { unsigned int active; struct i915_gem_active last_read[I915_NUM_ENGINES]; - struct i915_gem_active last_write; struct i915_gem_active last_fence; /** |