dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
	jgross@suse.com, konrad.wilk@oracle.com
Cc: daniel.vetter@intel.com, dongwon.kim@intel.com,
	matthew.d.roper@intel.com,
	Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v4 8/9] xen/gntdev: Implement dma-buf export functionality
Date: Fri, 15 Jun 2018 17:02:23 -0400	[thread overview]
Message-ID: <901a32b1-baae-7717-31f7-23bd31e23f05@oracle.com> (raw)
In-Reply-To: <20180615062753.9229-9-andr2000@gmail.com>

On 06/15/2018 02:27 AM, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>
> 1. Create a dma-buf from grant references provided by the foreign
>    domain. By default dma-buf is backed by system memory pages, but
>    by providing GNTDEV_DMA_FLAG_XXX flags it can also be created
>    as a DMA write-combine/coherent buffer, e.g. allocated with
>    corresponding dma_alloc_xxx API.
>    Export the resulting buffer as a new dma-buf.
>
> 2. Implement waiting for the dma-buf to be released: block until the
>    dma-buf with the file descriptor provided is released.
>    If within the time-out provided the buffer is not released then
>    -ETIMEDOUT error is returned. If the buffer with the file descriptor
>    does not exist or has already been released, then -ENOENT is
>    returned. For valid file descriptors this must not be treated as
>    error.
>
> 3. Make gntdev's common code and structures available to dma-buf.
>
> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>


Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

  reply	other threads:[~2018-06-15 21:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15  6:27 [PATCH v4 0/9] xen: dma-buf support for grant device Oleksandr Andrushchenko
2018-06-15  6:27 ` [PATCH v4 1/9] xen/grant-table: Export gnttab_{alloc|free}_pages as GPL Oleksandr Andrushchenko
2018-06-15  6:27 ` [PATCH v4 2/9] xen/grant-table: Make set/clear page private code shared Oleksandr Andrushchenko
2018-06-15  6:27 ` [PATCH v4 3/9] xen/balloon: Share common memory reservation routines Oleksandr Andrushchenko
2018-06-15 20:58   ` Boris Ostrovsky
2018-06-15  6:27 ` [PATCH v4 4/9] xen/grant-table: Allow allocating buffers suitable for DMA Oleksandr Andrushchenko
2018-06-15  6:27 ` [PATCH v4 5/9] xen/gntdev: Allow mappings for DMA buffers Oleksandr Andrushchenko
2018-06-15  6:32   ` Oleksandr Andrushchenko
2018-06-15  6:46     ` Juergen Gross
2018-06-15  6:50       ` Oleksandr Andrushchenko
2018-06-15 21:07         ` Boris Ostrovsky
2018-06-18  6:17           ` Oleksandr Andrushchenko
2018-06-15  6:27 ` [PATCH v4 6/9] xen/gntdev: Make private routines/structures accessible Oleksandr Andrushchenko
2018-06-15  6:27 ` [PATCH v4 7/9] xen/gntdev: Add initial support for dma-buf UAPI Oleksandr Andrushchenko
2018-06-15 21:00   ` Boris Ostrovsky
2018-06-15  6:27 ` [PATCH v4 8/9] xen/gntdev: Implement dma-buf export functionality Oleksandr Andrushchenko
2018-06-15 21:02   ` Boris Ostrovsky [this message]
2018-07-02  7:04   ` Oleksandr Andrushchenko
2018-06-15  6:27 ` [PATCH v4 9/9] xen/gntdev: Implement dma-buf import functionality Oleksandr Andrushchenko
2018-06-15 21:03   ` Boris Ostrovsky
2018-06-18  6:11 ` [PATCH v4 0/9] xen: dma-buf support for grant device Oleksandr Andrushchenko
2018-07-02  7:10 ` Oleksandr Andrushchenko
2018-07-02  8:20   ` Juergen Gross
2018-07-02 13:12     ` Oleksandr Andrushchenko
2018-07-10 22:31       ` Boris Ostrovsky

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=901a32b1-baae-7717-31f7-23bd31e23f05@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=andr2000@gmail.com \
    --cc=daniel.vetter@intel.com \
    --cc=dongwon.kim@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=matthew.d.roper@intel.com \
    --cc=oleksandr_andrushchenko@epam.com \
    --cc=xen-devel@lists.xenproject.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).