From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: unpin backing storage in dmabuf_unmap
Date: Wed, 07 Aug 2013 12:40:11 +0200 [thread overview]
Message-ID: <5202240B.6070008@canonical.com> (raw)
In-Reply-To: <1375870173-20269-1-git-send-email-daniel.vetter@ffwll.ch>
Op 07-08-13 12:09, Daniel Vetter schreef:
> This fixes a WARN in i915_gem_free_object when the
> obj->pages_pin_count isn't 0.
>
> v2: Add locking to unmap, noticed by Chris Wilson. Note that even
> though we call unmap with our own dev->struct_mutex held that won't
> result in an immediate deadlock since we never go through the dma_buf
> interfaces for our own, reimported buffers. But it's still easy to
> blow up and anger lockdep, but that's already the case with our ->map
> implementation. Fixing this for real will involve per dma-buf ww mutex
> locking by the callers. And lots of fun. So go with the duct-tape
> approach for now.
>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Reported-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@canonical.com>
> Tested-by: Armin K. <krejzi@email.com> (v1)
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
Acked, this was my original patch to solve the issue.
I want to note that locking struct_mutex here will break lockdep, but it's a problem in drm, not this patch.
~Maarten
next prev parent reply other threads:[~2013-08-07 10:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 9:15 [PATCH 0/3] Small i915/exynos prime cleanup Daniel Vetter
2013-08-07 9:15 ` [PATCH 1/3] drm: use common drm_gem_dmabuf_release in i915/exynos drivers Daniel Vetter
2013-08-07 9:37 ` [Intel-gfx] " Chris Wilson
2013-08-07 9:40 ` Inki Dae
2013-08-07 9:55 ` Daniel Vetter
2013-08-07 10:18 ` Joonyoung Shim
2013-08-07 10:21 ` Daniel Vetter
2013-08-07 10:29 ` Joonyoung Shim
2013-08-07 12:01 ` Inki Dae
2013-08-07 12:07 ` Daniel Vetter
2013-08-07 12:37 ` Inki Dae
2013-08-07 23:21 ` Daniel Vetter
2013-08-08 4:32 ` Inki Dae
2013-08-08 4:39 ` [PATCH 1/4] drm/exynos: explicit store base gem object in dma_buf->priv Inki Dae
2013-08-08 4:56 ` Inki Dae
2013-08-08 6:58 ` Daniel Vetter
2013-08-08 6:31 ` [PATCH 1/3] drm: use common drm_gem_dmabuf_release in i915/exynos drivers Daniel Vetter
2013-08-07 9:15 ` [PATCH 2/3] drm/i915: unpin backing storage in dmabuf_unmap Daniel Vetter
2013-08-07 9:19 ` Daniel Vetter
2013-08-07 9:29 ` [Intel-gfx] " Chris Wilson
2013-08-07 9:49 ` Daniel Vetter
2013-08-07 10:09 ` [PATCH 1/2] " Daniel Vetter
2013-08-07 10:09 ` [PATCH 2/2] drm/i915: no interruptible locking for dma_buf->map Daniel Vetter
2013-08-07 10:30 ` Chris Wilson
2013-08-07 10:49 ` Daniel Vetter
2013-08-07 10:40 ` Maarten Lankhorst [this message]
2013-08-08 0:50 ` [PATCH 1/2] drm/i915: unpin backing storage in dmabuf_unmap Konrad Rzeszutek Wilk
2013-08-08 1:20 ` Chris Wilson
2013-08-07 9:15 ` [PATCH 3/3] drm/i915: explicit store base gem object in dma_buf->priv Daniel Vetter
2013-08-07 9:43 ` Chris Wilson
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=5202240B.6070008@canonical.com \
--to=maarten.lankhorst@canonical.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 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.