All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Julien Boulnois <jboulnois@gmail.com>
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: omapdrm + etnaviv memory leak
Date: Thu, 24 May 2018 10:43:56 +0200	[thread overview]
Message-ID: <1527151436.2779.0.camel@pengutronix.de> (raw)
In-Reply-To: <383e0205-88b9-1ad0-fda4-7792d5c2a03b@ti.com>

Hi Tomi,

Am Donnerstag, den 24.05.2018, 11:39 +0300 schrieb Tomi Valkeinen:
> Hi Lucas,
> 
> On 23/05/18 11:53, Lucas Stach wrote:
> 
> > > With each run, I can see buffers being left lying around, visible
> > > in
> > > both omapdrm's and etnaviv's 'gem' debugfs file. And they're
> > > there
> > > even after killing X.
> > > 
> > > If I try to rmmod etnaviv, I get the warnings below. Unloading
> > > omapdrm is not possible, as it's being referenced by something
> > > (presumably by etnaviv having imported omapdrm's dmabufs).
> > > 
> > > I haven't debugged this much yet, but we do use dmabuf import &
> > > export successfully with omapdrm and v4l2. Has etnaviv dmabuf
> > > import/export been tested?
> > 
> > Yes, dma-buf import/export with etnaviv is extensively being used,
> > as
> > we need to work with imx-drm on the scanout side and a V4L2 driven
> > VPU
> > for video-decode.
> 
> I managed to create a simple test case for this, and I can see the
> leak
> happen without omapdrm too, with etna + vgem combination.
> 
> https://github.com/tomba/kmsxx/blob/etna-debug/utils/buftest.cpp
> 
> With etna_bo_map(), buffers leak.

Thanks, this is really helpful! I'll have a look.

Regards,
Lucas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-05-24  8:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  8:40 omapdrm + etnaviv memory leak Tomi Valkeinen
2018-05-23  8:53 ` Lucas Stach
2018-05-23 12:08   ` Tomi Valkeinen
2018-05-23 14:16     ` Julien Boulnois
2018-05-24  8:39   ` Tomi Valkeinen
2018-05-24  8:43     ` Lucas Stach [this message]
2018-05-24 14:04       ` Lucas Stach

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=1527151436.2779.0.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jboulnois@gmail.com \
    --cc=tomi.valkeinen@ti.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 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.