From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Check waiter->seqno carefully in case of preemption
Date: Tue, 19 Sep 2017 10:28:42 +0100 [thread overview]
Message-ID: <cee37675-4138-94e5-4e89-cdf833bb4414@linux.intel.com> (raw)
In-Reply-To: <20170918162734.21294-2-chris@chris-wilson.co.uk>
On 18/09/2017 17:27, Chris Wilson wrote:
> If preemption occurs at precisely the right moment, we may decide that
> the wait is complete even though the wait's request is no longer
> executing (having been preempted). We handle this situation by double
> checking that request following deciding whether the wait is complete.
>
> Reported-by: Michał Winiarski <michal.winiarski@intel.com
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Michał Winiarski <michal.winiarski@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/i915_irq.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index bb69c5b0efc4..7a53d94b7e61 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -1053,10 +1053,13 @@ static void notify_ring(struct intel_engine_cs *engine)
> */
> if (i915_seqno_passed(intel_engine_get_seqno(engine),
> wait->seqno)) {
> + struct drm_i915_gem_request *waiter = wait->request;
> +
> wakeup = true;
> if (!test_bit(DMA_FENCE_FLAG_SIGNALED_BIT,
> - &wait->request->fence.flags))
> - rq = i915_gem_request_get(wait->request);
> + &waiter->fence.flags) &&
> + intel_wait_check_request(wait, waiter))
> + rq = i915_gem_request_get(waiter);
> }
>
> if (wakeup)
>
Hm but as the user interrupt is nor serialized to exelists, what
prevents the preemption to happen after the intel_wait_check_request and
before dma_fence_signal?
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-09-19 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 16:27 [PATCH 1/2] drm/i915: Only wake the waiter from the interrupt if passed Chris Wilson
2017-09-18 16:27 ` [PATCH 2/2] drm/i915: Check waiter->seqno carefully in case of preemption Chris Wilson
2017-09-19 9:28 ` Tvrtko Ursulin [this message]
2017-09-19 10:07 ` Chris Wilson
2017-09-21 13:45 ` Michał Winiarski
2017-09-18 17:11 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Only wake the waiter from the interrupt if passed Patchwork
2017-09-19 9:00 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-09-19 9:23 ` [PATCH 1/2] " Tvrtko Ursulin
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=cee37675-4138-94e5-4e89-cdf833bb4414@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