Re: [Intel-gfx] [PATCH] drm/i915: Treat foreign dma-buf imports as uncached

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

Re: [Intel-gfx] [PATCH] drm/i915: Treat foreign dma-buf imports as uncached

2015-08-11 Thread Chris Wilson
On Tue, Aug 11, 2015 at 02:58:59PM +0200, Daniel Vetter wrote: > On Tue, Aug 11, 2015 at 11:24:58AM +0100, Chris Wilson wrote: > > On Tue, Aug 11, 2015 at 12:12:08PM +0200, Daniel Vetter wrote: > > > On Mon, Aug 10, 2015 at 09:16:46PM +0100, Chris Wilson wrote: > > > > If the set of pages is being

Re: [Intel-gfx] [PATCH] drm/i915: Treat foreign dma-buf imports as uncached

2015-08-11 Thread Daniel Vetter
On Tue, Aug 11, 2015 at 11:24:58AM +0100, Chris Wilson wrote: > On Tue, Aug 11, 2015 at 12:12:08PM +0200, Daniel Vetter wrote: > > On Mon, Aug 10, 2015 at 09:16:46PM +0100, Chris Wilson wrote: > > > If the set of pages is being imported from another device, we cannot > > > assume that it is fully c

Re: [Intel-gfx] [PATCH] drm/i915: Treat foreign dma-buf imports as uncached

2015-08-11 Thread Chris Wilson
On Tue, Aug 11, 2015 at 12:12:08PM +0200, Daniel Vetter wrote: > On Mon, Aug 10, 2015 at 09:16:46PM +0100, Chris Wilson wrote: > > If the set of pages is being imported from another device, we cannot > > assume that it is fully coherent with the CPU cache, so mark it as such. > > However, if the so

Re: [Intel-gfx] [PATCH] drm/i915: Treat foreign dma-buf imports as uncached

2015-08-11 Thread Daniel Vetter
On Mon, Aug 10, 2015 at 09:16:46PM +0100, Chris Wilson wrote: > If the set of pages is being imported from another device, we cannot > assume that it is fully coherent with the CPU cache, so mark it as such. > However, if the source is the shared memory vgem allocator, we could > treat the buffer a

[Intel-gfx] [PATCH] drm/i915: Treat foreign dma-buf imports as uncached

2015-08-10 Thread Chris Wilson
If the set of pages is being imported from another device, we cannot assume that it is fully coherent with the CPU cache, so mark it as such. However, if the source is the shared memory vgem allocator, we could treat the buffer as being cached (so long as all parties agree in the case the same buff