| 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: Wed, 11 Jul 2012 12:53:14 +0300 From: Avi Kivity <avi@...hat.com> To: Alex Williamson <alex.williamson@...hat.com> CC: mst@...hat.com, gleb@...hat.com, kvm@...r.kernel.org, linux-kernel@...r.kernel.org, jan.kiszka@...mens.com Subject: Re: [PATCH v3 0/2] kvm: level irqfd and new eoifd On 07/03/2012 10:21 PM, Alex Williamson wrote: > Here's the latest iteration of adding an interface to assert and > de-assert level interrupts from external drivers like vfio. These > apply on top of the previous argument cleanup, documentation, and > sanitization patches for irqfd. It would be great to get this queued > in next for linux 3.6. > > I believe I've addressed all the previous comments, including fixing > the locking problems in eoifd. I've run this with lockdep adding > and removing level irqfd/eoifd pairs without any problems. Please > let me know if there are any further comments. Thanks, Is there any performance justification for level irqfd? Don't all new/high bandwidth devices support msi, and this is just a legacy path? eoifd does add new functionality (which parallels the existing ack notifier usage in kvm device assignment); it's not just an optimization. -- 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