All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tina Zhang <tina.zhang@intel.com>
To: zhenyuw@linux.intel.com
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org,
	Gerd Hoffmann <kraxel@redhat.com>,
	intel-gvt-dev@lists.freedesktop.org
Subject: [PATCH v14 5/7] vfio: ABI for mdev display dma-buf operation
Date: Fri, 18 Aug 2017 18:21:34 +0800	[thread overview]
Message-ID: <1503051696-5158-6-git-send-email-tina.zhang@intel.com> (raw)
In-Reply-To: <1503051696-5158-1-git-send-email-tina.zhang@intel.com>

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.

v14:
- add PROBE, DMABUF and REGION flags. (Alex)

v12:
- add drm_format_mod back. (Gerd and Zhenyu)
- add region_index. (Gerd)

v11:
- rename plane_type to drm_plane_type. (Gerd)
- move fields of vfio_device_query_gfx_plane to vfio_device_gfx_plane_info.
  (Gerd)
- remove drm_format_mod, start fields. (Daniel)
- remove plane_id.

v10:
- refine the ABI API VFIO_DEVICE_QUERY_GFX_PLANE. (Alex) (Gerd)

v3:
- add a field gvt_plane_info in the drm_i915_gem_obj structure to save
  the decoded plane information to avoid look up while need the plane
  info. (Gerd)

Signed-off-by: Tina Zhang <tina.zhang@intel.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>

diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
index ae46105..fccc87f 100644
--- a/include/uapi/linux/vfio.h
+++ b/include/uapi/linux/vfio.h
@@ -502,6 +502,49 @@ struct vfio_pci_hot_reset {
 
 #define VFIO_DEVICE_PCI_HOT_RESET	_IO(VFIO_TYPE, VFIO_BASE + 13)
 
+/**
+ * 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, -errno on
+ * other failure.
+ */
+struct vfio_device_gfx_plane_info {
+	__u32 argsz;
+	__u32 flags;
+#define VFIO_GFX_PLANE_TYPE_PROBE (1 << 0)
+#define VFIO_GFX_PLANE_TYPE_DMABUF (1 << 1)
+#define VFIO_GFX_PLANE_TYPE_REGION (1 << 2)
+	/* in */
+	__u32 drm_plane_type;	/* type of plane: DRM_PLANE_TYPE_* */
+	/* out */
+	__u32 drm_format;	/* drm format of plane */
+	__u64 drm_format_mod;   /* tiled mode */
+	__u32 width;	/* width of plane */
+	__u32 height;	/* height of plane */
+	__u32 stride;	/* stride of plane */
+	__u32 size;	/* size of plane in bytes, align on page*/
+	__u32 x_pos;	/* horizontal position of cursor plane, upper left corner in pixels */
+	__u32 y_pos;	/* vertical position of cursor plane, upper left corner in lines*/
+	union {
+		__u32 region_index;	/* region index */
+		__s32 fd;	/* dma-buf fd */
+	};
+};
+
+#define VFIO_DEVICE_QUERY_GFX_PLANE _IO(VFIO_TYPE, VFIO_BASE + 14)
+
+
 /* -------- API for Type1 VFIO IOMMU -------- */
 
 /**
-- 
2.7.4

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-08-18 10:21 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 ` Tina Zhang [this message]
2017-08-22  8:33   ` [PATCH v14 5/7] vfio: ABI for mdev display dma-buf operation Gerd Hoffmann
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=1503051696-5158-6-git-send-email-tina.zhang@intel.com \
    --to=tina.zhang@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=kraxel@redhat.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.