qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@linaro.org>
To: eric.auger@st.com, eric.auger@linaro.org, qemu-devel@nongnu.org,
	alex.williamson@redhat.com
Cc: b.reynal@virtualopensystems.com, kvmarm@lists.cs.columbia.edu,
	christoffer.dall@linaro.org, patches@linaro.org
Subject: [Qemu-devel] [RFC v2 0/4] VFIO Platform device featuring IRQ forwarding
Date: Mon,  4 May 2015 13:49:54 +0100	[thread overview]
Message-ID: <1430743798-8839-1-git-send-email-eric.auger@linaro.org> (raw)

This series adds IRQ forwarding support in the VFIO platform device.

The VFIO platform device uses the KVM-VFIO device to enable IRQ forwarding.

Dependency List:
- QEMU KVM platform device passthrough and its dependencies
  see https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg04379.html
- kernel forwarding series:
  see (https://www.mail-archive.com/kvm@vger.kernel.org/msg115253.html)

Repos:
- QEMU pieces can be found at:
  http://git.linaro.org/people/eric.auger/qemu.git
  (branch vfio_integ_v15_fwd)
- kernel pieces can be found at:
  http://git.linaro.org/people/eric.auger/linux.git
  (branch 4.1-rc1_forward)

The patch series was tested on Calxeda Midway (ARMv7) where one xgmac
is assigned to KVM host while the second one is assigned to the guest.
Reworked PCI device is not tested.

Wiki for Calxeda Midway setup:
https://wiki.linaro.org/LEG/Engineering/Virtualization/Platform_Device_Passthrough_on_Midway

History:

v1 -> v2:
- update following
  x introduction of kvm qemu_irq/gsi hash table
  x new irq connect notifier
  x 2 stage eventfd/irqfd setup which complexifies irq forwarding setup

v1:
- that code originally was in KVM platform device passthrough series (v8),
  now moved in a separate RFC since dependent on many RFCs.

Best Regards

Eric


Eric Auger (4):
  linux-headers: Update KVM header for KVM-VFIO FORWARD/UNFORWARD
  hw/vfio/common: vfio_kvm_device_fd moved in the common header
  kvm: add kvm_vfio_get_device_irq
  hw/vfio/platform: add forwarded irq support

 hw/vfio/common.c                |   2 +-
 hw/vfio/platform.c              | 103 +++++++++++++++++++++++++++++++++++++---
 include/hw/vfio/vfio-common.h   |   4 ++
 include/hw/vfio/vfio-platform.h |   3 ++
 include/sysemu/kvm.h            |   5 ++
 kvm-all.c                       |  32 +++++++++++++
 linux-headers/linux/kvm.h       |  12 +++++
 trace-events                    |   1 +
 8 files changed, 154 insertions(+), 8 deletions(-)

-- 
1.8.3.2

             reply	other threads:[~2015-05-04 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 12:49 Eric Auger [this message]
2015-05-04 12:49 ` [Qemu-devel] [RFC v2 1/4] linux-headers: Update KVM header for KVM-VFIO FORWARD/UNFORWARD Eric Auger
2015-05-04 12:49 ` [Qemu-devel] [RFC v2 2/4] hw/vfio/common: vfio_kvm_device_fd moved in the common header Eric Auger
2015-05-04 12:49 ` [Qemu-devel] [RFC v2 3/4] kvm: add kvm_vfio_get_device_irq Eric Auger
2015-05-04 12:49 ` [Qemu-devel] [RFC v2 4/4] hw/vfio/platform: add forwarded irq support 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=1430743798-8839-1-git-send-email-eric.auger@linaro.org \
    --to=eric.auger@linaro.org \
    --cc=alex.williamson@redhat.com \
    --cc=b.reynal@virtualopensystems.com \
    --cc=christoffer.dall@linaro.org \
    --cc=eric.auger@st.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=patches@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).