[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49F6CDFC.6000400@redhat.com>
Date: Tue, 28 Apr 2009 12:35:56 +0300
From: Avi Kivity <avi@...hat.com>
To: Gregory Haskins <ghaskins@...ell.com>
CC: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
davidel@...ilserver.org
Subject: Re: [KVM PATCH v2 2/2] kvm: add support for irqfd via eventfd-notification
interface
Gregory Haskins wrote:
>> Sure, the interface remains the same (write 8 bytes), but the
>> implementation can change. For example, we can implement it to work
>> from interrupt context, once we hack the locking appropriately.
>>
>
> I was thinking more along the lines of eventfd_signal(). AIO and vbus
> currently use this interface, as opposed to the more polymorhpic
> f_ops->write().
>
>
But eventfd_signal basically marries us to eventfd.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
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