Re: [Intel-gfx] [PATCH 08/41] drm/i915: Rearrange i915_wait_request() accounting with callers

2016-10-19 Thread Joonas Lahtinen
On ti, 2016-10-18 at 19:51 +0100, Matthew Auld wrote: > > > >   * Returns 0 if the request was found within the alloted time. > > Else returns the > >   * errno with remaining time filled in timeout argument. > >   */ > > -int i915_wait_request(struct drm_i915_gem_request *req, > > -  

Re: [Intel-gfx] [PATCH 08/41] drm/i915: Rearrange i915_wait_request() accounting with callers

2016-10-18 Thread Matthew Auld
> * Returns 0 if the request was found within the alloted time. Else returns > the > * errno with remaining time filled in timeout argument. > */ > -int i915_wait_request(struct drm_i915_gem_request *req, > - unsigned int flags, > - s64 *timeout, > -

Re: [Intel-gfx] [PATCH 08/41] drm/i915: Rearrange i915_wait_request() accounting with callers

2016-10-17 Thread Joonas Lahtinen
On pe, 2016-10-14 at 13:18 +0100, Chris Wilson wrote: > Our low-level wait routine has evolved from our generic wait interface > that handled unlocked, RPS boosting, waits with time tracking. If we > push our GEM fence tracking to use reservation_objects (required for > handling multiple