| 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: <49E379FE.8060202@novell.com> Date: Mon, 13 Apr 2009 13:44:30 -0400 From: Gregory Haskins <ghaskins@...ell.com> To: Avi Kivity <avi@...hat.com> CC: linux-kernel@...r.kernel.org, agraf@...e.de, pmullaney@...ell.com, pmorreale@...ell.com, anthony@...emonkey.ws, rusty@...tcorp.com.au, netdev@...r.kernel.org, kvm@...r.kernel.org, bhutchings@...arflare.com, andi@...stfloor.org, gregkh@...e.de, herber@...dor.apana.org.au, chrisw@...s-sol.org, shemminger@...tta.com Subject: Re: [RFC PATCH v2 15/19] kvm: add dynamic IRQ support Avi Kivity wrote: >> > > Given that you're using the apic to inject the IRQ, you'll need an > EOI. So what's the difference between dynirq and MSI, performance wise? > I would have loved to eliminate that EOI completely, but that is a much broader problem to solve ;) Actually dynirq wasnt introduced as a performance alternative over MSI. Rather, I was trying to eliminate the complexity of needing to sync between the userspace PCI emulation and the in kernel models. However, its moot. Since v2 introduce virtio-vbus, I now have a much clearer picture of what is needed here, and v3 will simply integrate with MSI interrupts and drop dynirq completely. So please ignore this patch. -Greg -- 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