| 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: <4AE07541.8060903@redhat.com> Date: Thu, 22 Oct 2009 17:07:45 +0200 From: Avi Kivity <avi@...hat.com> To: Gregory Haskins <gregory.haskins@...il.com> CC: Gleb Natapov <gleb@...hat.com>, Gregory Haskins <ghaskins@...ell.com>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org, alacrityvm-devel@...ts.sourceforge.net Subject: Re: [KVM PATCH 1/2] KVM: Directly inject interrupts via irqfd On 10/21/2009 05:42 PM, Gregory Haskins wrote: > I believe Avi, Michael, et. al. were in agreement with me on that design > choice. I believe the reason is that there is no good way to do EOI/ACK > feedback within the constraints of an eventfd pipe which would be > required for the legacy pin-type interrupts. Therefore, we won't even > bother trying. High-performance subsystems will use irqfd/msi, and > legacy emulation can use the existing injection code (which includes the > necessary feedback for ack/eoi). > > Right. But we don't actually prevent anyone using non-msi with irqfd, which can trigger the bad lock usage from irq context, with a nice boom afterwards. So we need to either prevent it during registration, or to gracefully handle it afterwards. -- 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