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 13/15] drm/i915: Refactor direct GPU reset from request waiters
Date: Wed, 22 Feb 2017 14:16:49 +0000 [thread overview]
Message-ID: <0ad9adb2-ac54-79a5-caaa-62456a332705@linux.intel.com> (raw)
In-Reply-To: <20170222114610.5819-14-chris@chris-wilson.co.uk>
On 22/02/2017 11:46, Chris Wilson wrote:
> Combine the common code for the pair of waiters into a single function.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_gem_request.c | 21 ++++++++++++---------
> 1 file changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_request.c b/drivers/gpu/drm/i915/i915_gem_request.c
> index 42250eaf56ec..66d292384e60 100644
> --- a/drivers/gpu/drm/i915/i915_gem_request.c
> +++ b/drivers/gpu/drm/i915/i915_gem_request.c
> @@ -1024,6 +1024,16 @@ bool __i915_spin_request(const struct drm_i915_gem_request *req,
> return false;
> }
>
> +static bool __i915_reset_request(struct drm_i915_gem_request *request)
> +{
> + if (likely(!i915_reset_in_progress(&request->i915->gpu_error)))
> + return false;
> +
> + __set_current_state(TASK_RUNNING);
> + i915_reset(request->i915);
> + return true;
> +}
> +
> /**
> * i915_wait_request - wait until execution of request has finished
> * @req: the request to wait upon
> @@ -1087,11 +1097,8 @@ long i915_wait_request(struct drm_i915_gem_request *req,
> break;
>
> if (flags & I915_WAIT_LOCKED &&
> - i915_reset_in_progress(&req->i915->gpu_error)) {
> - __set_current_state(TASK_RUNNING);
> - i915_reset(req->i915);
> + __i915_reset_request(req))
> continue;
> - }
>
> if (signal_pending_state(state, current)) {
> timeout = -ERESTARTSYS;
> @@ -1160,12 +1167,8 @@ long i915_wait_request(struct drm_i915_gem_request *req,
> * to come along and update the breadcrumb (either directly
> * itself, or indirectly by recovering the GPU).
> */
> - if (flags & I915_WAIT_LOCKED &&
> - i915_reset_in_progress(&req->i915->gpu_error)) {
> - __set_current_state(TASK_RUNNING);
> - i915_reset(req->i915);
> + if (flags & I915_WAIT_LOCKED && __i915_reset_request(req))
> continue;
> - }
>
> /* Only spin if we know the GPU is processing this request */
> if (i915_spin_request(req, state, 2))
>
Okay in principle just unclear from the code now what it does. I suggest
__i915_check_and_reset_request or __i915_request_check_and_reset so it
is obvious the statement not only checks but also does stuff.
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-22 14:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 11:45 Pre-emption pre-enablement Chris Wilson
2017-02-22 11:45 ` [PATCH v2 01/15] drm/i915: Keep a global seqno per-engine Chris Wilson
2017-02-22 12:24 ` Tvrtko Ursulin
2017-02-22 11:45 ` [PATCH v2 02/15] drm/i915: Move reeerve_seqno() next to unreserve_seqno() Chris Wilson
2017-02-22 12:23 ` Joonas Lahtinen
2017-02-22 11:45 ` [PATCH v2 03/15] drm/i915: Use a local to shorten req->i915->gpu_error.wait_queue Chris Wilson
2017-02-22 11:45 ` [PATCH v2 04/15] drm/i915: Add ourselves to the gpu error waitqueue for the entire wait Chris Wilson
2017-02-22 11:46 ` [PATCH v2 05/15] drm/i915: Inline __i915_gem_request_wait_for_execute() Chris Wilson
2017-02-22 11:46 ` [PATCH v2 06/15] drm/i915: Deconstruct execute fence Chris Wilson
2017-02-22 11:46 ` [PATCH v2 07/15] drm/i915: Protect the request->global_seqno with the engine->timeline lock Chris Wilson
2017-02-22 12:29 ` Tvrtko Ursulin
2017-02-22 12:45 ` Chris Wilson
2017-02-22 13:13 ` Tvrtko Ursulin
2017-02-22 11:46 ` [PATCH v2 08/15] drm/i915: Take a reference whilst processing the signaler request Chris Wilson
2017-02-22 12:35 ` Tvrtko Ursulin
2017-02-22 11:46 ` [PATCH v2 09/15] drm/i915: Allow an request to be cancelled Chris Wilson
2017-02-22 13:08 ` Tvrtko Ursulin
2017-02-22 11:46 ` [PATCH v2 10/15] drm/i915: Remove the preempted request from the execution queue Chris Wilson
2017-02-22 13:33 ` Tvrtko Ursulin
2017-02-22 13:40 ` Chris Wilson
2017-02-22 13:50 ` Tvrtko Ursulin
2017-02-22 18:53 ` [PATCH v3] " Chris Wilson
2017-02-22 11:46 ` [PATCH v2 11/15] drm/i915: Exercise request cancellation using a mock selftest Chris Wilson
2017-02-22 13:46 ` Tvrtko Ursulin
2017-02-22 13:59 ` Chris Wilson
2017-02-22 14:03 ` Chris Wilson
2017-02-22 14:05 ` Tvrtko Ursulin
2017-02-22 11:46 ` [PATCH v2 12/15] drm/i915: Replace reset_wait_queue with default_wake_function Chris Wilson
2017-02-22 14:13 ` Tvrtko Ursulin
2017-02-22 11:46 ` [PATCH v2 13/15] drm/i915: Refactor direct GPU reset from request waiters Chris Wilson
2017-02-22 14:16 ` Tvrtko Ursulin [this message]
2017-02-22 14:26 ` Chris Wilson
2017-02-22 15:07 ` Tvrtko Ursulin
2017-02-22 11:46 ` [PATCH v2 14/15] drm/i915: Immediately process a reset before starting waiting Chris Wilson
2017-02-22 11:46 ` [PATCH v2 15/15] drm/i915: Remove one level of indention from wait-for-execute Chris Wilson
2017-02-22 14:22 ` Tvrtko Ursulin
2017-02-22 13:22 ` ✗ Fi.CI.BAT: failure for series starting with [v2,01/15] drm/i915: Keep a global seqno per-engine Patchwork
2017-02-22 20:52 ` ✗ Fi.CI.BAT: warning for series starting with [v2,01/15] drm/i915: Keep a global seqno per-engine (rev2) Patchwork
2017-02-22 20:56 ` Chris Wilson
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=0ad9adb2-ac54-79a5-caaa-62456a332705@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