From: Tina Zhang <tina.zhang@intel.com>
To: intel-gvt-dev@lists.freedesktop.org
Cc: Tina Zhang <tina.zhang@intel.com>,
kraxel@redhat.com, alex.williamson@redhat.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
hang.yuan@intel.com, zhiyuan.lv@intel.com
Subject: [PATCH v5 2/6] vfio: Introduce vGPU display irq type
Date: Fri, 16 Aug 2019 10:35:24 +0800 [thread overview]
Message-ID: <20190816023528.30210-3-tina.zhang@intel.com> (raw)
In-Reply-To: <20190816023528.30210-1-tina.zhang@intel.com>
Introduce vGPU specific irq type VFIO_IRQ_TYPE_GFX, and
VFIO_IRQ_SUBTYPE_GFX_DISPLAY_IRQ as the subtype for vGPU display.
Introduce vfio_irq_info_cap_display_plane_events capability to notify
user space with the vGPU's plane update events
v2:
- Add VFIO_IRQ_SUBTYPE_GFX_DISPLAY_IRQ description. (Alex & Kechen)
- Introduce vfio_irq_info_cap_display_plane_events. (Gerd & Alex)
Signed-off-by: Tina Zhang <tina.zhang@intel.com>
---
include/uapi/linux/vfio.h | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
index d83c9f136a5b..21ac69f0e1a9 100644
--- a/include/uapi/linux/vfio.h
+++ b/include/uapi/linux/vfio.h
@@ -465,6 +465,27 @@ struct vfio_irq_info_cap_type {
__u32 subtype; /* type specific */
};
+#define VFIO_IRQ_TYPE_GFX (1)
+/*
+ * vGPU vendor sub-type
+ * vGPU device display related interrupts e.g. vblank/pageflip
+ */
+#define VFIO_IRQ_SUBTYPE_GFX_DISPLAY_IRQ (1)
+
+/*
+ * Display capability of using one eventfd to notify user space with the
+ * vGPU's plane update events.
+ * cur_event_val: eventfd value stands for cursor plane change event.
+ * pri_event_val: eventfd value stands for primary plane change event.
+ */
+#define VFIO_IRQ_INFO_CAP_DISPLAY 4
+
+struct vfio_irq_info_cap_display_plane_events {
+ struct vfio_info_cap_header header;
+ __u64 cur_event_val;
+ __u64 pri_event_val;
+};
+
/**
* VFIO_DEVICE_SET_IRQS - _IOW(VFIO_TYPE, VFIO_BASE + 10, struct vfio_irq_set)
*
--
2.17.1
next prev parent reply other threads:[~2019-08-16 2:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 2:35 [PATCH v5 0/6] Deliver vGPU display refresh event to userspace Tina Zhang
2019-08-16 2:35 ` [PATCH v5 1/6] vfio: Define device specific irq type capability Tina Zhang
2019-08-16 20:51 ` Alex Williamson
2019-08-20 0:56 ` Zhang, Tina
2019-08-16 2:35 ` Tina Zhang [this message]
2019-08-16 20:51 ` [PATCH v5 2/6] vfio: Introduce vGPU display irq type Alex Williamson
2019-08-20 2:12 ` Zhang, Tina
2019-08-20 7:20 ` kraxel
2019-08-20 15:03 ` Alex Williamson
2019-08-20 15:32 ` Alex Williamson
2019-08-16 2:35 ` [PATCH v5 3/6] drm/i915/gvt: Register vGPU display event irq Tina Zhang
2019-08-16 2:35 ` [PATCH v5 4/6] drm/i915/gvt: Deliver vGPU refresh event to userspace Tina Zhang
2019-08-26 7:55 ` Zhenyu Wang
2019-08-28 1:49 ` Tian, Kevin
2019-08-28 6:59 ` Zhang, Tina
2019-08-28 7:10 ` Tian, Kevin
2019-08-28 7:39 ` Zhang, Tina
2019-08-16 2:35 ` [PATCH v5 5/6] drm/i915/gvt: Deliver async primary plane page flip events at vblank Tina Zhang
2019-08-16 2:35 ` [PATCH v5 6/6] drm/i915/gvt: Add cursor plane reg update trap emulation handler Tina Zhang
2019-09-03 1:26 ` [PATCH v5 0/6] Deliver vGPU display refresh event to userspace Zhang, Tina
2019-09-03 7:43 ` Tian, Kevin
2019-09-05 7:48 ` kraxel
2019-09-17 9:27 ` Zhang, Tina
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=20190816023528.30210-3-tina.zhang@intel.com \
--to=tina.zhang@intel.com \
--cc=alex.williamson@redhat.com \
--cc=hang.yuan@intel.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).