From: Alex Williamson <alex.williamson@redhat.com>
To: alex.williamson@redhat.com, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] vfio: type1 multi-domain support & kvm-vfio coherency checking
Date: Mon, 17 Feb 2014 13:23:49 -0700 [thread overview]
Message-ID: <20140217201324.22775.31904.stgit@bling.home> (raw)
This series switches the vfio type1 IOMMU backend to support multiple
IOMMU domains per container. As outlined in 1/4, this provides several
advantages, including supporting features like IOMMU_CACHE and allowing
bus_type independence. With such support, we're able to provide an
interface to indicate the container is fully cache coherent and export
it for use by the external user interface. This allows the kvm-vfio
pseudo device to properly test for non-coherent DMA rather than assume
it whenever a kvm-vfio device is registered.
A change introduced by 1/4 creates a new, v2 type1 IOMMU backend. This
type differs subtly in unmap behavior as described in the patch itself.
For QEMU use of VFIO, there's no change and switching to v2 is
transparent. I'd appreciate any feedback on whether we should simply
call the previous behavior broken or if we should do like implemented
here and support a compatible mode. Comments welcome. Thanks,
Alex
---
Alex Williamson (4):
vfio/iommu_type1: Multi-IOMMU domain support
vfio/type1: Add extension to test DMA cache coherence of IOMMU
vfio: Add external user check extension interface
kvm/vfio: Support for DMA coherent IOMMUs
drivers/vfio/vfio.c | 6
drivers/vfio/vfio_iommu_type1.c | 656 +++++++++++++++++++++------------------
include/linux/vfio.h | 2
include/uapi/linux/vfio.h | 6
virt/kvm/vfio.c | 27 +-
5 files changed, 389 insertions(+), 308 deletions(-)
next reply other threads:[~2014-02-17 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 20:23 Alex Williamson [this message]
2014-02-17 20:23 ` [PATCH 1/4] vfio/iommu_type1: Multi-IOMMU domain support Alex Williamson
2014-03-18 10:24 ` Varun Sethi
2014-03-18 14:16 ` Alex Williamson
[not found] ` <CAKKYfmFrRF8U3NKhkSgepDfKNeLQ8+2yiz8VSFBzMc58dNAPvg@mail.gmail.com>
2014-03-18 14:30 ` Alex Williamson
2014-02-17 20:24 ` [PATCH 2/4] vfio/type1: Add extension to test DMA cache coherence of IOMMU Alex Williamson
2014-02-17 20:24 ` [PATCH 3/4] vfio: Add external user check extension interface Alex Williamson
2014-02-17 20:24 ` [PATCH 4/4] kvm/vfio: Support for DMA coherent IOMMUs Alex Williamson
2014-02-18 10:38 ` Paolo Bonzini
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=20140217201324.22775.31904.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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