From: Gerd Hoffmann <kraxel@redhat.com>
To: Tina Zhang <tina.zhang@intel.com>, zhenyuw@linux.intel.com
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org
Subject: Re: [PATCH v14 5/7] vfio: ABI for mdev display dma-buf operation
Date: Tue, 22 Aug 2017 10:33:21 +0200 [thread overview]
Message-ID: <1503390801.21217.7.camel@redhat.com> (raw)
In-Reply-To: <1503051696-5158-6-git-send-email-tina.zhang@intel.com>
On Fri, 2017-08-18 at 18:21 +0800, Tina Zhang wrote:
> +/**
> + * VFIO_DEVICE_QUERY_GFX_PLANE - _IOW(VFIO_TYPE, VFIO_BASE + 14,
> struct vfio_device_query_gfx_plane)
> + *
> + * Set the drm_plane_type and flags, then retrieve information about
> the gfx plane.
> + *
> + * flags:
> + * VFIO_GFX_PLANE_TYPE_PROBE and VFIO_GFX_PLANE_TYPE_DMABUF are
> set to ask if the mdev
> + * supports dma-buf. 0 on support, -EINVAL on no support for
> dma-buf.
> + * VFIO_GFX_PLANE_TYPE_PROBE and VFIO_GFX_PLANE_TYPE_REGION are
> set to ask if the mdev
> + * supports region. 0 on support, -EINVAL on no support for
> region.
> + * VFIO_GFX_PLANE_TYPE_DMABUF or VFIO_GFX_PLANE_TYPE_REGION is
> set with each call to
> + * query the plane info.
> + * Others are invalid and return -EINVAL.
> + *
> + * Return: 0 on success, -ENODEV with all out fields zero on mdev
> device initialization,
Do you mean PROBE calls here?
The behavior in case the guest driver hasn't yet initialized the plane
should be documented here too.
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-22 8:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 10:21 [PATCH v14 0/7] drm/i915/gvt: Dma-buf support for GVT-g Tina Zhang
2017-08-18 10:21 ` [PATCH v14 1/7] drm/i915/gvt: Add framebuffer decoder support Tina Zhang
2017-08-23 9:45 ` Zhenyu Wang
2017-08-18 10:21 ` [PATCH v14 2/7] drm: Introduce RGB 64-bit 16:16:16:16 float format Tina Zhang
2017-08-18 10:21 ` [PATCH v14 3/7] drm/i915/gvt: Add " Tina Zhang
2017-08-18 10:21 ` [PATCH v14 4/7] drm/i915/gvt: Add opregion support Tina Zhang
2017-08-18 10:21 ` [PATCH v14 5/7] vfio: ABI for mdev display dma-buf operation Tina Zhang
2017-08-22 8:33 ` Gerd Hoffmann [this message]
2017-09-26 7:12 ` Gerd Hoffmann
2017-09-27 9:03 ` Zhang, Tina
2017-09-27 10:11 ` Gerd Hoffmann
2017-09-28 23:43 ` Zhang, Tina
2017-09-29 7:11 ` Gerd Hoffmann
2017-09-29 7:04 ` Zhang, Tina
2017-09-29 7:28 ` Gerd Hoffmann
2017-09-29 7:49 ` Zhang, Tina
2017-09-29 8:03 ` Gerd Hoffmann
2017-09-29 9:08 ` Zhang, Tina
2017-09-29 10:20 ` Gerd Hoffmann
2017-09-29 23:59 ` Zhang, Tina
2017-10-06 12:12 ` Gerd Hoffmann
2017-10-07 7:39 ` Zhang, Tina
2017-09-29 7:32 ` Gerd Hoffmann
2017-08-18 10:21 ` [PATCH v14 6/7] drm/i915: Introduce GEM proxy Tina Zhang
2017-08-18 11:36 ` Joonas Lahtinen
2017-08-18 10:21 ` [PATCH v14 7/7] drm/i915/gvt: Dmabuf support for GVT-g Tina Zhang
2017-08-18 12:19 ` ✓ Fi.CI.BAT: success for drm/i915/gvt: Dma-buf " Patchwork
2017-08-25 11:47 ` [PATCH v14 0/7] " Gerd Hoffmann
2017-08-25 12:52 ` Wang, Zhi A
2017-09-04 6:23 ` Zhang, Tina
2017-09-04 6:38 ` 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=1503390801.21217.7.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=tina.zhang@intel.com \
--cc=zhenyuw@linux.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.