From: Feng Wu <feng.wu@intel.com>
To: alex.williamson@redhat.com, pbonzini@redhat.com
Cc: kvm@vger.kernel.org, Feng Wu <feng.wu@intel.com>
Subject: [RFC PATCH v1 0/2] Define some VFIO interfaces for VT-d Posted-Interrupts
Date: Thu, 20 Nov 2014 17:05:14 +0800 [thread overview]
Message-ID: <1416474316-32159-1-git-send-email-feng.wu@intel.com> (raw)
VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
With VT-d Posted-Interrupts enabled, external interrupts from
direct-assigned devices can be delivered to guests without VMM
intervention when guest is running in non-root mode.
You can find the VT-d Posted-Interrtups Spec. in the following URL:
http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/vt-directed-io-spec.html
This patch set does the following things:
- Define a new VFIO group KVM_DEV_VFIO_INTERRUPT and it's attributes
KVM_DEV_VFIO_INTERRUPT_POSTING_IRQ. Qemu can use this interface to
configure VT-d PI when guest updates the interrupt configuration
(MSI/MSI-X configuration).
- Define a new VFIO API: vfio_msi_get_irq(), which can be used by KVM
to get the host irq of the assigned devices. Then KVM can update the
associated IRTE for VT-d PI.
Feng Wu (2):
vfio: Add new interrupt group for VFIO
vfio: Add VFIO API vfio_msi_get_irq
Documentation/virtual/kvm/devices/vfio.txt | 8 ++++++++
drivers/vfio/pci/vfio_pci.c | 10 ++++++++++
include/linux/vfio.h | 2 ++
include/uapi/linux/kvm.h | 14 ++++++++++++++
4 files changed, 34 insertions(+), 0 deletions(-)
next reply other threads:[~2014-11-20 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 9:05 Feng Wu [this message]
2014-11-20 9:05 ` [RFC PATCH v1 1/2] vfio: Add new interrupt group for VFIO Feng Wu
2014-11-20 15:53 ` Alex Williamson
2014-11-20 16:03 ` Eric Auger
[not found] ` <E959C4978C3B6342920538CF579893F0022A8711@SHSMSX104.ccr.corp.intel.com>
2014-11-21 19:35 ` Alex Williamson
2014-11-20 9:05 ` [RFC PATCH v1 2/2] vfio: Add VFIO API vfio_msi_get_irq Feng Wu
2014-11-20 16:05 ` Alex Williamson
2014-11-20 16:12 ` Eric Auger
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=1416474316-32159-1-git-send-email-feng.wu@intel.com \
--to=feng.wu@intel.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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