From: Pavel Fedin <p.fedin@samsung.com>
To: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Alex Williamson <alex.williamson@redhat.com>,
Manish Jaggi <mjaggi@caviumnetworks.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>
Subject: [PATCH v2 0/3] Introduce MSI hardware mapping for VFIO
Date: Tue, 24 Nov 2015 16:50:53 +0300 [thread overview]
Message-ID: <cover.1448372839.git.p.fedin@samsung.com> (raw)
On some architectures (e.g. ARM64) if the device is behind an IOMMU, and
is being mapped by VFIO, it is necessary to also add mappings for MSI
translation register for interrupts to work. This series implements the
necessary API to do this, and makes use of this API for GICv3 ITS on
ARM64.
v1 => v2:
- Adde dependency on CONFIG_GENERIC_MSI_IRQ_DOMAIN in some parts of the
code, should fix build without this option
Pavel Fedin (3):
vfio: Introduce map and unmap operations
gicv3, its: Introduce VFIO map and unmap operations
vfio: Introduce generic MSI mapping operations
drivers/irqchip/irq-gic-v3-its.c | 31 ++++++++++
drivers/vfio/pci/vfio_pci_intrs.c | 11 ++++
drivers/vfio/vfio.c | 116 +++++++++++++++++++++++++++++++++++++
drivers/vfio/vfio_iommu_type1.c | 29 ++++++++++
include/linux/irqchip/arm-gic-v3.h | 2 +
include/linux/msi.h | 12 ++++
include/linux/vfio.h | 17 +++++-
7 files changed, 217 insertions(+), 1 deletion(-)
--
2.4.4
next reply other threads:[~2015-11-24 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 13:50 Pavel Fedin [this message]
2015-11-24 13:50 ` [PATCH v2 1/3] vfio: Introduce map and unmap operations Pavel Fedin
2015-11-24 13:50 ` [PATCH v2 2/3] gicv3, its: Introduce VFIO " Pavel Fedin
2015-11-24 13:50 ` [PATCH v2 3/3] vfio: Introduce generic MSI mapping operations Pavel Fedin
2015-12-02 21:32 ` [PATCH v2 0/3] Introduce MSI hardware mapping for VFIO Alex Williamson
2015-12-03 13:16 ` Pavel Fedin
2015-12-03 14:49 ` Marc Zyngier
2015-12-03 17:05 ` Alex Williamson
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=cover.1448372839.git.p.fedin@samsung.com \
--to=p.fedin@samsung.com \
--cc=alex.williamson@redhat.com \
--cc=jason@lakedaemon.net \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=mjaggi@caviumnetworks.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.