From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Stop kicking the signaling thread on seqno wraparound
Date: Tue, 06 Mar 2018 17:04:38 +0200 [thread overview]
Message-ID: <1520348678.3569.2.camel@linux.intel.com> (raw)
In-Reply-To: <20180306130143.13312-1-chris@chris-wilson.co.uk>
On Tue, 2018-03-06 at 13:01 +0000, Chris Wilson wrote:
> Since commit fd10e2ce9905 ("drm/i915/breadcrumbs: Ignore unsubmitted
> signalers"), we cancel the signaler when retiring the request and so
> upon wraparound, where we wait for all requests to be retired, we no
> longer need to spin waiting for the signaling thread to release its
> references to the in-flight requests, and so we can assert that the
> signaler is idle.
>
> References: fd10e2ce9905 ("drm/i915/breadcrumbs: Ignore unsubmitted signalers")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-06 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 13:01 [PATCH 1/2] drm/i915: Stop kicking the signaling thread on seqno wraparound Chris Wilson
2018-03-06 13:01 ` [PATCH 2/2] drm/i915: Flush waiters " Chris Wilson
2018-03-06 15:05 ` Joonas Lahtinen
2018-03-06 13:59 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Stop kicking the signaling thread " Patchwork
2018-03-06 15:04 ` Joonas Lahtinen [this message]
2018-03-06 18:53 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-03-06 19:11 ` 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=1520348678.3569.2.camel@linux.intel.com \
--to=joonas.lahtinen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.