From: Alex Williamson <alex.williamson@redhat.com>
To: torvalds@linux-foundation.org
Cc: aafabbri@cisco.com, kvm@vger.kernel.org, joerg.roedel@amd.com,
B07421@freescale.com, aik@ozlabs.ru, konrad.wilk@oracle.com,
linux-pci@vger.kernel.org, agraf@suse.de, qemu-devel@nongnu.org,
chrisw@sous-sol.org, B08248@freescale.com,
iommu@lists.linux-foundation.org, ddutile@redhat.com,
avi@redhat.com, gregkh@linuxfoundation.org, bhelgaas@google.com,
benve@cisco.com, dwmw2@infradead.org,
linux-kernel@vger.kernel.org, david@gibson.dropbear.id.au
Subject: [Qemu-devel] [GIT PULL (PATCH 0/4) v2] VFIO driver for v3.6
Date: Thu, 26 Jul 2012 10:14:48 -0600 [thread overview]
Message-ID: <1343319288.3125.24.camel@ul30vt> (raw)
In-Reply-To: <20120725142254.12800.61860.stgit@bling.home>
On Wed, 2012-07-25 at 08:53 -0600, Alex Williamson wrote:
> Hi Linus,
>
> This series includes the VFIO userspace driver interface for the
> 3.6 kernel merge window. This driver is intended to provide a
> secure interface for device access using IOMMU protection for
> applications like assignment of physical devices to virtual
> machines. Qemu will be the first user of this interface, enabling
> assignment of PCI devices to Qemu guests. This interface is
> intended to eventually replace the x86-specific assignment mechanism
> currently available in KVM. This interface has the advantage of
> being more secure, by working with IOMMU groups to ensure device
> isolation and providing it's own filtered resource access mechanism,
> and also more flexible, in not being x86 or KVM specific (extensions
> to enable POWER are already working).
>
> As a new driver, I'm including both the individual patches in email,
> as well as a branch to pull from:
>
> git://github.com/awilliam/linux-vfio.git for-linus
>
> This driver is originally the work of Tom Lyon, but has since been
> handed over to me and gone through a complete overhaul thanks to the
> input from David Gibson, Ben Herrenschmidt, Chris Wright, Joerg
> Roedel, and others. This driver has been available in linux-next for
> the last month. Thanks,
randconfig testing in next found a dependency issue that I've fix in the
for-linus branch above. Change from v1 is:
diff --git a/drivers/vfio/pci/Kconfig b/drivers/vfio/pci/Kconfig
index cc7db62..5980758 100644
--- a/drivers/vfio/pci/Kconfig
+++ b/drivers/vfio/pci/Kconfig
@@ -1,6 +1,6 @@
config VFIO_PCI
tristate "VFIO support for PCI devices"
- depends on VFIO && PCI
+ depends on VFIO && PCI && EVENTFD
help
Support for the PCI VFIO bus driver. This is required to make
use of PCI drivers using the VFIO framework.
If anyone wants a full resend of v2 to the list with this change, please
let me know. Thanks,
Alex
> ---
>
> Alex Williamson (4):
> vfio: Add PCI device driver
> vfio: Type1 IOMMU implementation
> vfio: Add documentation
> vfio: VFIO core
>
>
> Documentation/ioctl/ioctl-number.txt | 1
> Documentation/vfio.txt | 314 +++++++
> MAINTAINERS | 8
> drivers/Kconfig | 2
> drivers/Makefile | 1
> drivers/vfio/Kconfig | 16
> drivers/vfio/Makefile | 3
> drivers/vfio/pci/Kconfig | 8
> drivers/vfio/pci/Makefile | 4
> drivers/vfio/pci/vfio_pci.c | 579 +++++++++++++
> drivers/vfio/pci/vfio_pci_config.c | 1540 ++++++++++++++++++++++++++++++++++
> drivers/vfio/pci/vfio_pci_intrs.c | 740 ++++++++++++++++
> drivers/vfio/pci/vfio_pci_private.h | 91 ++
> drivers/vfio/pci/vfio_pci_rdwr.c | 269 ++++++
> drivers/vfio/vfio.c | 1420 +++++++++++++++++++++++++++++++
> drivers/vfio/vfio_iommu_type1.c | 753 +++++++++++++++++
> include/linux/vfio.h | 445 ++++++++++
> 17 files changed, 6194 insertions(+)
> create mode 100644 Documentation/vfio.txt
> create mode 100644 drivers/vfio/Kconfig
> create mode 100644 drivers/vfio/Makefile
> create mode 100644 drivers/vfio/pci/Kconfig
> create mode 100644 drivers/vfio/pci/Makefile
> create mode 100644 drivers/vfio/pci/vfio_pci.c
> create mode 100644 drivers/vfio/pci/vfio_pci_config.c
> create mode 100644 drivers/vfio/pci/vfio_pci_intrs.c
> create mode 100644 drivers/vfio/pci/vfio_pci_private.h
> create mode 100644 drivers/vfio/pci/vfio_pci_rdwr.c
> create mode 100644 drivers/vfio/vfio.c
> create mode 100644 drivers/vfio/vfio_iommu_type1.c
> create mode 100644 include/linux/vfio.h
next prev parent reply other threads:[~2012-07-26 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 14:53 [Qemu-devel] [GIT PULL (PATCH 0/4)] VFIO driver for v3.6 Alex Williamson
2012-07-25 14:53 ` [Qemu-devel] [PATCH 1/4] vfio: VFIO core Alex Williamson
2012-07-25 14:53 ` [Qemu-devel] [PATCH 2/4] vfio: Add documentation Alex Williamson
2012-07-25 14:53 ` [Qemu-devel] [PATCH 3/4] vfio: Type1 IOMMU implementation Alex Williamson
2012-07-25 14:53 ` [Qemu-devel] [PATCH 4/4] vfio: Add PCI device driver Alex Williamson
2012-07-26 16:14 ` Alex Williamson [this message]
2012-07-27 5:32 ` [Qemu-devel] [GIT PULL (PATCH 0/4)] VFIO driver for v3.6 Paul Mackerras
2012-07-30 23:17 ` Alex Williamson
2012-07-31 5:11 ` Linus Torvalds
2012-07-31 14:53 ` Alex Williamson
2012-07-31 16:33 ` 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=1343319288.3125.24.camel@ul30vt \
--to=alex.williamson@redhat.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=aafabbri@cisco.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=avi@redhat.com \
--cc=benve@cisco.com \
--cc=bhelgaas@google.com \
--cc=chrisw@sous-sol.org \
--cc=david@gibson.dropbear.id.au \
--cc=ddutile@redhat.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=torvalds@linux-foundation.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).