From: Harry Wentland <harry.wentland@amd.com>
To: dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 13/19] drm: simplify the locking in the GETCRTC ioctl
Date: Mon, 27 Mar 2017 20:13:17 -0400 [thread overview]
Message-ID: <3437695.pIRnbztWNA@hwentlanhp> (raw)
In-Reply-To: <20170322215058.8671-14-daniel.vetter@ffwll.ch>
On Wednesday, March 22, 2017 10:50:52 PM EDT Daniel Vetter wrote:
> No need to grab both plane and crtc locks at the same time, we can do
> them one after the other. If userspace races it'll get what it
> deserves either way.
>
> This removes another user of drm_modeset_lock_crtc. There's only one
> left.
>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> drivers/gpu/drm/drm_crtc.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> index 660b4c8715de..df1ff0b8818b 100644
> --- a/drivers/gpu/drm/drm_crtc.c
> +++ b/drivers/gpu/drm/drm_crtc.c
> @@ -406,16 +406,18 @@ int drm_mode_getcrtc(struct drm_device *dev,
> if (!crtc)
> return -ENOENT;
>
> - drm_modeset_lock_crtc(crtc, crtc->primary);
> crtc_resp->gamma_size = crtc->gamma_size;
>
> + drm_modeset_lock(&crtc->primary->mutex, NULL);
> if (crtc->primary->state && crtc->primary->state->fb)
> crtc_resp->fb_id = crtc->primary->state->fb->base.id;
> else if (!crtc->primary->state && crtc->primary->fb)
> crtc_resp->fb_id = crtc->primary->fb->base.id;
> else
> crtc_resp->fb_id = 0;
> + drm_modeset_unlock(&crtc->primary->mutex);
>
> + drm_modeset_lock(&crtc->mutex, NULL);
> if (crtc->state) {
> crtc_resp->x = crtc->primary->state->src_x >> 16;
> crtc_resp->y = crtc->primary->state->src_y >> 16;
What about crtc->primary here? Shouldn't that also be locked with the crtc-
>primary->mutex or do we treat state differently? Still not 100% on the exact
locking semantics.
Harry
> @@ -437,7 +439,7 @@ int drm_mode_getcrtc(struct drm_device *dev,
> crtc_resp->mode_valid = 0;
> }
> }
> - drm_modeset_unlock_crtc(crtc);
> + drm_modeset_unlock(&crtc->mutex);
>
> return 0;
> }
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-28 0:13 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 21:50 [PATCH 00/19] wire acquire ctx through legacy modeset paths Daniel Vetter
2017-03-22 21:50 ` [PATCH 01/19] drm: Wire up proper acquire ctx for plane functions Daniel Vetter
2017-03-27 20:12 ` Harry Wentland
2017-03-28 6:23 ` Daniel Vetter
2017-03-28 6:46 ` Daniel Vetter
2017-03-28 7:02 ` Daniel Vetter
2017-03-28 14:48 ` Harry Wentland
2017-03-22 21:50 ` [PATCH 02/19] drm: Add acquire ctx parameter to ->update_plane Daniel Vetter
2017-03-22 23:03 ` Russell King - ARM Linux
2017-03-24 7:07 ` Daniel Vetter
2017-03-22 21:50 ` [PATCH 03/19] drm: drm_plane_force_disable is not for atomic drivers Daniel Vetter
2017-03-22 21:50 ` [PATCH 04/19] drm: Add acquire ctx parameter to ->plane_disable Daniel Vetter
2017-03-22 21:50 ` [PATCH 05/19] drm/atomic-helper: remove backoff hack from disable/update_plane Daniel Vetter
2017-03-22 21:50 ` [PATCH 06/19] drm/vmwgfx: Drop the cursor locking hack Daniel Vetter
2017-03-23 6:22 ` Thomas Hellstrom
2017-03-23 7:28 ` Daniel Vetter
2017-03-23 7:31 ` Daniel Vetter
2017-03-23 8:35 ` Thomas Hellstrom
2017-03-23 10:10 ` Daniel Vetter
2017-03-23 10:32 ` Thomas Hellstrom
2017-03-23 12:56 ` Daniel Vetter
2017-03-27 3:01 ` Michel Dänzer
2017-03-27 6:28 ` Daniel Vetter
2017-03-27 8:31 ` Thomas Hellstrom
2017-03-29 8:00 ` Daniel Vetter
2017-03-29 8:04 ` Thomas Hellstrom
2017-03-22 21:50 ` [PATCH 07/19] drm/tegra: Don't use modeset_lock_crtc Daniel Vetter
2017-03-27 15:50 ` Daniel Vetter
2017-03-22 21:50 ` [PATCH 08/19] drm/tilcdc: Drop calls to modeset_lock_crtc Daniel Vetter
2017-03-24 9:46 ` Tomi Valkeinen
2017-03-25 21:19 ` Daniel Vetter
2017-03-24 13:34 ` Jyri Sarha
2017-03-22 21:50 ` [PATCH 09/19] drm: Make drm_modeset_lock_crtc internal Daniel Vetter
2017-03-22 21:50 ` [PATCH 10/19] drm: Roll out acquire context for the page_flip ioctl Daniel Vetter
2017-03-22 21:50 ` [PATCH 11/19] drm: Add acquire ctx parameter to ->page_flip(_target) Daniel Vetter
2017-03-22 21:50 ` [PATCH 12/19] drm/atomic-helper: remove backoff hack from page_flip Daniel Vetter
2017-03-22 21:50 ` [PATCH 13/19] drm: simplify the locking in the GETCRTC ioctl Daniel Vetter
2017-03-28 0:13 ` Harry Wentland [this message]
2017-03-28 6:27 ` Daniel Vetter
2017-03-28 7:01 ` [PATCH] " Daniel Vetter
2017-03-28 14:41 ` Harry Wentland
2017-03-30 7:36 ` [PATCH] Revert unrelated part of "drm: simplify the locking in the GETCRTC ioctl" Maarten Lankhorst
2017-03-30 7:48 ` Pandiyan, Dhinakaran
2017-03-30 7:56 ` [Intel-gfx] " Daniel Vetter
2017-03-22 21:50 ` [PATCH 14/19] drm: Remove drm_modeset_(un)lock_crtc Daniel Vetter
2017-03-22 21:50 ` [PATCH 15/19] drm: Remove drm_modeset_legacy_acquire_ctx and crtc->acquire_ctx Daniel Vetter
2017-03-22 21:50 ` [PATCH 16/19] drm: Restrict drm_mode_set_config_internal to non-atomic drivers Daniel Vetter
2017-03-22 21:50 ` [PATCH 17/19] drm: Add explicit acquire ctx handling around ->set_config Daniel Vetter
2017-03-22 21:50 ` [PATCH 18/19] drm: Add acquire ctx parameter to ->set_config Daniel Vetter
2017-04-04 0:06 ` Sinclair Yeh
2017-03-22 21:50 ` [PATCH 19/19] drm/atomic-helper: Remove the backoff hack from set_config Daniel Vetter
2017-03-23 9:37 ` ✗ Fi.CI.BAT: warning for wire acquire ctx through legacy modeset paths Patchwork
2017-03-28 0:31 ` [PATCH 00/19] " Harry Wentland
2017-03-28 7:20 ` ✓ Fi.CI.BAT: success for wire acquire ctx through legacy modeset paths (rev2) 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=3437695.pIRnbztWNA@hwentlanhp \
--to=harry.wentland@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--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