From: Gerd Hoffmann <kraxel@redhat.com>
To: Tina Zhang <tina.zhang@intel.com>
Cc: intel-gvt-dev@lists.freedesktop.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, 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 v3 1/4] vfio: Define device specific irq type capability
Date: Thu, 27 Jun 2019 08:19:42 +0200 [thread overview]
Message-ID: <20190627061942.k5onxbm27dju3iv5@sirius.home.kraxel.org> (raw)
In-Reply-To: <20190627033802.1663-2-tina.zhang@intel.com>
Hi,
> +struct vfio_irq_info_cap_type {
> + struct vfio_info_cap_header header;
> + __u32 type; /* global per bus driver */
> + __u32 subtype; /* type specific */
Do we really need both type and subtype?
cheers,
Gerd
next prev parent reply other threads:[~2019-06-27 6:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 3:37 [RFC PATCH v3 0/4] Deliver vGPU display vblank event to userspace Tina Zhang
2019-06-27 3:37 ` [RFC PATCH v3 1/4] vfio: Define device specific irq type capability Tina Zhang
2019-06-27 4:07 ` Alex Williamson
2019-06-27 8:40 ` Zhang, Tina
2019-06-27 6:19 ` Gerd Hoffmann [this message]
2019-06-27 8:55 ` Zhang, Tina
2019-06-27 10:20 ` Gerd Hoffmann
2019-06-27 3:38 ` [RFC PATCH v3 2/4] vfio: Introduce vGPU display irq type Tina Zhang
2019-06-27 6:20 ` Gerd Hoffmann
2019-06-27 9:11 ` Zhang, Tina
2019-06-27 3:38 ` [RFC PATCH v3 3/4] drm/i915/gvt: Register vGPU display vblank irq Tina Zhang
2019-06-27 3:38 ` [RFC PATCH v3 4/4] drm/i915/gvt: Deliver vGPU vblank event to userspace Tina Zhang
2019-06-27 6:22 ` [RFC PATCH v3 0/4] Deliver vGPU display " Gerd Hoffmann
2019-06-27 8:44 ` Zhang, Tina
2019-06-27 10:31 ` Gerd Hoffmann
2019-06-28 3:21 ` Zhenyu Wang
2019-06-28 5:43 ` Gerd Hoffmann
2019-06-28 7:23 ` Zhenyu Wang
2019-06-28 8:44 ` Zhang, Tina
2019-06-28 12:43 ` Zhang, Tina
2019-07-01 3:09 ` Zhenyu Wang
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=20190627061942.k5onxbm27dju3iv5@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=hang.yuan@intel.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--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 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).