| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4C04C085.1030107@redhat.com> Date: Tue, 01 Jun 2010 11:10:45 +0300 From: Avi Kivity <avi@...hat.com> To: "Michael S. Tsirkin" <mst@...hat.com> CC: Tom Lyon <pugs@...co.com>, linux-kernel@...r.kernel.org, kvm@...r.kernel.org, chrisw@...s-sol.org, joro@...tes.org, hjk@...utronix.de, gregkh@...e.de, aafabbri@...co.com, scofeldm@...co.com Subject: Re: [PATCH] VFIO driver: Non-privileged user level PCI drivers On 05/31/2010 08:10 PM, Michael S. Tsirkin wrote: > On Mon, May 31, 2010 at 02:50:29PM +0300, Avi Kivity wrote: > >> On 05/30/2010 05:53 PM, Michael S. Tsirkin wrote: >> >>> So what I suggested is failing any kind of access until iommu >>> is assigned. >>> >>> >> So, the kernel driver must be aware of the iommu. In which case it may >> as well program it. >> > It's a kernel driver anyway. Point is that > the *device* driver is better off not programming iommu, > this way we do not need to reprogram it for each device. > The device driver is in userspace. It can't program the iommu. What the patch proposes is that userspace tells vfio about the needed mappings, and vfio programs the iommu. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists