On Wed, Aug 26, 2015 at 03:06:59PM +0200, Daniel Vetter wrote: > On Wed, Aug 26, 2015 at 12:55:57PM +0100, Chris Wilson wrote: > > As we mark the preallocated objects as bound, we should also flag them > > correctly as being map-and-fenceable (if appropriate!) so that latter > > users do not get confused and try and rebind the pinned vma in order to > > get a map-and-fenceable binding. > > > > Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk> > > Cc: "Goel, Akash" <akash.g...@intel.com> > > Cc: Daniel Vetter <daniel.vet...@ffwll.ch> > > Cc: Jesse Barnes <jbar...@virtuousgeek.org> > > Cc: sta...@vger.kernel.org > > Reviewed-by: Daniel Vetter <daniel.vet...@ffwll.ch> > > Jani, can you please pick up both? And some bugzilla references for either > would be great too - Chris? > > Oh and does patch 1 fix the execlist resume troubles? Execlist having > bigger contexts might be enough explanations for the apparent regression. > > And can we igt patch 1 somehow? E.g. with memory pressure plus doing an > mmap on the legacy fbdev ...
Actually add Jani ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
