From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jani Nikula Subject: Re: [Intel-gfx] [PATCH] drm/i915: Deny wrapping an userptr into a framebuffer Date: Tue, 13 Oct 2015 17:08:11 +0300 Message-ID: <8737xe50ac.fsf@intel.com> References: <1444742546-27401-1-git-send-email-chris@chris-wilson.co.uk> <561D0E72.9060507@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <561D0E72.9060507@linux.intel.com> Sender: stable-owner@vger.kernel.org To: Tvrtko Ursulin , Chris Wilson , intel-gfx@lists.freedesktop.org Cc: Daniel Vetter , stable@vger.kernel.org List-Id: intel-gfx@lists.freedesktop.org On Tue, 13 Oct 2015, Tvrtko Ursulin wrote: > On 13/10/15 14:22, Chris Wilson wrote: >> Pinning a userptr onto the hardware raises interesting questions about >> the lifetime of such a surface as the framebuffer extends that life >> beyond the client's address space. That is the hardware will need to >> keep scanning out from the backing storage even after the client wants >> to remap its address space. As the hardware pins the backing storage, >> the userptr becomes invalid and this raises a WARN when the clients >> tries to unmap its address space. The situation can be even more >> complicated when the buffer is passed between processes, between a >> client and display server, where the lifetime and hardware access is >> even more confusing. Deny it. > > Reviewed-by: Tvrtko Ursulin Pushed to drm-intel-fixes, thanks for the patch and review. BR, Jani. > > Regards, > > Tvrtko > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Jani Nikula, Intel Open Source Technology Center