LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Tina Zhang <tina.zhang@intel.com>
Cc: intel-gvt-dev@lists.freedesktop.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, kraxel@redhat.com,
zhenyuw@linux.intel.com, zhiyuan.lv@intel.com,
zhi.a.wang@intel.com, kevin.tian@intel.com, hang.yuan@intel.com,
alex.williamson@redhat.com
Subject: Re: [RFC PATCH v2 1/3] vfio: Use capability chains to handle device specific irq
Date: Wed, 5 Jun 2019 12:04:46 +0800 [thread overview]
Message-ID: <20190605040446.GW9684@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20190604095534.10337-2-tina.zhang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2450 bytes --]
On 2019.06.04 17:55:32 +0800, Tina Zhang wrote:
> Caps the number of irqs with fixed indexes and uses capability chains
> to chain device specific irqs.
>
> VFIO vGPU leverages this mechanism to trigger primary plane and cursor
> plane page flip event to the user space.
>
> Signed-off-by: Tina Zhang <tina.zhang@intel.com>
> ---
> include/uapi/linux/vfio.h | 23 ++++++++++++++++++++++-
> 1 file changed, 22 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> index 02bb7ad6e986..9b5e25937c7d 100644
> --- a/include/uapi/linux/vfio.h
> +++ b/include/uapi/linux/vfio.h
> @@ -444,11 +444,31 @@ struct vfio_irq_info {
> #define VFIO_IRQ_INFO_MASKABLE (1 << 1)
> #define VFIO_IRQ_INFO_AUTOMASKED (1 << 2)
> #define VFIO_IRQ_INFO_NORESIZE (1 << 3)
> +#define VFIO_IRQ_INFO_FLAG_CAPS (1 << 4) /* Info supports caps */
> __u32 index; /* IRQ index */
> + __u32 cap_offset; /* Offset within info struct of first cap */
> __u32 count; /* Number of IRQs within this index */
This would break ABI for get irq info. I think irq cap chain can just follow
vfio_irq_info.
> };
> #define VFIO_DEVICE_GET_IRQ_INFO _IO(VFIO_TYPE, VFIO_BASE + 9)
>
> +/*
> + * The irq type capability allows irqs unique to a specific device or
> + * class of devices to be exposed.
> + *
> + * The structures below define version 1 of this capability.
> + */
> +#define VFIO_IRQ_INFO_CAP_TYPE 3
> +
> +struct vfio_irq_info_cap_type {
> + struct vfio_info_cap_header header;
> + __u32 type; /* global per bus driver */
> + __u32 subtype; /* type specific */
> +};
> +
> +#define VFIO_IRQ_TYPE_GFX (1)
> +#define VFIO_IRQ_SUBTYPE_GFX_PRI_PLANE_FLIP (1)
> +#define VFIO_IRQ_SUBTYPE_GFX_CUR_PLANE_FLIP (2)
> +
Really need to split for different planes? I'd like a VFIO_IRQ_SUBTYPE_GFX_DISPLAY_EVENT
so user space can probe change for all.
> /**
> * VFIO_DEVICE_SET_IRQS - _IOW(VFIO_TYPE, VFIO_BASE + 10, struct vfio_irq_set)
> *
> @@ -550,7 +570,8 @@ enum {
> VFIO_PCI_MSIX_IRQ_INDEX,
> VFIO_PCI_ERR_IRQ_INDEX,
> VFIO_PCI_REQ_IRQ_INDEX,
> - VFIO_PCI_NUM_IRQS
> + VFIO_PCI_NUM_IRQS = 5 /* Fixed user ABI, IRQ indexes >=5 use */
> + /* device specific cap to define content */
> };
>
> /*
> --
> 2.17.1
>
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-06-05 4:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 9:55 [RFC PATCH v2 0/3] Deliver vGPU page flip events to userspace Tina Zhang
2019-06-04 9:55 ` [RFC PATCH v2 1/3] vfio: Use capability chains to handle device specific irq Tina Zhang
2019-06-05 4:04 ` Zhenyu Wang [this message]
2019-06-05 9:18 ` Zhang, Tina
2019-06-05 10:09 ` kraxel
2019-06-06 2:57 ` Tian, Kevin
2019-06-06 10:17 ` Zhang, Tina
2019-06-06 16:25 ` Alex Williamson
2019-06-04 9:55 ` [RFC PATCH v2 2/3] drm/i915/gvt: Leverage irq capability chain to get eventfd Tina Zhang
2019-06-04 9:55 ` [RFC PATCH v2 3/3] drm/i915/gvt: Send plane flip events to user space Tina Zhang
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=20190605040446.GW9684@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=hang.yuan@intel.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kevin.tian@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tina.zhang@intel.com \
--cc=zhi.a.wang@intel.com \
--cc=zhiyuan.lv@intel.com \
--subject='Re: [RFC PATCH v2 1/3] vfio: Use capability chains to handle device specific irq' \
/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
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).