From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 04/14] drm/i915: Inline __i915_gem_request_wait_for_execute()
Date: Fri, 17 Feb 2017 14:04:16 +0000 [thread overview]
Message-ID: <00c64800-afce-e860-0a3e-fceebd9ab117@linux.intel.com> (raw)
In-Reply-To: <20170214095413.26452-5-chris@chris-wilson.co.uk>
On 14/02/2017 09:54, Chris Wilson wrote:
> It had only one callsite and existed to keep the code clearer. Now
> having shared the wait-on-error between phases and with plans to change
> the wait-for-execute in the next few patches, remove the out of line
> wait loop and move it into the main body of i915_wait_request.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_gem_request.c | 78 ++++++++++++---------------------
> 1 file changed, 29 insertions(+), 49 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_request.c b/drivers/gpu/drm/i915/i915_gem_request.c
> index dcc0a7ab95dc..001fc9fedf49 100644
> --- a/drivers/gpu/drm/i915/i915_gem_request.c
> +++ b/drivers/gpu/drm/i915/i915_gem_request.c
> @@ -988,54 +988,6 @@ bool __i915_spin_request(const struct drm_i915_gem_request *req,
> return false;
> }
>
> -static long
> -__i915_request_wait_for_execute(struct drm_i915_gem_request *request,
> - unsigned int flags,
> - long timeout)
> -{
> - const int state = flags & I915_WAIT_INTERRUPTIBLE ?
> - TASK_INTERRUPTIBLE : TASK_UNINTERRUPTIBLE;
> - wait_queue_head_t *q = &request->i915->gpu_error.wait_queue;
> - DEFINE_WAIT(reset);
> - DEFINE_WAIT(wait);
> -
> - if (flags & I915_WAIT_LOCKED)
> - add_wait_queue(q, &reset);
> -
> - do {
> - prepare_to_wait(&request->execute.wait, &wait, state);
> -
> - if (i915_sw_fence_done(&request->execute))
> - break;
> -
> - if (flags & I915_WAIT_LOCKED &&
> - i915_reset_in_progress(&request->i915->gpu_error)) {
> - __set_current_state(TASK_RUNNING);
> - i915_reset(request->i915);
> - reset_wait_queue(q, &reset);
> - continue;
> - }
> -
> - if (signal_pending_state(state, current)) {
> - timeout = -ERESTARTSYS;
> - break;
> - }
> -
> - if (!timeout) {
> - timeout = -ETIME;
> - break;
> - }
> -
> - timeout = io_schedule_timeout(timeout);
> - } while (1);
> - finish_wait(&request->execute.wait, &wait);
> -
> - if (flags & I915_WAIT_LOCKED)
> - remove_wait_queue(q, &reset);
> -
> - return timeout;
> -}
> -
> /**
> * i915_wait_request - wait until execution of request has finished
> * @req: the request to wait upon
> @@ -1085,7 +1037,35 @@ long i915_wait_request(struct drm_i915_gem_request *req,
> add_wait_queue(errq, &reset);
>
> if (!i915_sw_fence_done(&req->execute)) {
> - timeout = __i915_request_wait_for_execute(req, flags, timeout);
> + DEFINE_WAIT(exec);
> +
> + do {
> + prepare_to_wait(&req->execute.wait, &exec, state);
> + if (i915_sw_fence_done(&req->execute))
> + break;
> +
> + if (flags & I915_WAIT_LOCKED &&
> + i915_reset_in_progress(&req->i915->gpu_error)) {
> + __set_current_state(TASK_RUNNING);
> + i915_reset(req->i915);
> + reset_wait_queue(errq, &reset);
> + continue;
> + }
> +
> + if (signal_pending_state(state, current)) {
> + timeout = -ERESTARTSYS;
> + break;
> + }
> +
> + if (!timeout) {
> + timeout = -ETIME;
> + break;
> + }
> +
> + timeout = io_schedule_timeout(timeout);
> + } while (1);
> + finish_wait(&req->execute.wait, &exec);
> +
> if (timeout < 0)
> goto complete;
>
>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-17 14:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 9:53 Prep work for preemption and GEM bugfixes Chris Wilson
2017-02-14 9:54 ` [PATCH v2 01/14] drm/i915: Keep a global seqno per-engine Chris Wilson
2017-02-15 17:05 ` Tvrtko Ursulin
2017-02-15 21:49 ` Chris Wilson
2017-02-15 22:20 ` Chris Wilson
2017-02-15 22:36 ` Chris Wilson
2017-02-16 8:10 ` Tvrtko Ursulin
2017-02-16 8:28 ` Chris Wilson
2017-02-14 9:54 ` [PATCH v2 02/14] drm/i915: Use a local to shorten req->i915->gpu_error.wait_queue Chris Wilson
2017-02-15 17:06 ` Tvrtko Ursulin
2017-02-14 9:54 ` [PATCH v2 03/14] drm/i915: Add ourselves to the gpu error waitqueue for the entire wait Chris Wilson
2017-02-15 17:11 ` Tvrtko Ursulin
2017-02-14 9:54 ` [PATCH v2 04/14] drm/i915: Inline __i915_gem_request_wait_for_execute() Chris Wilson
2017-02-17 14:04 ` Tvrtko Ursulin [this message]
2017-02-14 9:54 ` [PATCH v2 05/14] drm/i915: Deconstruct execute fence Chris Wilson
2017-02-17 14:26 ` Tvrtko Ursulin
2017-02-17 14:41 ` Chris Wilson
2017-02-17 14:55 ` Tvrtko Ursulin
2017-02-14 9:54 ` [PATCH v2 06/14] drm/i915: Protect the request->global_seqno with the engine->timeline lock Chris Wilson
2017-02-17 14:43 ` Tvrtko Ursulin
2017-02-22 12:38 ` Chris Wilson
2017-02-14 9:54 ` [PATCH v2 07/14] drm/i915: Take a reference whilst processing the signaler request Chris Wilson
2017-02-14 9:54 ` [PATCH v2 08/14] drm/i915: Allow an request to be cancelled Chris Wilson
2017-02-14 9:54 ` [PATCH v2 09/14] drm/i915: Remove the preempted request from the execution queue Chris Wilson
2017-02-14 9:54 ` [PATCH v2 10/14] drm/i915: Exercise request cancellation using a mock selftest Chris Wilson
2017-02-14 9:54 ` [PATCH v2 11/14] drm/i915: Replace reset_wait_queue with default_wake_function Chris Wilson
2017-02-14 9:54 ` [PATCH v2 12/14] drm/i915: Refactor direct GPU reset from request waiters Chris Wilson
2017-02-14 9:54 ` [PATCH v2 13/14] drm/i915: Immediately process a reset before starting waiting Chris Wilson
2017-02-14 9:54 ` [PATCH v2 14/14] drm/i915: Remove one level of indention from wait-for-execute Chris Wilson
2017-02-14 11:52 ` ✓ Fi.CI.BAT: success for series starting with [v2,01/14] drm/i915: Keep a global seqno per-engine Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00c64800-afce-e860-0a3e-fceebd9ab117@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox