freedreno: add fd_device_new_dup()

There seem to be some cases (I've noticed this switching resolution in
some games, for example) where the fd can get closed() before the device
and all it's bo's are destroyed.  Which, if the drm device is opened
again and bo's are allocated with the same handles, results that when
the first pipe_screen/pipe_context is destroyed causes the first dev to
close handles for bo's allocated by the second device.

The easy solution to that is to add a mode where the fd_device creates
it's own private fd (a dup()).

Signed-off-by: Rob Clark <robclark@freedesktop.org>

1 files changed, 12 insertions, 0 deletions

diff --git a/freedreno/freedreno_device.c b/freedreno/freedreno_device.c
index 6486983d..23e086bb 100644
--- a/freedreno/freedreno_device.c
+++ b/freedreno/freedreno_device.c
@@ -135,6 +135,16 @@ struct fd_device * fd_device_new(int fd)
         return dev;
 }
 
+/* like fd_device_new() but creates it's own private dup() of the fd
+ * which is close()d when the device is finalized.
+ */
+struct fd_device * fd_device_new_dup(int fd)
+{
+        struct fd_device *dev = fd_device_new(dup(fd));
+        dev->closefd = 1;
+        return dev;
+}
+
 struct fd_device * fd_device_ref(struct fd_device *dev)
 {
         atomic_inc(&dev->refcnt);
@@ -147,6 +157,8 @@ static void fd_device_del_impl(struct fd_device *dev)
         drmHashDestroy(dev->handle_table);
         drmHashDestroy(dev->name_table);
         drmHashDelete(dev_table, dev->fd);
+        if (dev->closefd)
+                close(dev->fd);
         dev->funcs->destroy(dev);
 }