From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/mst: drop cancel work sync in the mstb destroy path
Date: Wed, 30 Sep 2015 09:20:47 +0200 [thread overview]
Message-ID: <20150930072046.GU3383@phenom.ffwll.local> (raw)
In-Reply-To: <1443573582-19537-1-git-send-email-airlied@gmail.com>
On Wed, Sep 30, 2015 at 10:39:42AM +1000, Dave Airlie wrote:
> From: Dave Airlie <airlied@redhat.com>
>
> Since 9eb1e57f564d4e6e10991402726cc83fe0b9172f
> drm/dp/mst: make sure mst_primary mstb is valid in work function
>
> we validate the mstb structs in the work function, and doing
> that takes a reference. So we should never get here with the
> work function running using the mstb device, only if the work
> function hasn't run yet or is running for another mstb.
>
> So we don't need to sync the work here, this was causing
> lockdep spew when the device failed during the initial EDID
> read.
can you pls paste the lockdep spew here? I think I see the locking
recursion but would like to be sure.
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> ---
> drivers/gpu/drm/drm_dp_mst_topology.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c
> index e23df5f..16f911c 100644
> --- a/drivers/gpu/drm/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/drm_dp_mst_topology.c
> @@ -804,8 +804,6 @@ static void drm_dp_destroy_mst_branch_device(struct kref *kref)
> struct drm_dp_mst_port *port, *tmp;
> bool wake_tx = false;
>
> - cancel_work_sync(&mstb->mgr->work);
> -
Without this there's no place any more where we stop this worker on
teardown. Generally we need to sync with outstanding work at least in
system suspend and on driver unload. I think we need a flush_work (outside
of the locked region ofc!) in drm_dp_mst_topology_mgr_suspend and
drm_dp_mst_topology_mgr_destroy. Might be better as a follow-up patch, but
should imo be part of this.
With lockdep splat + 2x flush_work this is Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
-Daniel
> /*
> * destroy all ports - don't need lock
> * as there are no more references to the mst branch
> --
> 2.4.3
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-09-30 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 0:39 [PATCH] drm/mst: drop cancel work sync in the mstb destroy path Dave Airlie
2015-09-30 7:20 ` Daniel Vetter [this message]
2015-09-30 7:30 ` 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=20150930072046.GU3383@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@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