linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomeu Vizoso <tomeu.vizoso@collabora.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
	dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	Shuah Khan <shuah@kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:DMA BUFFER SHARING FRAMEWORK" 
	<linux-media@vger.kernel.org>,
	"moderated list:DMA BUFFER SHARING FRAMEWORK" 
	<linaro-mm-sig@lists.linaro.org>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	Zach Reizner <zachr@google.com>,
	Daniel Stone <daniels@collabora.com>
Subject: Re: [PATCH v6] Add udmabuf misc device
Date: Wed, 4 Jul 2018 09:26:39 +0200	[thread overview]
Message-ID: <9818b301-9c9d-c703-d4fe-7c2d4d43ed66@collabora.com> (raw)
In-Reply-To: <20180704055338.n3b7oexltaejqmcd@sirius.home.kraxel.org>

On 07/04/2018 07:53 AM, Gerd Hoffmann wrote:
> On Tue, Jul 03, 2018 at 10:37:57AM +0200, Daniel Vetter wrote:
>> On Tue, Jul 03, 2018 at 09:53:58AM +0200, Gerd Hoffmann wrote:
>>> A driver to let userspace turn memfd regions into dma-bufs.
>>>
>>> Use case:  Allows qemu create dmabufs for the vga framebuffer or
>>> virtio-gpu ressources.  Then they can be passed around to display
>>> those guest things on the host.  To spice client for classic full
>>> framebuffer display, and hopefully some day to wayland server for
>>> seamless guest window display.
>>>
>>> qemu test branch:
>>>    https://git.kraxel.org/cgit/qemu/log/?h=sirius/udmabuf
>>>
>>> Cc: David Airlie <airlied@linux.ie>
>>> Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>
>>> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>>> Cc: Daniel Vetter <daniel@ffwll.ch>
>>> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>>
>> I think some ack for a 2nd use-case, like virtio-wl or whatever would be
>> really cool. To give us some assurance that this is generically useful.
> 
> Tomeu?  Laurent?

Sorry, but I think I will need some help to understand how this could 
help in the virtio-wl case [adding Zach Reizner to CC].

Any graphics buffers that are allocated with memfd will be shared with 
the compositor via wl_shm, without need for dmabufs.

Daniel Stone [added to CC] commented though that this could be useful for 
browsers that composite pages with a nested Wayland compositor, to avoid 
having to blit each layer so that the EGL platform notifies the 
compositor of new contents.

Cheers,

Tomeu

>> Plus an ack from dma-buf folks (nag them on irc, you don't have them on Cc
>> here).
> 
> Hmm, does MAINTAINERS need an update then?  Maintainer and mailing lists
> listed in the "DMA BUFFER SHARING FRAMEWORK" entry are on Cc.
> 
> Who should be Cc'ed?
> 
>> Then this is imo good to go.
>>
>> I assume you'll push it to drm-misc, like all the other dma-buf stuff?
> 
> Can do that, sure, after collecting the acks ...
> 
> thanks,
>    Gerd
> 

  reply	other threads:[~2018-07-04  7:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03  7:53 [PATCH v6] Add udmabuf misc device Gerd Hoffmann
2018-07-03  8:37 ` Daniel Vetter
2018-07-04  5:53   ` Gerd Hoffmann
2018-07-04  7:26     ` Tomeu Vizoso [this message]
2018-07-04  8:00       ` Gerd Hoffmann
2018-07-06  4:00         ` Dave Airlie
2018-08-30 15:17         ` Tomeu Vizoso
2018-08-31  7:04           ` Gerd Hoffmann
2018-07-04  8:08     ` Daniel Vetter
2018-07-04  8:58       ` Gerd Hoffmann
2018-07-04  9:19         ` Daniel Vetter
2018-08-27  9:34           ` Gerd Hoffmann

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=9818b301-9c9d-c703-d4fe-7c2d4d43ed66@collabora.com \
    --to=tomeu.vizoso@collabora.com \
    --cc=airlied@linux.ie \
    --cc=corbet@lwn.net \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kraxel@redhat.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=sumit.semwal@linaro.org \
    --cc=zachr@google.com \
    /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).