From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 07/18] drm/i915: Restore nonblocking awaits for modesetting
Date: Mon, 19 Sep 2016 19:01:38 +0300 [thread overview]
Message-ID: <1474300898.3344.68.camel@linux.intel.com> (raw)
In-Reply-To: <20160914065250.15482-8-chris@chris-wilson.co.uk>
Maarten, could you give this a look?
On ke, 2016-09-14 at 07:52 +0100, Chris Wilson wrote:
> After combining the dma-buf reservation object and the GEM reservation
> object, we lost the ability to do a nonblocking wait on the i915 request
> (as we blocked upon the reservation object during prepare_fb). We can
> instead convert the reservation object into a fence upon which we can
> asynchronously wait (including a forced timeout in case the DMA fence is
> never signaled).
>
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/intel_display.c | 78 ++++++++++++++++++++++--------------
> drivers/gpu/drm/i915/intel_drv.h | 2 +
> 2 files changed, 51 insertions(+), 29 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 5c0ea08dddb3..294df122f7c6 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -14383,12 +14383,33 @@ static void intel_atomic_commit_tail(struct drm_atomic_state *state)
>
> static void intel_atomic_commit_work(struct work_struct *work)
> {
> > - struct drm_atomic_state *state = container_of(work,
> > - struct drm_atomic_state,
> > - commit_work);
> > + struct drm_atomic_state *state =
> > + container_of(work, struct drm_atomic_state, commit_work);
> +
> > intel_atomic_commit_tail(state);
> }
>
> +static int __i915_sw_fence_call
> +intel_atomic_commit_ready(struct i915_sw_fence *fence,
> > + enum i915_sw_fence_notify notify)
> +{
> > + struct intel_atomic_state *state =
> > + container_of(fence, struct intel_atomic_state, commit_ready);
> +
> > + switch (notify) {
> > + case FENCE_COMPLETE:
> > + if (state->base.commit_work.func)
> > + queue_work(system_unbound_wq, &state->base.commit_work);
> > + break;
> +
> > + case FENCE_FREE:
> > + drm_atomic_state_put(&state->base);
> > + break;
> > + }
> +
> > + return NOTIFY_DONE;
> +}
> +
> static void intel_atomic_track_fbs(struct drm_atomic_state *state)
> {
> > struct drm_plane_state *old_plane_state;
> @@ -14434,11 +14455,14 @@ static int intel_atomic_commit(struct drm_device *dev,
> > if (ret)
> > return ret;
>
> > - INIT_WORK(&state->commit_work, intel_atomic_commit_work);
> > + drm_atomic_state_get(state);
> > + i915_sw_fence_init(&intel_state->commit_ready,
> > + intel_atomic_commit_ready);
>
> > ret = intel_atomic_prepare_commit(dev, state);
> > if (ret) {
> > DRM_DEBUG_ATOMIC("Preparing state failed with %i\n", ret);
> > + i915_sw_fence_commit(&intel_state->commit_ready);
> > return ret;
> > }
>
> @@ -14449,10 +14473,14 @@ static int intel_atomic_commit(struct drm_device *dev,
> > intel_atomic_track_fbs(state);
>
> > drm_atomic_state_get(state);
> > - if (nonblock)
> > - queue_work(system_unbound_wq, &state->commit_work);
> > - else
> > + INIT_WORK(&state->commit_work,
> > + nonblock ? intel_atomic_commit_work : NULL);
> +
> > + i915_sw_fence_commit(&intel_state->commit_ready);
> > + if (!nonblock) {
> > + i915_sw_fence_wait(&intel_state->commit_ready);
> > intel_atomic_commit_tail(state);
> > + }
>
> > return 0;
> }
> @@ -14568,8 +14596,7 @@ intel_prepare_plane_fb(struct drm_plane *plane,
> > struct drm_framebuffer *fb = new_state->fb;
> > struct drm_i915_gem_object *obj = intel_fb_obj(fb);
> > struct drm_i915_gem_object *old_obj = intel_fb_obj(plane->state->fb);
> > - long lret;
> > - int ret = 0;
> > + int ret;
>
> > if (!obj && !old_obj)
> > return 0;
> @@ -14577,7 +14604,6 @@ intel_prepare_plane_fb(struct drm_plane *plane,
> > if (old_obj) {
> > struct drm_crtc_state *crtc_state =
> > drm_atomic_get_existing_crtc_state(new_state->state, plane->state->crtc);
> > - long timeout = 0;
>
> > /* Big Hammer, we also need to ensure that any pending
> > * MI_WAIT_FOR_EVENT inside a user batch buffer on the
> @@ -14590,31 +14616,25 @@ intel_prepare_plane_fb(struct drm_plane *plane,
> > * This should only fail upon a hung GPU, in which case we
> > * can safely continue.
> > */
> > - if (needs_modeset(crtc_state))
> > - timeout = i915_gem_object_wait(old_obj,
> > - I915_WAIT_INTERRUPTIBLE |
> > - I915_WAIT_LOCKED,
> > - MAX_SCHEDULE_TIMEOUT,
> > - NULL);
> > - if (timeout < 0) {
> > - /* GPU hangs should have been swallowed by the wait */
> > - WARN_ON(timeout == -EIO);
> > - return timeout;
> > + if (needs_modeset(crtc_state)) {
> > + ret = i915_sw_fence_await_reservation(&to_intel_atomic_state(new_state->state)->commit_ready,
> > + old_obj->resv, NULL,
> > + false, 0,
> > + GFP_KERNEL);
> > + if (ret < 0)
> > + return ret;
> > }
> > }
>
> > if (!obj)
> > return 0;
>
> > - /* For framebuffer backed by dmabuf, wait for fence */
> > - lret = i915_gem_object_wait(obj,
> > - I915_WAIT_INTERRUPTIBLE | I915_WAIT_LOCKED,
> > - MAX_SCHEDULE_TIMEOUT,
> > - NULL);
> > - if (lret == -ERESTARTSYS)
> > - return lret;
> -
> > - WARN(lret < 0, "waiting returns %li\n", lret);
> > + ret = i915_sw_fence_await_reservation(&to_intel_atomic_state(new_state->state)->commit_ready,
> > + obj->resv, NULL,
> > + false, 10*HZ,
> > + GFP_KERNEL);
> > + if (ret < 0)
> > + return ret;
>
> > if (plane->type == DRM_PLANE_TYPE_CURSOR &&
> > INTEL_INFO(dev)->cursor_needs_physical) {
> diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
> index 15e3050edeb9..cb99a2540863 100644
> --- a/drivers/gpu/drm/i915/intel_drv.h
> +++ b/drivers/gpu/drm/i915/intel_drv.h
> @@ -357,6 +357,8 @@ struct intel_atomic_state {
>
> > /* Gen9+ only */
> > struct skl_wm_values wm_results;
> +
> > + struct i915_sw_fence commit_ready;
> };
>
> struct intel_plane_state {
--
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:[~2016-09-19 16:01 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 6:52 Tracking multiple timelines (full-ppgtt) Chris Wilson
2016-09-14 6:52 ` [PATCH 01/18] drm/i915: Support asynchronous waits on struct fence from i915_gem_request Chris Wilson
2016-09-14 7:37 ` Joonas Lahtinen
2016-09-19 11:26 ` Chris Wilson
2016-09-14 6:52 ` [PATCH 02/18] drm/i915: Allow i915_sw_fence_await_sw_fence() to allocate Chris Wilson
2016-09-14 7:51 ` Joonas Lahtinen
2016-09-14 8:46 ` Chris Wilson
2016-09-14 6:52 ` [PATCH 03/18] drm/i915: Rearrange i915_wait_request() accounting with callers Chris Wilson
2016-09-14 8:47 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 04/18] drm/i915: Remove unused i915_gem_active_wait() in favour of _unlocked() Chris Wilson
2016-09-14 8:48 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 05/18] drm/i915: Move GEM activity tracking into a common struct reservation_object Chris Wilson
2016-09-14 9:44 ` Joonas Lahtinen
2016-09-14 17:35 ` Chris Wilson
2016-09-15 9:38 ` Dave Gordon
2016-09-15 9:55 ` Jani Nikula
2016-09-16 11:40 ` Chris Wilson
2016-09-14 6:52 ` [PATCH 06/18] drm: Add reference counting to drm_atomic_state Chris Wilson
2016-09-14 6:52 ` [PATCH 07/18] drm/i915: Restore nonblocking awaits for modesetting Chris Wilson
2016-09-19 16:01 ` Joonas Lahtinen [this message]
2016-09-14 6:52 ` [PATCH 08/18] drm/i915: Combine seqno + tracking into a global timeline struct Chris Wilson
2016-09-14 15:42 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 09/18] drm/i915: Wait first for submission, before waiting for request completion Chris Wilson
2016-09-19 8:59 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 10/18] drm/i915: Introduce a global_seqno for each request Chris Wilson
2016-09-19 10:36 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 11/18] drm/i915: Record space required for request emission Chris Wilson
2016-09-14 13:30 ` Tvrtko Ursulin
2016-09-14 17:33 ` Chris Wilson
2016-09-15 8:59 ` Tvrtko Ursulin
2016-09-19 10:47 ` Joonas Lahtinen
2016-09-19 11:32 ` Chris Wilson
2016-09-19 16:09 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 12/18] drm/i915: Defer " Chris Wilson
2016-09-19 12:06 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 13/18] drm/i915: Move the global sync optimisation to the timeline Chris Wilson
2016-09-19 13:16 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 14/18] drm/i915: Create a unique name for the context Chris Wilson
2016-09-19 13:23 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 15/18] drm/i915: Reserve space in the global seqno during request allocation Chris Wilson
2016-09-19 13:47 ` Joonas Lahtinen
2016-09-19 15:35 ` Jani Nikula
2016-09-19 16:07 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 16/18] drm/i915: Enable multiple timelines Chris Wilson
2016-09-19 15:52 ` Joonas Lahtinen
2016-10-20 12:49 ` Chris Wilson
2016-10-20 15:25 ` Joonas Lahtinen
2016-09-14 6:52 ` [PATCH 17/18] drm/i915: Enable userspace to opt-out of implicit fencing Chris Wilson
2016-09-14 6:52 ` [PATCH 18/18] drm/i915: Support explicit fencing for execbuf Chris Wilson
2016-09-14 9:16 ` ✗ Fi.CI.BAT: failure for series starting with [01/18] drm/i915: Support asynchronous waits on struct fence from i915_gem_request Patchwork
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=1474300898.3344.68.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).