From: Gerd Hoffmann <kraxel@redhat.com>
To: Tina Zhang <tina.zhang@intel.com>,
alex.williamson@redhat.com, chris@chris-wilson.co.uk,
zhenyuw@linux.intel.com, zhiyuan.lv@intel.com,
zhi.a.wang@intel.com, kevin.tian@intel.com, daniel@ffwll.ch,
kwankhede@nvidia.com
Cc: intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v15 5/7] vfio: ABI for mdev display dma-buf operation
Date: Tue, 10 Oct 2017 16:07:31 +0200 [thread overview]
Message-ID: <1507644451.27800.10.camel@redhat.com> (raw)
In-Reply-To: <1507629007-3183-6-git-send-email-tina.zhang@intel.com>
On Tue, 2017-10-10 at 17:50 +0800, Tina Zhang wrote:
> Add VFIO_DEVICE_QUERY_GFX_PLANE ioctl command to let user mode query
> and
> get the plan and its related information. This ioctl can be invoked
> with:
> 1) either flag DMABUF or REGION is set. Vendor driver returns success
> and
> the plane_info only when the specific kind of buffer is supported.
> 2) flag PROBE is set with either DMABUF or REGION. Vendor driver
> returns
> success only when the specific kind of buffer is supported.
>
> The dma-buf's life cycle is handled by user mode and tracked by
> kernel.
> The returned fd in struct vfio_device_query_gfx_plane can be a new
> fd or an old fd of a re-exported dma-buf. Host user mode can check
> the
> value of fd and to see if it needs to create new resource according
> to
> the new fd or just use the existed resource related to the old fd.
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
cheers,
Gerd
next prev parent reply other threads:[~2017-10-10 14:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 9:50 [PATCH v15 0/7] drm/i915/gvt: Dma-buf support for GVT-g Tina Zhang
2017-10-10 9:50 ` [PATCH v15 1/7] drm/i915/gvt: Add framebuffer decoder support Tina Zhang
2017-10-10 9:50 ` [PATCH v15 2/7] drm: Introduce RGB 64-bit 16:16:16:16 float format Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 9:50 ` [PATCH v15 3/7] drm/i915/gvt: Add " Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 9:50 ` [PATCH v15 4/7] drm/i915/gvt: Add opregion support Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-11 4:29 ` Du, Changbin
2017-10-11 4:29 ` Du, Changbin
2017-10-10 9:50 ` [PATCH v15 5/7] vfio: ABI for mdev display dma-buf operation Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 14:07 ` Gerd Hoffmann [this message]
2017-10-10 19:16 ` Alex Williamson
2017-10-11 1:46 ` Zhang, Tina
2017-10-11 1:46 ` Zhang, Tina
2017-10-11 2:18 ` Alex Williamson
2017-10-11 2:18 ` Alex Williamson
2017-10-11 6:27 ` Gerd Hoffmann
2017-10-10 9:50 ` [PATCH v15 6/7] drm/i915: Introduce GEM proxy Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 10:58 ` Joonas Lahtinen
2017-10-10 13:02 ` [Intel-gfx] " Joonas Lahtinen
2017-10-11 1:54 ` Zhang, Tina
2017-10-10 9:50 ` [PATCH v15 7/7] drm/i915/gvt: Dmabuf support for GVT-g Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 10:05 ` ✗ Fi.CI.BAT: failure for drm/i915/gvt: Dma-buf " Patchwork
2017-10-10 14:06 ` [PATCH v15 0/7] " Gerd Hoffmann
2017-10-10 14:06 ` 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=1507644451.27800.10.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kevin.tian@intel.com \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tina.zhang@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.com \
--cc=zhiyuan.lv@intel.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.