Re: [Intel-gfx] [PATCH RFC 3/4] drm/i915: add SVM execbuf ioctl v10

2016-08-17 Thread Jesse Barnes
On Wed, 2016-08-17 at 12:37 +0300, Joonas Lahtinen wrote: > On ma, 2016-08-15 at 09:26 -0700, Jesse Barnes wrote: > > > > On Mon, 2016-08-15 at 15:34 +0300, Mika Kuoppala wrote: > > > > > > > > > No idea yet why we would need to limit for rcs only. > > > > > I went back and forth; I think I

Re: [Intel-gfx] [PATCH RFC 3/4] drm/i915: add SVM execbuf ioctl v10

2016-08-17 Thread Joonas Lahtinen
On ma, 2016-08-15 at 09:26 -0700, Jesse Barnes wrote: > On Mon, 2016-08-15 at 15:34 +0300, Mika Kuoppala wrote: > > > > No idea yet why we would need to limit for rcs only. > > > I went back and forth; I think I did test on the BLT ring and maybe one > of the video rings and things worked on at

Re: [Intel-gfx] [PATCH RFC 3/4] drm/i915: add SVM execbuf ioctl v10

2016-08-16 Thread Jesse Barnes
On Mon, 2016-08-15 at 15:34 +0300, Mika Kuoppala wrote: > Chris Wilson writes: > > > > > On Mon, Aug 15, 2016 at 02:48:06PM +0300, Mika Kuoppala wrote: > > > > > > From: Jesse Barnes > > > > > > We just need to pass in an address to execute

Re: [Intel-gfx] [PATCH RFC 3/4] drm/i915: add SVM execbuf ioctl v10

2016-08-15 Thread Mika Kuoppala
Chris Wilson writes: > On Mon, Aug 15, 2016 at 02:48:06PM +0300, Mika Kuoppala wrote: >> From: Jesse Barnes >> >> We just need to pass in an address to execute and some flags, since we >> don't have to worry about buffer relocation or any of

Re: [Intel-gfx] [PATCH RFC 3/4] drm/i915: add SVM execbuf ioctl v10

2016-08-15 Thread Chris Wilson
On Mon, Aug 15, 2016 at 02:48:06PM +0300, Mika Kuoppala wrote: > From: Jesse Barnes > > We just need to pass in an address to execute and some flags, since we > don't have to worry about buffer relocation or any of the other usual > stuff. Returns a fence to be used