From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915/breadcrumbs: Ignore unsubmitted signalers
Date: Wed, 7 Feb 2018 10:40:46 +0000 [thread overview]
Message-ID: <ced00ce1-9fd6-89c2-1e39-126d51a8bd49@linux.intel.com> (raw)
In-Reply-To: <20180206094633.30181-1-chris@chris-wilson.co.uk>
On 06/02/2018 09:46, Chris Wilson wrote:
> When a request is preempted, it is unsubmitted from the HW queue and
> removed from the active list of breadcrumbs. In the process, this
> however triggers the signaler and it may see the clear rbtree with the
> old, and still valid, seqno. This confuses the signaler into action and
> signaling the fence.
>
> Fixes: d6a2289d9d6b ("drm/i915: Remove the preempted request from the execution queue")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: <stable@vger.kernel.org> # v4.12+
> ---
> drivers/gpu/drm/i915/intel_breadcrumbs.c | 20 ++++----------------
> 1 file changed, 4 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_breadcrumbs.c b/drivers/gpu/drm/i915/intel_breadcrumbs.c
> index efbc627a2a25..b955f7d7bd0f 100644
> --- a/drivers/gpu/drm/i915/intel_breadcrumbs.c
> +++ b/drivers/gpu/drm/i915/intel_breadcrumbs.c
> @@ -588,29 +588,16 @@ void intel_engine_remove_wait(struct intel_engine_cs *engine,
> spin_unlock_irq(&b->rb_lock);
> }
>
> -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;
>
> - /* If another process served as the bottom-half it may have already
> - * signalled that this wait is already completed.
> - */
> - if (intel_wait_complete(&request->signaling.wait))
> - return signal_valid(request);
Okay so this can return true for unsubmitted requests since rb node will
be empty and global_seqno == wait.seqno == 0.
I just panic when thinking about races and ordering, since these checks
used to run unlocked. So even better that they are gone.
> -
> - /* Carefully check if the request is complete, giving time for the
> + /*
> + * Carefully check if the request is complete, giving time for the
> * seqno to be visible or if the GPU hung.
> */
> - if (__i915_request_irq_complete(request))
> - return true;
> -
> - return false;
> + return __i915_request_irq_complete(request); > }
>
> static struct drm_i915_gem_request *to_signaler(struct rb_node *rb)
> @@ -712,6 +699,7 @@ static int intel_breadcrumbs_signaler(void *arg)
> &request->fence.flags)) {
> local_bh_disable();
> dma_fence_signal(&request->fence);
> + GEM_BUG_ON(!i915_gem_request_completed(request));
> local_bh_enable(); /* kick start the tasklets */
> }
>
>
Looks OK. But I can't say it's straightforward to understand it.
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
next prev parent reply other threads:[~2018-02-07 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 9:46 [PATCH] drm/i915/breadcrumbs: Ignore unsubmitted signalers Chris Wilson
2018-02-06 9:52 ` Chris Wilson
2018-02-06 10:29 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-06 12:12 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-02-06 17:13 ` [PATCH] " Chris Wilson
2018-02-07 10:40 ` Tvrtko Ursulin [this message]
2018-02-07 11:04 ` Chris Wilson
2018-02-07 11:10 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2018-02-13 7:38 patches that failed to cherry-pick on drm-intel-fixes for 4.16-rc1 Rodrigo Vivi
2018-02-13 9:01 ` [PATCH] drm/i915/breadcrumbs: Ignore unsubmitted signalers Chris Wilson
2018-02-14 1:00 ` Rodrigo Vivi
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=ced00ce1-9fd6-89c2-1e39-126d51a8bd49@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=stable@vger.kernel.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