| 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
| ||
|
Date: Tue, 6 Oct 2015 17:56:07 +0300 From: "Michael S. Tsirkin" <mst@...hat.com> To: Vlad Zolotarov <vladz@...udius-systems.com> Cc: Avi Kivity <avi@...lladb.com>, Greg KH <gregkh@...uxfoundation.org>, linux-kernel@...r.kernel.org, hjk@...sjkoch.de, corbet@....net, bruce.richardson@...el.com, avi@...udius-systems.com, gleb@...udius-systems.com, stephen@...workplumber.org, alexander.duyck@...il.com Subject: Re: [PATCH v3 2/3] uio_pci_generic: add MSI/MSI-X support On Tue, Oct 06, 2015 at 05:43:50PM +0300, Vlad Zolotarov wrote: > The only "like VFIO" behavior we implement here is binding the MSI-X > interrupt notification to eventfd descriptor. There will be more if you add some basic memory protections. Besides, that's not true. Your patch queries MSI capability, sets # of vectors. You even hinted you want to add BAR mapping down the road. VFIO does all of that. > This doesn't justifies the > hassle of implementing IOMMU-less VFIO mode. This applies to both VFIO and UIO really. I'm not sure the hassle of maintaining this functionality in tree is justified. It remains to be seen whether there are any users that won't taint the kernel. Apparently not in the current form of the patch, but who knows. -- MST -- 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