similar to: [RFC PATCH] drm/virtio: Export resource handles via DMA-buf API

Displaying 20 results from an estimated 40000 matches similar to: "[RFC PATCH] drm/virtio: Export resource handles via DMA-buf API"

2019 Sep 17
0
[RFC PATCH] drm/virtio: Export resource handles via DMA-buf API
On Thu, Sep 12, 2019 at 06:41:21PM +0900, Tomasz Figa wrote: > This patch is an early RFC to judge the direction we are following in > our virtualization efforts in Chrome OS. The purpose is to start a > discussion on how to handle buffer sharing between multiple virtio > devices. > > On a side note, we are also working on a virtio video decoder interface > and
2019 Oct 08
0
[RFC PATCH] drm/virtio: Export resource handles via DMA-buf API
On Sat, Oct 05, 2019 at 02:41:54PM +0900, Tomasz Figa wrote: > Hi Daniel, Gerd, > > On Tue, Sep 17, 2019 at 10:23 PM Daniel Vetter <daniel at ffwll.ch> wrote: > > > > On Thu, Sep 12, 2019 at 06:41:21PM +0900, Tomasz Figa wrote: > > > This patch is an early RFC to judge the direction we are following in > > > our virtualization efforts in Chrome OS. The
2019 Oct 08
0
[RFC PATCH] drm/virtio: Export resource handles via DMA-buf API
On Tue, Oct 08, 2019 at 07:49:39PM +0900, Tomasz Figa wrote: > On Tue, Oct 8, 2019 at 7:03 PM Daniel Vetter <daniel at ffwll.ch> wrote: > > > > On Sat, Oct 05, 2019 at 02:41:54PM +0900, Tomasz Figa wrote: > > > Hi Daniel, Gerd, > > > > > > On Tue, Sep 17, 2019 at 10:23 PM Daniel Vetter <daniel at ffwll.ch> wrote: > > > > > >
2019 Oct 16
0
[RFC PATCH] drm/virtio: Export resource handles via DMA-buf API
On Wed, Oct 16, 2019 at 12:19:02PM +0900, Tomasz Figa wrote: > On Wed, Oct 9, 2019 at 12:04 AM Daniel Vetter <daniel at ffwll.ch> wrote: > > > > On Tue, Oct 08, 2019 at 07:49:39PM +0900, Tomasz Figa wrote: > > > On Tue, Oct 8, 2019 at 7:03 PM Daniel Vetter <daniel at ffwll.ch> wrote: > > > > > > > > On Sat, Oct 05, 2019 at 02:41:54PM
2020 May 13
2
[PATCH v3 1/4] dma-buf: add support for virtio exported objects
On Wed, Mar 11, 2020 at 12:20 PM David Stevens <stevensd at chromium.org> wrote: > > This change adds a new dma-buf operation that allows dma-bufs to be used > by virtio drivers to share exported objects. The new operation allows > the importing driver to query the exporting driver for the UUID which > identifies the underlying exported object. > > Signed-off-by: David
2020 May 13
2
[PATCH v3 1/4] dma-buf: add support for virtio exported objects
On Wed, Mar 11, 2020 at 12:20 PM David Stevens <stevensd at chromium.org> wrote: > > This change adds a new dma-buf operation that allows dma-bufs to be used > by virtio drivers to share exported objects. The new operation allows > the importing driver to query the exporting driver for the UUID which > identifies the underlying exported object. > > Signed-off-by: David
2019 Sep 13
0
[RFC PATCH] drm/virtio: Export resource handles via DMA-buf API
Hi, > > > To seamlessly enable buffer sharing with drivers using such frameworks, > > > make the virtio-gpu driver expose the resource handle as the DMA address > > > of the buffer returned from the DMA-buf mapping operation. Arguably, the > > > resource handle is a kind of DMA address already, as it is the buffer > > > identifier that the device
2020 Mar 04
0
[PATCH v2 1/4] dma-buf: add support for virtio exported objects
On Mon, Mar 02, 2020 at 09:15:21PM +0900, David Stevens wrote: > This change adds a new dma-buf operation that allows dma-bufs to be used > by virtio drivers to share exported objects. The new operation allows > the importing driver to query the exporting driver for the UUID which > identifies the underlying exported object. > > Signed-off-by: David Stevens <stevensd at
2019 Sep 12
0
[RFC PATCH] drm/virtio: Export resource handles via DMA-buf API
Hi, > To seamlessly enable buffer sharing with drivers using such frameworks, > make the virtio-gpu driver expose the resource handle as the DMA address > of the buffer returned from the DMA-buf mapping operation. Arguably, the > resource handle is a kind of DMA address already, as it is the buffer > identifier that the device needs to access the backing memory, which is >
2019 Oct 16
0
[RFC PATCH] drm/virtio: Export resource handles via DMA-buf API
Hi, > up later when given a buffer index. But we would still need to make > the DMA-buf itself importable. For virtio-gpu I guess that would mean > returning an sg_table backed by the shadow buffer pages. The virtio-gpu driver in drm-misc-next supports dma-buf exports. cheers, Gerd
2014 Sep 29
1
[RFC PATCH 7/7] drm/prime: Support explicit fence on export
On Fri, Sep 26, 2014 at 01:00:12PM +0300, Lauri Peltonen wrote: > Allow user space to provide an explicit sync fence fd when exporting > a dma-buf from gem handle. The fence will be stored as the explicit > fence to the reservation object. > > Signed-off-by: Lauri Peltonen <lpeltonen at nvidia.com> All existing userspace treats dma_bufs as long-lived objects. Well, all the
2014 Sep 26
0
[RFC PATCH 7/7] drm/prime: Support explicit fence on export
Allow user space to provide an explicit sync fence fd when exporting a dma-buf from gem handle. The fence will be stored as the explicit fence to the reservation object. Signed-off-by: Lauri Peltonen <lpeltonen at nvidia.com> --- drivers/gpu/drm/drm_prime.c | 41 +++++++++++++++++++++++++++++++++-------- include/uapi/drm/drm.h | 9 ++++++++- 2 files changed, 41 insertions(+), 9
2020 Sep 10
0
[PATCH v7 1/3] virtio: add dma-buf support for exported objects
On Tue, Aug 18, 2020 at 04:13:41PM +0900, David Stevens wrote: > This change adds a new flavor of dma-bufs that can be used by virtio > drivers to share exported objects. A virtio dma-buf can be queried by > virtio drivers to obtain the UUID which identifies the underlying > exported object. > > Signed-off-by: David Stevens <stevensd at chromium.org> This makes VIRTIO
2020 Jun 19
0
[PATCH v4 1/3] virtio: add dma-buf support for exported objects
Hi David, On Fri, Jun 19, 2020 at 10:57:37AM +0900, David Stevens wrote: > On Thu, Jun 18, 2020 at 9:29 PM Guennadi Liakhovetski > <guennadi.liakhovetski at linux.intel.com> wrote: > > > > Hi Michael, > > > > On Thu, Jun 04, 2020 at 03:05:23PM -0400, Michael S. Tsirkin wrote: > > > On Tue, May 26, 2020 at 07:58:09PM +0900, David Stevens wrote: >
2020 Jun 08
0
[PATCH v4 1/3] virtio: add dma-buf support for exported objects
On Mon, Jun 08, 2020 at 05:32:26PM +0900, David Stevens wrote: > On Mon, Jun 8, 2020 at 3:00 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > On Mon, Jun 08, 2020 at 10:33:09AM +0900, David Stevens wrote: > > > On Sun, Jun 7, 2020 at 5:04 AM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > > > > > On Fri, Jun 05, 2020 at
2020 Jun 04
2
[PATCH v4 1/3] virtio: add dma-buf support for exported objects
On Tue, May 26, 2020 at 07:58:09PM +0900, David Stevens wrote: > This change adds a new flavor of dma-bufs that can be used by virtio > drivers to share exported objects. A virtio dma-buf can be queried by > virtio drivers to obtain the UUID which identifies the underlying > exported object. > > Signed-off-by: David Stevens <stevensd at chromium.org> Is this just for
2020 Jun 04
2
[PATCH v4 1/3] virtio: add dma-buf support for exported objects
On Tue, May 26, 2020 at 07:58:09PM +0900, David Stevens wrote: > This change adds a new flavor of dma-bufs that can be used by virtio > drivers to share exported objects. A virtio dma-buf can be queried by > virtio drivers to obtain the UUID which identifies the underlying > exported object. > > Signed-off-by: David Stevens <stevensd at chromium.org> Is this just for
2020 Aug 13
0
[PATCH 20/20] drm: Remove obsolete GEM and PRIME callbacks from struct drm_driver
Several GEM and PRIME callbacks have been deprecated in favor of per-instance GEM object functions. Remove the callbacks as they are now unused. The only exception is .gem_prime_mmap, which is still in use by several drivers. What is also gone is gem_vm_ops in struct drm_driver. All drivers now use struct drm_gem_object_funcs.vm_ops instead. While at it, the patch also improves error handling
2020 Sep 15
0
[PATCH v2 21/21] drm: Remove obsolete GEM and PRIME callbacks from struct drm_driver
Several GEM and PRIME callbacks have been deprecated in favor of per-instance GEM object functions. Remove the callbacks as they are now unused. The only exception is .gem_prime_mmap, which is still in use by several drivers. What is also gone is gem_vm_ops in struct drm_driver. All drivers now use struct drm_gem_object_funcs.vm_ops instead. While at it, the patch also improves error handling
2020 Jun 06
0
[PATCH v4 1/3] virtio: add dma-buf support for exported objects
On Fri, Jun 05, 2020 at 10:28:42AM +0900, David Stevens wrote: > On Fri, Jun 5, 2020 at 4:05 AM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > On Tue, May 26, 2020 at 07:58:09PM +0900, David Stevens wrote: > > > This change adds a new flavor of dma-bufs that can be used by virtio > > > drivers to share exported objects. A virtio dma-buf can be queried