[lkml]   [2009]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [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

 \ /
  Last update: 2009-10-22 17:11    [W:0.066 / U:3.056 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site