Re: omapdrm + etnaviv memory leak

2018-05-24 Thread Lucas Stach
Am Donnerstag, den 24.05.2018, 10:43 +0200 schrieb Lucas Stach: > 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 > >

Re: omapdrm + etnaviv memory leak

2018-05-24 Thread Julien Boulnois
Hi Lucas, 2018-05-23 14:08 GMT+02:00 Tomi Valkeinen : > On 23/05/18 11:53, Lucas Stach wrote: > > Hi Tomi, > > > > Am Mittwoch, den 23.05.2018, 11:40 +0300 schrieb Tomi Valkeinen: > >> Hi Lucas, > >> > >> Julien has written an X driver for OMAP5 SoC (which has Vivante's > >> GC320). We're seeing

Re: omapdrm + etnaviv memory leak

2018-05-24 Thread Lucas Stach
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 > >

Re: omapdrm + etnaviv memory leak

2018-05-24 Thread 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

Re: omapdrm + etnaviv memory leak

2018-05-23 Thread Tomi Valkeinen
On 23/05/18 11:53, Lucas Stach wrote: > Hi Tomi, > > Am Mittwoch, den 23.05.2018, 11:40 +0300 schrieb Tomi Valkeinen: >> Hi Lucas, >> >> Julien has written an X driver for OMAP5 SoC (which has Vivante's >> GC320). We're seeing a memory leak when using omapdrm for display and >> etnaviv for X 2D re

Re: omapdrm + etnaviv memory leak

2018-05-23 Thread Lucas Stach
Hi Tomi, Am Mittwoch, den 23.05.2018, 11:40 +0300 schrieb Tomi Valkeinen: > Hi Lucas, > > Julien has written an X driver for OMAP5 SoC (which has Vivante's > GC320). We're seeing a memory leak when using omapdrm for display and > etnaviv for X 2D rendering. The X driver uses DRI3, so dmabuf > imp

omapdrm + etnaviv memory leak

2018-05-23 Thread Tomi Valkeinen
Hi Lucas, Julien has written an X driver for OMAP5 SoC (which has Vivante's GC320). We're seeing a memory leak when using omapdrm for display and etnaviv for X 2D rendering. The X driver uses DRI3, so dmabuf import/export is involved. I've written a simple DRI3 tester, which supports using diff