Re: [Mesa-dev] [PATCH v2 0/4] gallium/winsys/kms: Fix issues with prime import

2016-08-24 Thread Tomasz Figa
Hi Emil, On Wed, Aug 24, 2016 at 10:41 PM, Emil Velikov wrote: > Hi Tomasz, > > On 2 August 2016 at 11:46, Tomasz Figa wrote: >> Current prime import code in kms-dri Gallium winsys backend has several >> issues: >> - It leaks imported buffers, because of duplicate reference count >>incremen

Re: [Mesa-dev] [PATCH v2 0/4] gallium/winsys/kms: Fix issues with prime import

2016-08-24 Thread Emil Velikov
Hi Tomasz, On 2 August 2016 at 11:46, Tomasz Figa wrote: > Current prime import code in kms-dri Gallium winsys backend has several > issues: > - It leaks imported buffers, because of duplicate reference count >increment at import time. > - It does not check whether an already imported (or l

Re: [Mesa-dev] [PATCH v2 0/4] gallium/winsys/kms: Fix issues with prime import

2016-08-12 Thread Hans de Goede
Hi, On 02-08-16 12:46, Tomasz Figa wrote: Current prime import code in kms-dri Gallium winsys backend has several issues: - It leaks imported buffers, because of duplicate reference count increment at import time. - It does not check whether an already imported (or local) buffer is not b

[Mesa-dev] [PATCH v2 0/4] gallium/winsys/kms: Fix issues with prime import

2016-08-02 Thread Tomasz Figa
Current prime import code in kms-dri Gallium winsys backend has several issues: - It leaks imported buffers, because of duplicate reference count increment at import time. - It does not check whether an already imported (or local) buffer is not being imported, which is problematic because p