From: Alex Williamson <alex.williamson@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>, linux-pci <linux-pci@vger.kernel.org>,
iommu <iommu@lists.linux-foundation.org>,
qemu-devel <qemu-devel@nongnu.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
David Gibson <david@gibson.dropbear.id.au>,
chrisw <chrisw@sous-sol.org>,
"Roedel, Joerg" <Joerg.Roedel@amd.com>,
linux-next@vger.kernel.org
Subject: Request VFIO inclusion in linux-next
Date: Mon, 25 Jun 2012 22:55:52 -0600 [thread overview]
Message-ID: <1340686552.1207.128.camel@bling.home> (raw)
Hi,
VFIO has been kicking around for well over a year now and has been
posted numerous times for review. The pre-requirements are finally
available in linux-next (or will be in the 20120626 build) so I'd like
to request a new branch be included in linux-next with a goal of being
accepted into v3.6.
VFIO is a userspace driver interface designed to support assignment of
devices into virtual machines using IOMMU level access control. This
IOMMU requirement, secure resource access, and flexible interrupt
support make VFIO unique from existing drivers, like UIO. VFIO supports
modular backends for both IOMMU and device access. Initial backends are
included for PCI device assignment using the IOMMU API in a manner
compatible with x86 device assignment. POWER support is also under
development, making use of the same PCI device backend, but adding new
IOMMU support for their platforms.
As with previous versions of VFIO, Qemu is targeted as a primary user
and a working development tree including vfio-pci support can be found
here:
git://github.com/awilliam/qemu-vfio.git iommu-group-vfio
Eventually we hope VFIO can deprecate the x86, PCI-specific device
assignment currently used by KVM.
The info for linux-next:
Tree: git://github.com/awilliam/linux-vfio.git
Branch: next
Contact: Alex Williamson <alex.williamson@redhat.com>
This branch should be applied after both Bjorn's PCI next branch and
Joerg's IOMMU next branch and contains the following changes:
Documentation/ioctl/ioctl-number.txt | 1
Documentation/vfio.txt | 315 +++++++
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 | 565 ++++++++++++
drivers/vfio/pci/vfio_pci_config.c | 1528 +++++++++++++++++++++++++++++++++++
drivers/vfio/pci/vfio_pci_intrs.c | 727 ++++++++++++++++
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 | 754 +++++++++++++++++
include/linux/vfio.h | 445 ++++++++++
17 files changed, 6157 insertions(+)
If there are any objections to including this, please speak now. If
anything looks amiss in the branch, let me know. I've never hosted a
next branch. Review comments welcome and I'll be glad to post the
series in email again if requested. Thanks,
Alex
next reply other threads:[~2012-06-26 4:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 4:55 Alex Williamson [this message]
2012-06-26 21:17 ` Request VFIO inclusion in linux-next Benjamin Herrenschmidt
2012-06-26 23:50 ` Stephen Rothwell
2012-06-27 12:37 ` Dan Carpenter
2012-06-27 19:23 ` Alex Williamson
2012-06-28 6:44 ` Dan Carpenter
2012-07-02 3:41 ` Alexey Kardashevskiy
2012-07-02 4:14 ` 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=1340686552.1207.128.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=Joerg.Roedel@amd.com \
--cc=aik@ozlabs.ru \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=chrisw@sous-sol.org \
--cc=david@gibson.dropbear.id.au \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=sfr@canb.auug.org.au \
--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).