From: eric.auger@redhat.com (Eric Auger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v13 00/15] KVM PCIe/MSI passthrough on ARM/ARM64
Date: Thu, 6 Oct 2016 08:45:16 +0000 [thread overview]
Message-ID: <1475743531-4780-1-git-send-email-eric.auger@redhat.com> (raw)
Following Robin's series [1], addressing MSI IOMMU mapping for devices
attached to a DMA ops domain, quite a lot of changes (and simplifications)
were induced with respect to the v12 iteration:
- msi-iommu API role now is handled at dma-iommu level
- MSI doorbell registration API still is used for security assessment
and doorbell overall iommu page size computation.
- MSI layer part II is not needed anymore since mapping directly is
done in the irqchip compose callback.
The VFIO user API and VFIO layer changes have not changed though. All the
patches now are in the same series.
Tested on AMD Overdrive (single GICv2m frame) with I350 VF assignment.
dependency:
the series depends on Robin's generic-v7 branch:
[1] [PATCH v7 00/22] Generic DT bindings for PCI IOMMUs and ARM SMMU
http://www.spinics.net/lists/arm-kernel/msg531110.html
Best Regards
Eric
Git: complete series available at
https://github.com/eauger/linux/tree/generic-v7-pcie-passthru-v13
the above branch includes a temporary patch to work around a ThunderX pci
bus reset crash (which I think unrelated to this series):
"vfio: pci: HACK! workaround thunderx pci_try_reset_bus crash"
Do not take this one for other platforms.
Eric Auger (14):
iommu: Introduce DOMAIN_ATTR_MSI_GEOMETRY
iommu/arm-smmu: Initialize the msi geometry
genirq/msi: Introduce the MSI doorbell API
genirq/msi: msi_doorbell_calc_pages
irqchip/gic-v2m: Register the MSI doorbell
irqchip/gicv3-its: Register the MSI doorbell
vfio: Introduce a vfio_dma type field
vfio/type1: vfio_find_dma accepting a type argument
vfio/type1: Implement recursive vfio_find_dma_from_node
vfio/type1: Handle unmap/unpin and replay for VFIO_IOVA_RESERVED slots
vfio: Allow reserved msi iova registration
vfio/type1: Check doorbell safety
iommu/arm-smmu: Do not advertise IOMMU_CAP_INTR_REMAP
vfio/type1: Return the MSI geometry through VFIO_IOMMU_GET_INFO
capability chains
Robin Murphy (1):
iommu/dma: Allow MSI-only cookies
drivers/iommu/Kconfig | 2 +
drivers/iommu/arm-smmu-v3.c | 5 +-
drivers/iommu/arm-smmu.c | 6 +-
drivers/iommu/dma-iommu.c | 40 +++++++
drivers/iommu/iommu.c | 5 +
drivers/irqchip/irq-gic-v2m.c | 11 +-
drivers/irqchip/irq-gic-v3-its.c | 14 +++
drivers/vfio/Kconfig | 1 +
drivers/vfio/vfio_iommu_type1.c | 244 ++++++++++++++++++++++++++++++++++++---
include/linux/dma-iommu.h | 9 ++
include/linux/iommu.h | 14 +++
include/linux/msi-doorbell.h | 92 +++++++++++++++
include/uapi/linux/vfio.h | 42 ++++++-
kernel/irq/Kconfig | 4 +
kernel/irq/Makefile | 1 +
kernel/irq/msi-doorbell.c | 162 ++++++++++++++++++++++++++
16 files changed, 633 insertions(+), 19 deletions(-)
create mode 100644 include/linux/msi-doorbell.h
create mode 100644 kernel/irq/msi-doorbell.c
--
1.9.1
next reply other threads:[~2016-10-06 8:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 8:45 Eric Auger [this message]
2016-10-06 8:45 ` [PATCH v13 01/15] iommu: Introduce DOMAIN_ATTR_MSI_GEOMETRY Eric Auger
2016-10-06 8:45 ` [PATCH v13 02/15] iommu/arm-smmu: Initialize the msi geometry Eric Auger
2016-10-06 20:16 ` Alex Williamson
2016-10-06 8:45 ` [PATCH v13 03/15] iommu/dma: Allow MSI-only cookies Eric Auger
2016-10-06 20:17 ` Alex Williamson
2016-10-07 17:14 ` Auger Eric
2016-10-10 14:26 ` Robin Murphy
2016-10-10 14:47 ` Auger Eric
2016-10-10 15:52 ` Robin Murphy
2016-10-06 8:45 ` [PATCH v13 04/15] genirq/msi: Introduce the MSI doorbell API Eric Auger
2016-10-06 20:17 ` Alex Williamson
2016-10-07 17:13 ` Auger Eric
2016-10-06 8:45 ` [PATCH v13 05/15] genirq/msi: msi_doorbell_calc_pages Eric Auger
2016-10-06 8:45 ` [PATCH v13 06/15] irqchip/gic-v2m: Register the MSI doorbell Eric Auger
2016-10-06 8:45 ` [PATCH v13 07/15] irqchip/gicv3-its: " Eric Auger
2016-10-06 8:45 ` [PATCH v13 08/15] vfio: Introduce a vfio_dma type field Eric Auger
2016-10-06 20:18 ` Alex Williamson
2016-10-06 8:45 ` [PATCH v13 09/15] vfio/type1: vfio_find_dma accepting a type argument Eric Auger
2016-10-06 20:18 ` Alex Williamson
2016-10-06 8:45 ` [PATCH v13 10/15] vfio/type1: Implement recursive vfio_find_dma_from_node Eric Auger
2016-10-06 20:19 ` Alex Williamson
2016-10-06 8:45 ` [PATCH v13 11/15] vfio/type1: Handle unmap/unpin and replay for VFIO_IOVA_RESERVED slots Eric Auger
2016-10-06 20:19 ` Alex Williamson
2016-10-07 17:11 ` Auger Eric
2016-10-06 8:45 ` [PATCH v13 12/15] vfio: Allow reserved msi iova registration Eric Auger
2016-10-06 20:19 ` Alex Williamson
2016-10-07 17:11 ` Auger Eric
2016-10-07 20:45 ` Alex Williamson
2016-10-06 8:45 ` [PATCH v13 13/15] vfio/type1: Check doorbell safety Eric Auger
2016-10-06 20:19 ` Alex Williamson
2016-10-06 8:45 ` [PATCH v13 14/15] iommu/arm-smmu: Do not advertise IOMMU_CAP_INTR_REMAP Eric Auger
2016-10-06 8:45 ` [PATCH v13 15/15] vfio/type1: Return the MSI geometry through VFIO_IOMMU_GET_INFO capability chains Eric Auger
2016-10-06 20:20 ` Alex Williamson
2016-10-06 20:42 ` Alex Williamson
2016-10-07 17:10 ` Auger Eric
2016-10-07 20:38 ` Alex Williamson
2016-10-10 15:01 ` Auger Eric
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=1475743531-4780-1-git-send-email-eric.auger@redhat.com \
--to=eric.auger@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).