From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH V2] VFIO driver: Non-privileged user level PCI drivers Date: Wed, 09 Jun 2010 14:04:53 +0300 Message-ID: <4C0F7555.6050802@redhat.com> References: <4c0eb470.1HMjondO00NIvFM6%pugs@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: randy.dunlap@oracle.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, chrisw@sous-sol.org, joro@8bytes.org, hjk@linutronix.de, mst@redhat.com, gregkh@suse.de, aafabbri@cisco.com, scofeldm@cisco.com To: Tom Lyon Return-path: In-Reply-To: <4c0eb470.1HMjondO00NIvFM6%pugs@cisco.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 06/09/2010 12:21 AM, Tom Lyon wrote: > The VFIO "driver" is used to allow privileged AND non-privileged processes to > implement user-level device drivers for any well-behaved PCI, PCI-X, and PCIe > devices. > Signed-off-by: Tom Lyon > --- > This version now requires an IOMMU domain to be set before any access to > device registers is granted (except that config space may be read). In > addition, the VFIO_DMA_MAP_ANYWHERE is dropped - it used the dma_map_sg API > which does not have sufficient controls around IOMMU usage. The IOMMU domain > is obtained from the 'uiommu' driver which is included in this patch. > > Various locking, security, and documentation issues have also been fixed. > > Please commit - it or me! > But seriously, who gets to commit this? Avi for KVM? Definitely not me. > or GregKH for drivers? > I guess. -- error compiling committee.c: too many arguments to function