drm/i915: pass which operation triggered the frontbuffer tracking
authorPaulo Zanoni <paulo.r.zanoni@intel.com>
Fri, 13 Feb 2015 19:23:44 +0000 (17:23 -0200)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Tue, 17 Mar 2015 21:29:51 +0000 (22:29 +0100)
commita4001f1b75cdb06db0febd9e72d3631f73ba8171
tree3c4db0ac56bb5b6e1480be8d275ab130b9e44b2f
parentff42e093e9c9c17a6e1d6aab24875a36795f926e
drm/i915: pass which operation triggered the frontbuffer tracking

We want to port FBC to the frontbuffer tracking infrastructure, but
for that we need to know what caused the object invalidation so
we can react accordingly: CPU mmaps need manual, GTT mmaps and
flips don't need handling and ring rendering needs nukes.

v2: - s/ORIGIN_RENDER/ORIGIN_CS/ (Daniel, Rodrigo)
    - Fix copy/pasted wrong documentation
    - Rebase
v3: - Rebase
v4: - Don't pass the operation to flushes (Daniel).

Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drivers/gpu/drm/i915/i915_drv.h
drivers/gpu/drm/i915/i915_gem.c
drivers/gpu/drm/i915/i915_gem_execbuffer.c
drivers/gpu/drm/i915/intel_drv.h
drivers/gpu/drm/i915/intel_frontbuffer.c
This page took 0.028142 seconds and 5 git commands to generate.