All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/atomic: Call ww_acquire_done after check phase is complete
Date: Wed, 5 Aug 2015 16:57:24 +0200	[thread overview]
Message-ID: <55C22454.3090304@linux.intel.com> (raw)
In-Reply-To: <1438780119-30493-1-git-send-email-daniel.vetter@ffwll.ch>

Hey,

Op 05-08-15 om 15:08 schreef Daniel Vetter:
> We want to make sure that no one tries to acquire more locks and
> states, and ww mutexes provide debug facilities for that. So use them.
>
> Cc: Rob Clark <robdclark@gmail.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
>  drivers/gpu/drm/drm_atomic.c | 2 ++
>  1 file changed, 2 insertions(+)
I like the idea, played with the thought myself, but I think it might need to be slightly less strict for transitional drivers.

~Maarten
> diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c
> index 422183e7ee7d..5ea609f270ea 100644
> --- a/drivers/gpu/drm/drm_atomic.c
> +++ b/drivers/gpu/drm/drm_atomic.c
> @@ -1268,6 +1268,8 @@ int drm_atomic_check_only(struct drm_atomic_state *state)
>  		}
>  	}
>  
> +	ww_acquire_done(&state->acquire_ctx->ww_ctx);
> +
>  	return ret;
>  }
>  EXPORT_SYMBOL(drm_atomic_check_only);

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-08-05 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 13:08 [PATCH] drm/atomic: Call ww_acquire_done after check phase is complete Daniel Vetter
2015-08-05 14:57 ` Maarten Lankhorst [this message]
2015-08-05 15:03   ` Daniel Vetter
2015-08-05 18:13     ` Maarten Lankhorst
2015-08-05 22:25       ` Daniel Vetter
2015-08-06  4:17         ` Maarten Lankhorst
2015-08-06 13:07           ` Daniel Vetter
2015-08-12  1:47 ` shuang.he
  -- strict thread matches above, loose matches on Subject: below --
2015-08-06 13:06 Daniel Vetter
2015-08-10 12:11 ` Daniel Vetter

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=55C22454.3090304@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.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 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.