Re: [Intel-gfx] [PATCH 07/11] drm/i915: Fix up map and fenceable for VMA

2013-07-10 Thread Daniel Vetter
On Wed, Jul 10, 2013 at 09:39:00AM -0700, Ben Widawsky wrote: > On Tue, Jul 09, 2013 at 09:16:54AM +0200, Daniel Vetter wrote: > > On Mon, Jul 08, 2013 at 11:08:38PM -0700, Ben Widawsky wrote: > > > formerly: "drm/i915: Create VMAs (part 3.5) - map and fenceable > > > tracking" > > > > > > The map

Re: [Intel-gfx] [PATCH 07/11] drm/i915: Fix up map and fenceable for VMA

2013-07-10 Thread Ben Widawsky
On Tue, Jul 09, 2013 at 09:16:54AM +0200, Daniel Vetter wrote: > On Mon, Jul 08, 2013 at 11:08:38PM -0700, Ben Widawsky wrote: > > formerly: "drm/i915: Create VMAs (part 3.5) - map and fenceable > > tracking" > > > > The map_and_fenceable tracking is per object. GTT mapping, and fences > > only ap

Re: [Intel-gfx] [PATCH 07/11] drm/i915: Fix up map and fenceable for VMA

2013-07-09 Thread Daniel Vetter
On Mon, Jul 08, 2013 at 11:08:38PM -0700, Ben Widawsky wrote: > formerly: "drm/i915: Create VMAs (part 3.5) - map and fenceable > tracking" > > The map_and_fenceable tracking is per object. GTT mapping, and fences > only apply to global GTT. As such, object operations which are not > performed on

[Intel-gfx] [PATCH 07/11] drm/i915: Fix up map and fenceable for VMA

2013-07-08 Thread Ben Widawsky
formerly: "drm/i915: Create VMAs (part 3.5) - map and fenceable tracking" The map_and_fenceable tracking is per object. GTT mapping, and fences only apply to global GTT. As such, object operations which are not performed on the global GTT should not effect mappable or fenceable characteristics.