Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030249AbdDZVMv (ORCPT ); Wed, 26 Apr 2017 17:12:51 -0400 Received: from mail-qk0-f182.google.com ([209.85.220.182]:35211 "EHLO mail-qk0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030213AbdDZVMj (ORCPT ); Wed, 26 Apr 2017 17:12:39 -0400 From: Laura Abbott To: Daniel Vetter , Chris Wilson , Sean Paul Cc: Laura Abbott , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Sumit Semwal Subject: [RFC PATCHv2 0/3] dma_buf import support for vgem Date: Wed, 26 Apr 2017 14:12:27 -0700 Message-Id: <1493241150-21742-1-git-send-email-labbott@redhat.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1098 Lines: 33 Hi, This is v2 of my proposal to add dma_buf import functions for vgem. Big changes from v1: - A device is required for dma_buf attach to work. The existing vgem driver intentionally does not use one as it provides a good way to test the DRM framework. This approach instead puts a dummy platform device in the existing drm_device->platformdev field and uses that for attaching. - Native vgem buffers can still be faulted in a page at a time without requiring the entire buffer be resident in memory. I'm still marking this as RFC as I haven't had a chance to finish a userspace test that can be integrated into igt. Feedback appreciated as always. Thanks, Laura Laura Abbott (3): drm/vgem: Add a dummy platform device drm/prime: Introduce drm_gem_prime_import_platform drm/vgem: Enable dmabuf import interfaces drivers/gpu/drm/drm_prime.c | 23 +++++- drivers/gpu/drm/vgem/vgem_drv.c | 150 +++++++++++++++++++++++++++++++--------- drivers/gpu/drm/vgem/vgem_drv.h | 2 + include/drm/drmP.h | 5 ++ 4 files changed, 145 insertions(+), 35 deletions(-) -- 2.7.4