From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 5/5] drm/omapdrm: Switch to gem_free_object_unlocked
Date: Wed, 28 Mar 2018 12:52:13 +0300 [thread overview]
Message-ID: <d1bbbae5-ed5f-fa9d-5a92-a7b717806dca@ti.com> (raw)
In-Reply-To: <20180327082356.24516-5-daniel.vetter@ffwll.ch>
Hi,
On 27/03/18 11:23, Daniel Vetter wrote:
> The only thing that omap_gem_free_object does that might need the
> magic protection of struct_mutex (of keeping all objects alive if that
> lock is held, even if the last reference is gone) is the mm_list
> manipulation.
>
> But that is already protected by the separate omapdrm->list_lock,
> which means struct_mutex is an entirely internal lock for omapdrm.
> Everything else is just releasing resources, which is all protected
> already by the various subsystems and allocators.
>
> To make this even more obvious we could do an
> s/dev->struct_mutex/omapdrm->gem_lock/ like I've done for udl. But
> since omapdrm is a lot bigger and a lot more active I'll refrain from
> that - this is better done by omapdrm developers at some suitable time
> in the future.
>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
> ---
> drivers/gpu/drm/omapdrm/omap_drv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/omapdrm/omap_drv.c b/drivers/gpu/drm/omapdrm/omap_drv.c
> index 3f40f7af3285..6d52877ed25a 100644
> --- a/drivers/gpu/drm/omapdrm/omap_drv.c
> +++ b/drivers/gpu/drm/omapdrm/omap_drv.c
> @@ -490,7 +490,7 @@ static struct drm_driver omap_drm_driver = {
> .prime_fd_to_handle = drm_gem_prime_fd_to_handle,
> .gem_prime_export = omap_gem_prime_export,
> .gem_prime_import = omap_gem_prime_import,
> - .gem_free_object = omap_gem_free_object,
> + .gem_free_object_unlocked = omap_gem_free_object,
> .gem_vm_ops = &omap_gem_vm_ops,
> .dumb_create = omap_gem_dumb_create,
> .dumb_map_offset = omap_gem_dumb_map_offset,
>
This triggers WARN_ON(!mutex_is_locked(&dev->struct_mutex)), we have a
few of those. I need to reverse engineer the omap_gem locking a bit to
understand what's needed. And I need to figure out what exactly does
struct_mutext protect =).
Tomi
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-28 9:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 8:23 [PATCH 1/5] staging/vboxvideo: Use gem_free_object_unlocked Daniel Vetter
2018-03-27 8:23 ` [PATCH 2/5] drm/rockchip: fixup comment for gem_free_object_unlocked Daniel Vetter
2018-03-28 14:02 ` Sean Paul
2018-03-27 8:23 ` [PATCH 3/5] drm/udl: Get rid of dev->struct_mutex usage Daniel Vetter
2018-03-27 16:35 ` Sean Paul
2018-03-27 8:23 ` [PATCH 4/5] drm/omapdrm: Fix mm_list locking Daniel Vetter
2018-03-29 9:40 ` Tomi Valkeinen
2018-03-27 8:23 ` [PATCH 5/5] drm/omapdrm: Switch to gem_free_object_unlocked Daniel Vetter
2018-03-28 9:52 ` Tomi Valkeinen [this message]
2018-03-28 10:12 ` Daniel Vetter
2018-03-28 11:13 ` Tomi Valkeinen
2018-03-28 11:41 ` [PATCH] " Daniel Vetter
2018-03-29 9:41 ` Tomi Valkeinen
2018-04-02 15:05 ` Laurent Pinchart
2018-04-03 9:07 ` Daniel Vetter
2018-04-03 11:23 ` Laurent Pinchart
2018-03-27 8:34 ` [PATCH 1/5] staging/vboxvideo: Use gem_free_object_unlocked Greg Kroah-Hartman
2018-03-27 9:18 ` Daniel Vetter
2018-03-27 15:25 ` Greg Kroah-Hartman
2018-03-28 15:07 ` 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=d1bbbae5-ed5f-fa9d-5a92-a7b717806dca@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
/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