Re: [GIT PULL (PATCH 0/4)] VFIO driver for v3.6

From: Alex Williamson
Date: Mon Jul 30 2012 - 19:19:07 EST


On Fri, 2012-07-27 at 15:32 +1000, Paul Mackerras wrote:
> On Wed, Jul 25, 2012 at 08:53:06AM -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,
>
> Linus,
>
> Are you thinking of pulling this driver in for 3.6? I would be glad
> to see it go in since we want to use it with KVM on PowerPC. If
> possible we'd like the PowerPC bits for it to go in as well.

I'm pretty anxious to find out as well. Linus, ping, any thoughts on
including this in 3.6? Thanks,

Alex

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/