From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 8/8] drm: Nuke drm_atomic_legacy_backoff
Date: Tue, 25 Jul 2017 11:36:14 +0200 [thread overview]
Message-ID: <58bfe6b4-0a45-1034-4670-1d87660a225a@linux.intel.com> (raw)
In-Reply-To: <20170725080122.20548-9-daniel.vetter@ffwll.ch>
Op 25-07-17 om 10:01 schreef Daniel Vetter:
> Finally all users are gone!
>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
> drivers/gpu/drm/drm_atomic.c | 32 --------------------------------
> include/drm/drm_atomic.h | 2 --
> 2 files changed, 34 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c
> index 306fdca92abf..1b755439f591 100644
> --- a/drivers/gpu/drm/drm_atomic.c
> +++ b/drivers/gpu/drm/drm_atomic.c
> @@ -1588,38 +1588,6 @@ drm_atomic_add_affected_planes(struct drm_atomic_state *state,
> EXPORT_SYMBOL(drm_atomic_add_affected_planes);
>
> /**
> - * drm_atomic_legacy_backoff - locking backoff for legacy ioctls
> - * @state: atomic state
> - *
> - * This function should be used by legacy entry points which don't understand
> - * -EDEADLK semantics. For simplicity this one will grab all modeset locks after
> - * the slowpath completed.
> - */
> -void drm_atomic_legacy_backoff(struct drm_atomic_state *state)
> -{
> - struct drm_device *dev = state->dev;
> - int ret;
> - bool global = false;
> -
> - if (WARN_ON(dev->mode_config.acquire_ctx == state->acquire_ctx)) {
> - global = true;
> -
> - dev->mode_config.acquire_ctx = NULL;
> - }
> -
> -retry:
> - drm_modeset_backoff(state->acquire_ctx);
> -
> - ret = drm_modeset_lock_all_ctx(dev, state->acquire_ctx);
> - if (ret)
> - goto retry;
> -
> - if (global)
> - dev->mode_config.acquire_ctx = state->acquire_ctx;
> -}
> -EXPORT_SYMBOL(drm_atomic_legacy_backoff);
You're missing one patch here. We should also mark dev->mode_config.acquire_ctx __private. That way atomic commits will never be able to use lock_all. :)
Though I think it requires fixing vmwgfx_fb.c and i915 first.
Otherwise series looks good, so with review comments addressed.
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-07-25 9:36 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 8:01 [PATCH 0/8] acquire ctx for everyone! Daniel Vetter
2017-07-25 8:01 ` [PATCH 1/8] drm/omap: Simplify the rotation-on-crtc hack Daniel Vetter
2017-07-25 8:47 ` Maarten Lankhorst
2017-07-25 9:24 ` [Intel-gfx] " Daniel Vetter
2017-07-31 11:48 ` Laurent Pinchart
2017-07-31 11:56 ` Tomi Valkeinen
2017-07-31 10:54 ` [PATCH] drm/omap: Rework " Daniel Vetter
2017-07-31 11:57 ` Laurent Pinchart
2017-07-31 12:45 ` Daniel Vetter
2017-07-31 13:30 ` Laurent Pinchart
2017-07-31 15:42 ` Daniel Vetter
2017-08-01 5:59 ` Maarten Lankhorst
2017-08-01 10:20 ` Laurent Pinchart
2017-08-02 8:02 ` Daniel Vetter
2017-08-02 13:20 ` Maarten Lankhorst
2017-08-04 9:57 ` Tomi Valkeinen
2017-08-04 10:02 ` Daniel Vetter
2017-08-07 9:24 ` Maarten Lankhorst
2017-08-07 9:56 ` Maarten Lankhorst
2017-08-07 10:20 ` [PATCH v7] " Maarten Lankhorst
2017-08-08 12:08 ` Tomi Valkeinen
2017-07-25 8:01 ` [PATCH 2/8] drm: Don't update property values for atomic drivers Daniel Vetter
2017-07-25 8:32 ` Maarten Lankhorst
2017-07-25 12:01 ` [PATCH] " Daniel Vetter
2017-08-11 22:20 ` [PATCH 2/8] " Laurent Pinchart
2017-08-14 7:25 ` Daniel Vetter
2017-08-14 10:32 ` Laurent Pinchart
2017-08-14 14:09 ` Daniel Vetter
2017-07-25 8:01 ` [PATCH 3/8] drm: Handle properties in the core " Daniel Vetter
2017-07-25 9:36 ` Archit Taneja
2017-07-25 12:02 ` [PATCH] " Daniel Vetter
2017-07-25 8:01 ` [PATCH 4/8] drm: Nuke drm_atomic_helper_crtc_set_property Daniel Vetter
2017-07-25 9:38 ` Archit Taneja
2017-07-25 10:05 ` Philippe CORNU
2017-08-03 13:34 ` Thomas Hellstrom
2017-07-25 8:01 ` [PATCH 5/8] drm: Nuke drm_atomic_helper_plane_set_property Daniel Vetter
2017-07-25 9:38 ` Archit Taneja
2017-07-25 10:06 ` Philippe CORNU
2017-07-28 16:45 ` Liviu Dudau
2017-08-08 10:03 ` Vincent ABRIOU
2017-08-08 12:31 ` Laurent Pinchart
[not found] ` <20170725080122.20548-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2017-07-25 8:01 ` [PATCH 6/8] drm: Nuke drm_atomic_helper_connector_set_property Daniel Vetter
[not found] ` <20170725080122.20548-7-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2017-07-25 9:23 ` [Intel-gfx] " Maarten Lankhorst
2017-07-25 9:26 ` Daniel Vetter
2017-08-08 10:04 ` Vincent ABRIOU
2017-07-25 8:01 ` [PATCH 7/8] drm: Nuke drm_atomic_helper_connector_dpms Daniel Vetter
2017-07-25 8:04 ` Neil Armstrong
2017-07-25 8:59 ` Philipp Zabel
2017-07-25 9:30 ` Archit Taneja
2017-07-25 10:07 ` Philippe CORNU
2017-07-25 14:01 ` Laurent Pinchart
2017-07-25 14:42 ` Shawn Guo
2017-07-26 19:00 ` Noralf Trønnes
2017-08-08 10:05 ` Vincent ABRIOU
2017-07-25 8:01 ` [PATCH 8/8] drm: Nuke drm_atomic_legacy_backoff Daniel Vetter
2017-07-25 9:36 ` Maarten Lankhorst [this message]
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=58bfe6b4-0a45-1034-4670-1d87660a225a@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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