[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A9585EC.2030505@redhat.com>
Date: Wed, 26 Aug 2009 21:58:52 +0300
From: Avi Kivity <avi@...hat.com>
To: Davide Libenzi <davidel@...ilserver.org>
CC: "Michael S. Tsirkin" <mst@...hat.com>, gleb@...hat.com,
kvm@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] eventfd: new EFD_STATE flag
On 08/26/2009 08:45 PM, Davide Libenzi wrote:
> OK, if I get it correctly, there is one eventfd signaler (the device), and
> one eventfd reader (the hypervisor), right?
> Each hypervisor listens for multiple devices detecting state changes, and
> associating the eventfd "line" to the IRQ number by some configuration
> (ala PCI), right?
>
Yes. The PCI stuff happens in userspace, all the hypervisor sees is
"this eventfd is IRQ 10". There may be multiple eventfds routed to one
IRQ (corresponding to a shared IRQ line).
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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