From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754056Ab2FZVSq (ORCPT ); Tue, 26 Jun 2012 17:18:46 -0400 Received: from gate.crashing.org ([63.228.1.57]:51381 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751036Ab2FZVSo (ORCPT ); Tue, 26 Jun 2012 17:18:44 -0400 Message-ID: <1340745479.3732.18.camel@pasglop> Subject: Re: Request VFIO inclusion in linux-next From: Benjamin Herrenschmidt To: Alex Williamson Cc: Stephen Rothwell , Linus Torvalds , Andrew Morton , Greg Kroah-Hartman , linux-kernel , kvm , linux-pci , iommu , qemu-devel , Alexey Kardashevskiy , David Gibson , chrisw , "Roedel, Joerg" , linux-next@vger.kernel.org Date: Wed, 27 Jun 2012 07:17:59 +1000 In-Reply-To: <1340686552.1207.128.camel@bling.home> References: <1340686552.1207.128.camel@bling.home> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2012-06-25 at 22:55 -0600, Alex Williamson wrote: > 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. Ack. Let's get that in, it's been simmering for too long and we'll need that to do PCI pass-through on KVM powerpc. Cheers, Ben. > 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 > > 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 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-pci" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: Request VFIO inclusion in linux-next Date: Wed, 27 Jun 2012 07:17:59 +1000 Message-ID: <1340745479.3732.18.camel@pasglop> References: <1340686552.1207.128.camel@bling.home> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1340686552.1207.128.camel-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Alex Williamson Cc: Stephen Rothwell , kvm , Alexey Kardashevskiy , Greg Kroah-Hartman , linux-kernel , qemu-devel , chrisw , iommu , linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-pci , Andrew Morton , Linus Torvalds , David Gibson List-Id: linux-next.vger.kernel.org On Mon, 2012-06-25 at 22:55 -0600, Alex Williamson wrote: > 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. Ack. Let's get that in, it's been simmering for too long and we'll need that to do PCI pass-through on KVM powerpc. Cheers, Ben. > 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 > > 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 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-pci" in > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > More majordomo info at http://vger.kernel.org/majordomo-info.html