Re: [Intel-gfx] [PATCH] drm/i915: Do not re-allocate vmas in aliasing ppgtt

2015-04-23 Thread Mika Kuoppala
Michel Thierry writes: > Aliasing ppgtt is fully allocated right after creation, thus shouldn't > need to call allocate_va_range in i915_vma_bind. > > This duplication started after commit 5c5f645773b6d147bf68c350674dc3ef4f8de83d > ("drm/i915: drm/i915: Unify aliasing ppgtt handling"), as aliasin

Re: [Intel-gfx] [PATCH] drm/i915: Do not re-allocate vmas in aliasing ppgtt

2015-04-22 Thread shuang . he
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang...@intel.com) Task id: 6248 -Summary- Platform Delta drm-intel-nightly Series Applied PNV

Re: [Intel-gfx] [PATCH] drm/i915: Do not re-allocate vmas in aliasing ppgtt

2015-04-22 Thread Chris Wilson
On Wed, Apr 22, 2015 at 05:13:38PM +0100, Michel Thierry wrote: > Aliasing ppgtt is fully allocated right after creation, thus shouldn't > need to call allocate_va_range in i915_vma_bind. And? > This duplication started after commit 5c5f645773b6d147bf68c350674dc3ef4f8de83d > ("drm/i915: drm/i915

[Intel-gfx] [PATCH] drm/i915: Do not re-allocate vmas in aliasing ppgtt

2015-04-22 Thread Michel Thierry
Aliasing ppgtt is fully allocated right after creation, thus shouldn't need to call allocate_va_range in i915_vma_bind. This duplication started after commit 5c5f645773b6d147bf68c350674dc3ef4f8de83d ("drm/i915: drm/i915: Unify aliasing ppgtt handling"), as aliasing ppgtt now also uses allocate_va_