Re: [Intel-gfx] [PATCH 13/18] drm/i915: Stop passing caller's num_dwords to engine->semaphore.signal()

2016-07-22 Thread Joonas Lahtinen
On pe, 2016-07-22 at 09:30 +0100, Chris Wilson wrote: > On Fri, Jul 22, 2016 at 11:15:59AM +0300, Joonas Lahtinen wrote: > > > > On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > > > > > > Rather than pass in the num_dwords that the caller wishes to use after > > > the signal command

Re: [Intel-gfx] [PATCH 13/18] drm/i915: Stop passing caller's num_dwords to engine->semaphore.signal()

2016-07-22 Thread Chris Wilson
On Fri, Jul 22, 2016 at 11:15:59AM +0300, Joonas Lahtinen wrote: > On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > > Rather than pass in the num_dwords that the caller wishes to use after > > the signal command packet, split the breadcrumb emission into two phases > > and have both the

Re: [Intel-gfx] [PATCH 13/18] drm/i915: Stop passing caller's num_dwords to engine->semaphore.signal()

2016-07-22 Thread Joonas Lahtinen
On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > Rather than pass in the num_dwords that the caller wishes to use after > the signal command packet, split the breadcrumb emission into two phases > and have both the signal and breadcrumb individiually acquire space on > the ring. This makes

[Intel-gfx] [PATCH 13/18] drm/i915: Stop passing caller's num_dwords to engine->semaphore.signal()

2016-07-20 Thread Chris Wilson
Rather than pass in the num_dwords that the caller wishes to use after the signal command packet, split the breadcrumb emission into two phases and have both the signal and breadcrumb individiually acquire space on the ring. This makes the interface simpler for the reader, and will simplify for