On Thu, Aug 23, 2012 at 01:12:52PM +0100, Chris Wilson wrote: > This prevents the case of unbinding the object in order to process the > relocations through the GTT and then rebinding it only to then proceed > to use cpu relocations as the object is now in the CPU write domain. By > choosing to use cpu relocations up front, we can therefore avoid the > rebind penalty. > > Signed-off-by: Chris Wilson <[email protected]> lgtm, applied to dinq. -Daniel -- Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
- [Intel-gfx] [PATCH 1/3] drm/i915: Use a non-blocking wait fo... Chris Wilson
- [Intel-gfx] [PATCH 2/3] drm/i915: Use cpu relocations i... Chris Wilson
- Re: [Intel-gfx] [PATCH 2/3] drm/i915: Use cpu reloc... Daniel Vetter
- [Intel-gfx] [PATCH 3/3] drm/i915: Avoid unbinding due t... Chris Wilson
- Re: [Intel-gfx] [PATCH 3/3] drm/i915: Avoid unbindi... Daniel Vetter
- Re: [Intel-gfx] [PATCH 3/3] drm/i915: Avoid unb... Chris Wilson
- [Intel-gfx] [PATCH] drm/i915: Avoid unbindi... Chris Wilson
- Re: [Intel-gfx] [PATCH] drm/i915: Avoi... Daniel Vetter
- Re: [Intel-gfx] [PATCH 1/3] drm/i915: Use a non-blockin... Daniel Vetter
- [Intel-gfx] [PATCH 1/2] drm/i915: Juggle code order... Chris Wilson
- [Intel-gfx] [PATCH 2/2] drm/i915: Use a non-blo... Chris Wilson
