From: Chris Wilson <chris@chris-wilson.co.uk>
To: Laura Abbott <labbott@redhat.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Sean Paul <seanpaul@chromium.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [RFC PATCHv2 0/3] dma_buf import support for vgem
Date: Thu, 27 Apr 2017 08:41:37 +0100 [thread overview]
Message-ID: <20170427074137.GX11432@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1493241150-21742-1-git-send-email-labbott@redhat.com>
On Wed, Apr 26, 2017 at 02:12:27PM -0700, Laura Abbott wrote:
> 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.
Note, that it will be good to cc:intel-gfx@ so that our CI does run it
over the existing vgem tests.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2017-04-27 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 21:12 [RFC PATCHv2 0/3] dma_buf import support for vgem Laura Abbott
2017-04-26 21:12 ` [RFC PATCHv2 1/3] drm/vgem: Add a dummy platform device Laura Abbott
2017-04-26 21:12 ` [RFC PATCHv2 2/3] drm/prime: Introduce drm_gem_prime_import_platform Laura Abbott
2017-05-02 9:19 ` Daniel Vetter
2017-04-26 21:12 ` [RFC PATCHv2 3/3] drm/vgem: Enable dmabuf import interfaces Laura Abbott
2017-04-27 7:31 ` Chris Wilson
2017-04-27 7:41 ` Chris Wilson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170427074137.GX11432@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.org \
--cc=sumit.semwal@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).