From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4 11/16] drm/i915: Remove the preempted request from the execution queue
Date: Thu, 23 Feb 2017 12:11:34 +0000 [thread overview]
Message-ID: <54b7564f-cd29-2282-3abf-ac5864864e2d@linux.intel.com> (raw)
In-Reply-To: <20170223074422.4125-12-chris@chris-wilson.co.uk>
On 23/02/2017 07:44, Chris Wilson wrote:
> After the request is cancelled, we then need to remove it from the
> global execution timeline and return it to the context timeline, the
> inverse of submit_request().
>
> v2: Move manipulation of struct intel_wait to helpers
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem_request.c | 55 ++++++++++++++++++++++++++++++++
> drivers/gpu/drm/i915/i915_gem_request.h | 3 ++
> drivers/gpu/drm/i915/intel_breadcrumbs.c | 17 ++++++++--
> 3 files changed, 73 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_request.c b/drivers/gpu/drm/i915/i915_gem_request.c
> index 5ed52521397f..76e31cd7840e 100644
> --- a/drivers/gpu/drm/i915/i915_gem_request.c
> +++ b/drivers/gpu/drm/i915/i915_gem_request.c
> @@ -441,6 +441,55 @@ void i915_gem_request_submit(struct drm_i915_gem_request *request)
> spin_unlock_irqrestore(&engine->timeline->lock, flags);
> }
>
> +void __i915_gem_request_unsubmit(struct drm_i915_gem_request *request)
> +{
> + struct intel_engine_cs *engine = request->engine;
> + struct intel_timeline *timeline;
> +
> + assert_spin_locked(&engine->timeline->lock);
> +
> + /* Only unwind in reverse order, required so that the per-context list
> + * is kept in seqno/ring order.
> + */
> + GEM_BUG_ON(request->global_seqno != engine->timeline->seqno);
> + engine->timeline->seqno--;
> +
> + /* We may be recursing from the signal callback of another i915 fence */
> + spin_lock_nested(&request->lock, SINGLE_DEPTH_NESTING);
> + request->global_seqno = 0;
> + if (test_bit(DMA_FENCE_FLAG_ENABLE_SIGNAL_BIT, &request->fence.flags))
> + intel_engine_cancel_signaling(request);
> + spin_unlock(&request->lock);
> +
> + /* Transfer back from the global per-engine timeline to per-context */
> + timeline = request->timeline;
> + GEM_BUG_ON(timeline == engine->timeline);
> +
> + spin_lock(&timeline->lock);
> + list_move(&request->link, &timeline->requests);
> + spin_unlock(&timeline->lock);
> +
> + /* We don't need to wake_up any waiters on request->execute, they
> + * will get woken by any other event or us re-adding this request
> + * to the engine timeline (__i915_gem_request_submit()). The waiters
> + * should be quite adapt at finding that the request now has a new
> + * global_seqno to the one they went to sleep on.
> + */
> +}
> +
> +void i915_gem_request_unsubmit(struct drm_i915_gem_request *request)
> +{
> + struct intel_engine_cs *engine = request->engine;
> + unsigned long flags;
> +
> + /* Will be called from irq-context when using foreign fences. */
> + spin_lock_irqsave(&engine->timeline->lock, flags);
> +
> + __i915_gem_request_unsubmit(request);
> +
> + spin_unlock_irqrestore(&engine->timeline->lock, flags);
> +}
> +
> static int __i915_sw_fence_call
> submit_notify(struct i915_sw_fence *fence, enum i915_sw_fence_notify state)
> {
> @@ -1036,6 +1085,7 @@ long i915_wait_request(struct drm_i915_gem_request *req,
>
> intel_wait_init(&wait);
>
> +restart:
> reset_wait_queue(&req->execute, &exec);
> if (!intel_wait_update_request(&wait, req)) {
> do {
> @@ -1134,6 +1184,11 @@ long i915_wait_request(struct drm_i915_gem_request *req,
> /* Only spin if we know the GPU is processing this request */
> if (i915_spin_request(req, state, 2))
> break;
> +
> + if (!intel_wait_check_request(&wait, req)) {
> + intel_engine_remove_wait(req->engine, &wait);
> + goto restart;
> + }
> }
>
> intel_engine_remove_wait(req->engine, &wait);
> diff --git a/drivers/gpu/drm/i915/i915_gem_request.h b/drivers/gpu/drm/i915/i915_gem_request.h
> index b81f6709905c..5f73d8c0a38a 100644
> --- a/drivers/gpu/drm/i915/i915_gem_request.h
> +++ b/drivers/gpu/drm/i915/i915_gem_request.h
> @@ -274,6 +274,9 @@ void __i915_add_request(struct drm_i915_gem_request *req, bool flush_caches);
> void __i915_gem_request_submit(struct drm_i915_gem_request *request);
> void i915_gem_request_submit(struct drm_i915_gem_request *request);
>
> +void __i915_gem_request_unsubmit(struct drm_i915_gem_request *request);
> +void i915_gem_request_unsubmit(struct drm_i915_gem_request *request);
> +
> struct intel_rps_client;
> #define NO_WAITBOOST ERR_PTR(-1)
> #define IS_RPS_CLIENT(p) (!IS_ERR(p))
> diff --git a/drivers/gpu/drm/i915/intel_breadcrumbs.c b/drivers/gpu/drm/i915/intel_breadcrumbs.c
> index dd39e4f7a560..027c93e34c97 100644
> --- a/drivers/gpu/drm/i915/intel_breadcrumbs.c
> +++ b/drivers/gpu/drm/i915/intel_breadcrumbs.c
> @@ -453,7 +453,12 @@ void intel_engine_remove_wait(struct intel_engine_cs *engine,
> spin_unlock_irq(&b->lock);
> }
>
> -static bool signal_complete(struct drm_i915_gem_request *request)
> +static bool signal_valid(const struct drm_i915_gem_request *request)
> +{
> + return intel_wait_check_request(&request->signaling.wait, request);
> +}
> +
> +static bool signal_complete(const struct drm_i915_gem_request *request)
> {
> if (!request)
> return false;
> @@ -462,7 +467,7 @@ static bool signal_complete(struct drm_i915_gem_request *request)
> * signalled that this wait is already completed.
> */
> if (intel_wait_complete(&request->signaling.wait))
> - return true;
> + return signal_valid(request);
>
> /* Carefully check if the request is complete, giving time for the
> * seqno to be visible or if the GPU hung.
> @@ -542,13 +547,21 @@ static int intel_breadcrumbs_signaler(void *arg)
>
> i915_gem_request_put(request);
> } else {
> + DEFINE_WAIT(exec);
> +
> if (kthread_should_stop()) {
> GEM_BUG_ON(request);
> break;
> }
>
> + if (request)
> + add_wait_queue(&request->execute, &exec);
> +
> schedule();
>
> + if (request)
> + remove_wait_queue(&request->execute, &exec);
> +
> if (kthread_should_park())
> kthread_parkme();
> }
>
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-23 12:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 7:44 Preemption preparation pass phaw Chris Wilson
2017-02-23 7:44 ` [PATCH v4 01/16] drm/i915: Check against the signaled bit for fences/requests Chris Wilson
2017-02-23 7:44 ` [PATCH v4 02/16] drm/i915: Keep a global seqno per-engine Chris Wilson
2017-02-23 7:44 ` [PATCH v4 03/16] drm/i915: Move reserve_seqno() next to unreserve_seqno() Chris Wilson
2017-02-23 7:44 ` [PATCH v4 04/16] drm/i915: Use a local to shorten req->i915->gpu_error.wait_queue Chris Wilson
2017-02-23 7:44 ` [PATCH v4 05/16] drm/i915: Add ourselves to the gpu error waitqueue for the entire wait Chris Wilson
2017-02-23 7:44 ` [PATCH v4 06/16] drm/i915: Inline __i915_gem_request_wait_for_execute() Chris Wilson
2017-02-23 7:44 ` [PATCH v4 07/16] drm/i915: Deconstruct execute fence Chris Wilson
2017-02-23 7:44 ` [PATCH v4 08/16] drm/i915: Protect the request->global_seqno with the engine->timeline lock Chris Wilson
2017-02-23 7:44 ` [PATCH v4 09/16] drm/i915: Take a reference whilst processing the signaler request Chris Wilson
2017-02-23 7:44 ` [PATCH v4 10/16] drm/i915: Allow a request to be cancelled Chris Wilson
2017-02-23 7:44 ` [PATCH v4 11/16] drm/i915: Remove the preempted request from the execution queue Chris Wilson
2017-02-23 12:11 ` Tvrtko Ursulin [this message]
2017-02-23 7:44 ` [PATCH v4 12/16] drm/i915: Exercise request cancellation using a mock selftest Chris Wilson
2017-02-23 12:21 ` Tvrtko Ursulin
2017-02-23 7:44 ` [PATCH v4 13/16] drm/i915: Replace reset_wait_queue with default_wake_function Chris Wilson
2017-02-23 7:44 ` [PATCH v4 14/16] drm/i915: Refactor direct GPU reset from request waiters Chris Wilson
2017-02-23 12:23 ` Tvrtko Ursulin
2017-02-23 7:44 ` [PATCH v4 15/16] drm/i915: Immediately process a reset before starting waiting Chris Wilson
2017-02-23 12:35 ` Tvrtko Ursulin
2017-02-23 12:41 ` Chris Wilson
2017-02-23 12:45 ` Tvrtko Ursulin
2017-02-23 7:44 ` [PATCH v4 16/16] drm/i915: Remove one level of indention from wait-for-execute Chris Wilson
2017-02-23 8:18 ` ✓ Fi.CI.BAT: success for series starting with [v4,01/16] drm/i915: Check against the signaled bit for fences/requests Patchwork
2017-02-23 15:21 ` 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=54b7564f-cd29-2282-3abf-ac5864864e2d@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