drm2/i915/i915_gem.c

85 					 struct drm_i915_fence_reg *fence,
107 	/* As we do not have an associated fence register, we will force
1464  * the GTT (if needed), allocating and programming a fence register (again,
1469  * from the GTT and/or fence registers to make room.  So performance may
1470  * suffer if the GTT working set is large or there are few fence registers
1630  * object through the GTT and then lose the fence register due to
1678 	/* Previous chips need a power-of-two fence region when tiling */
1695  * potential fence register mapping.
1704 	 * if a fence register is needed for the object.
1712 	 * fence register that can contain the object.
1845  * a fence register, and mapping the appropriate aperture address into
2423 	/* The fence registers are invalidated so clear them out */
2748 	/* release the fence reg _after_ flushing */
2932 			       struct drm_i915_fence_reg *fence)
2934 	return fence - dev_priv->fence_regs;
2943 					 struct drm_i915_fence_reg *fence,
2948 	int fence_reg = fence_number(dev_priv, fence);
2951 	 * the update to the fence register we need to take extreme
2952 	 * measures on SNB+. In theory, the write to the fence register
2958 	 * transactions before updating the fence register.
2966 		fence->obj = obj;
2967 		list_move_tail(&fence->lru_list, &dev_priv->mm.fence_list);
2970 		fence->obj = NULL;
2971 		list_del_init(&fence->lru_list);
2986 	/* Ensure that all CPU reads are completed before installing a fence
2987 	 * and all writes before removing the fence.
3051  * @obj: object to map through a fence reg
3055  * This function walks the fence regs looking for a free one for @obj,
3061  * For an untiled surface, this removes any existing fence.
3073 	 * will need to serialise the write to the associated fence register?
3081 	/* Just update our place in the LRU if our fence is getting reused. */
3448 		/* Before SandyBridge, you could not use tiling or fence
4468 	/* Initialize fence registers to zero */