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,
> > -
> * 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,
> -
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 timelines)
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 timelines), we lose the ability to pass the required
information down to