All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: 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: Fri, 31 Aug 2018 09:04:24 +0200	[thread overview]
Message-ID: <20180831070424.3xoxfy54vyxbdfzd@sirius.home.kraxel.org> (raw)
In-Reply-To: <06d8aa8d-5eac-64e2-f21e-43fe7ca96cc2@collabora.com>

  Hi,

> > qemu can use memfd to allocate guest ram.  Now, with the help of
> > udmabuf, qemu can create a *host* dma-buf for the *guest* graphics
> > buffer.
> 
> Guess each physical address in the iovec in
> VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING can be passed as the offset in the
> udmabuf_create_item struct?

Exactly.

https://git.kraxel.org/cgit/qemu/commit/?h=sirius/udmabuf&id=515a5b9f1215ea668a992e39d66993a17a940801

> Are you thinking of anything else besides passing the winsrv protocol across
> the guest/host boundary? Just wondering if I'm missing something.

The patch above uses the dmabuf internally in qemu.  It simply mmaps it,
so qemu has a linear representation of the resource and can use it as
pixman image backing storage without copying the pixel data.

So it is useful even without actually exporting the dmabuf to other
processes.

cheers,
  Gerd

PS: Any chance you can review the v7 patch?

WARNING: multiple messages have this Message-ID (diff)
From: kraxel at redhat.com (Gerd Hoffmann)
Subject: [PATCH v6] Add udmabuf misc device
Date: Fri, 31 Aug 2018 09:04:24 +0200	[thread overview]
Message-ID: <20180831070424.3xoxfy54vyxbdfzd@sirius.home.kraxel.org> (raw)
In-Reply-To: <06d8aa8d-5eac-64e2-f21e-43fe7ca96cc2@collabora.com>

  Hi,

> > qemu can use memfd to allocate guest ram.  Now, with the help of
> > udmabuf, qemu can create a *host* dma-buf for the *guest* graphics
> > buffer.
> 
> Guess each physical address in the iovec in
> VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING can be passed as the offset in the
> udmabuf_create_item struct?

Exactly.

https://git.kraxel.org/cgit/qemu/commit/?h=sirius/udmabuf&id=515a5b9f1215ea668a992e39d66993a17a940801

> Are you thinking of anything else besides passing the winsrv protocol across
> the guest/host boundary? Just wondering if I'm missing something.

The patch above uses the dmabuf internally in qemu.  It simply mmaps it,
so qemu has a linear representation of the resource and can use it as
pixman image backing storage without copying the pixel data.

So it is useful even without actually exporting the dmabuf to other
processes.

cheers,
  Gerd

PS: Any chance you can review the v7 patch?

WARNING: multiple messages have this Message-ID (diff)
From: kraxel@redhat.com (Gerd Hoffmann)
Subject: [PATCH v6] Add udmabuf misc device
Date: Fri, 31 Aug 2018 09:04:24 +0200	[thread overview]
Message-ID: <20180831070424.3xoxfy54vyxbdfzd@sirius.home.kraxel.org> (raw)
Message-ID: <20180831070424.6zaMDnaqmbWWu66pxlfexh7GZC9fNGJqt2lnQx79e1I@z> (raw)
In-Reply-To: <06d8aa8d-5eac-64e2-f21e-43fe7ca96cc2@collabora.com>

  Hi,

> > qemu can use memfd to allocate guest ram.  Now, with the help of
> > udmabuf, qemu can create a *host* dma-buf for the *guest* graphics
> > buffer.
> 
> Guess each physical address in the iovec in
> VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING can be passed as the offset in the
> udmabuf_create_item struct?

Exactly.

https://git.kraxel.org/cgit/qemu/commit/?h=sirius/udmabuf&id=515a5b9f1215ea668a992e39d66993a17a940801

> Are you thinking of anything else besides passing the winsrv protocol across
> the guest/host boundary? Just wondering if I'm missing something.

The patch above uses the dmabuf internally in qemu.  It simply mmaps it,
so qemu has a linear representation of the resource and can use it as
pixman image backing storage without copying the pixel data.

So it is useful even without actually exporting the dmabuf to other
processes.

cheers,
  Gerd

PS: Any chance you can review the v7 patch?

WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: Daniel Stone <daniels@collabora.com>,
	Jonathan Corbet <corbet@lwn.net>, David Airlie <airlied@linux.ie>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org,
	"moderated list:DMA BUFFER SHARING FRAMEWORK"
	<linaro-mm-sig@lists.linaro.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	"open list:KERNEL SELFTEST FRAMEWORK"
	<linux-kselftest@vger.kernel.org>, Shuah Khan <shuah@kernel.org>,
	"open list:DMA BUFFER SHARING FRAMEWORK"
	<linux-media@vger.kernel.org>
Subject: Re: [PATCH v6] Add udmabuf misc device
Date: Fri, 31 Aug 2018 09:04:24 +0200	[thread overview]
Message-ID: <20180831070424.3xoxfy54vyxbdfzd@sirius.home.kraxel.org> (raw)
In-Reply-To: <06d8aa8d-5eac-64e2-f21e-43fe7ca96cc2@collabora.com>

  Hi,

> > qemu can use memfd to allocate guest ram.  Now, with the help of
> > udmabuf, qemu can create a *host* dma-buf for the *guest* graphics
> > buffer.
> 
> Guess each physical address in the iovec in
> VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING can be passed as the offset in the
> udmabuf_create_item struct?

Exactly.

https://git.kraxel.org/cgit/qemu/commit/?h=sirius/udmabuf&id=515a5b9f1215ea668a992e39d66993a17a940801

> Are you thinking of anything else besides passing the winsrv protocol across
> the guest/host boundary? Just wondering if I'm missing something.

The patch above uses the dmabuf internally in qemu.  It simply mmaps it,
so qemu has a linear representation of the resource and can use it as
pixman image backing storage without copying the pixel data.

So it is useful even without actually exporting the dmabuf to other
processes.

cheers,
  Gerd

PS: Any chance you can review the v7 patch?
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-08-31  7:04 UTC|newest]

Thread overview: 66+ 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  7:53 ` Gerd Hoffmann
2018-07-03  7:53 ` Gerd Hoffmann
2018-07-03  7:53 ` kraxel
2018-07-03  7:53 ` Gerd Hoffmann
2018-07-03  8:37 ` Daniel Vetter
2018-07-03  8:37   ` Daniel Vetter
2018-07-03  8:37   ` Daniel Vetter
2018-07-03  8:37   ` daniel
2018-07-03  8:37   ` Daniel Vetter
2018-07-03  8:37   ` Daniel Vetter
2018-07-04  5:53   ` Gerd Hoffmann
2018-07-04  5:53     ` Gerd Hoffmann
2018-07-04  5:53     ` Gerd Hoffmann
2018-07-04  5:53     ` kraxel
2018-07-04  5:53     ` Gerd Hoffmann
2018-07-04  5:53     ` Gerd Hoffmann
2018-07-04  7:26     ` Tomeu Vizoso
2018-07-04  7:26       ` Tomeu Vizoso
2018-07-04  7:26       ` Tomeu Vizoso
2018-07-04  7:26       ` tomeu.vizoso
2018-07-04  7:26       ` Tomeu Vizoso
2018-07-04  7:26       ` Tomeu Vizoso
2018-07-04  8:00       ` Gerd Hoffmann
2018-07-04  8:00         ` Gerd Hoffmann
2018-07-04  8:00         ` Gerd Hoffmann
2018-07-04  8:00         ` kraxel
2018-07-04  8:00         ` Gerd Hoffmann
2018-07-04  8:00         ` Gerd Hoffmann
2018-07-06  4:00         ` Dave Airlie
2018-07-06  4:00           ` Dave Airlie
2018-07-06  4:00           ` Dave Airlie
2018-07-06  4:00           ` airlied
2018-07-06  4:00           ` Dave Airlie
2018-07-06  4:00           ` Dave Airlie
2018-08-30 15:17         ` Tomeu Vizoso
2018-08-30 15:17           ` Tomeu Vizoso
2018-08-30 15:17           ` tomeu.vizoso
2018-08-30 15:17           ` Tomeu Vizoso
2018-08-31  7:04           ` Gerd Hoffmann [this message]
2018-08-31  7:04             ` Gerd Hoffmann
2018-08-31  7:04             ` Gerd Hoffmann
2018-08-31  7:04             ` kraxel
2018-08-31  7:04             ` Gerd Hoffmann
2018-07-04  8:08     ` Daniel Vetter
2018-07-04  8:08       ` Daniel Vetter
2018-07-04  8:08       ` Daniel Vetter
2018-07-04  8:08       ` daniel
2018-07-04  8:08       ` Daniel Vetter
2018-07-04  8:08       ` Daniel Vetter
2018-07-04  8:58       ` Gerd Hoffmann
2018-07-04  8:58         ` Gerd Hoffmann
2018-07-04  8:58         ` Gerd Hoffmann
2018-07-04  8:58         ` kraxel
2018-07-04  8:58         ` Gerd Hoffmann
2018-07-04  8:58         ` Gerd Hoffmann
2018-07-04  9:19         ` Daniel Vetter
2018-07-04  9:19           ` Daniel Vetter
2018-07-04  9:19           ` Daniel Vetter
2018-07-04  9:19           ` daniel
2018-07-04  9:19           ` Daniel Vetter
2018-07-04  9:19           ` Daniel Vetter
2018-08-27  9:34           ` Gerd Hoffmann
2018-08-27  9:34             ` Gerd Hoffmann
2018-08-27  9:34             ` kraxel
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=20180831070424.3xoxfy54vyxbdfzd@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=airlied@linux.ie \
    --cc=corbet@lwn.net \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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=tomeu.vizoso@collabora.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.