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

[Emil Velikov]

Hi Tomasz,

On 2 August 2016 at 11:46, Tomasz Figa <tfiga at chromium.org> 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
>    being imported, which is problematic because prime import always
>    returns the same GEM handle for the same buffer and we end up creating
>    duplicate structs referencing the same handle.
>
> This series is an attempt to fix these problems. It originated from
> [PATCH] gallium/sw/kms: Fix multiple imports from PRIME FDs
> (https://patchwork.freedesktop.org/patch/98856/)
> and so they patches inside are considered to be v2.
>
> Tomasz Figa (4):
>   gallium/winsys/kms: Fix double refcount when importing from prime FD (v2)
>   gallium/winsys/kms: Fully initialize kms_sw_dt at prime import time (v2)
>   gallium/winsys/kms: Move display target handle lookup to separate
>     function (v2)
>   gallium/winsys/kms: Look up the GEM handle after importing a prime FD (v2)
>
As you're likely busy with other things so I've taken the liberty of
updating patches 3 and 4 (to match Jordan's suggestion) and pushed the
lot to master.

Thanks for the patches.
Emil