[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A03EB00.2070203@redhat.com>
Date: Fri, 08 May 2009 11:19:12 +0300
From: Avi Kivity <avi@...hat.com>
To: Davide Libenzi <davidel@...ilserver.org>
CC: Gregory Haskins <ghaskins@...ell.com>, viro@...IV.linux.org.uk,
kvm@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [KVM PATCH v4 2/2] kvm: add support for irqfd via eventfd-notification
interface
Davide Libenzi wrote:
> On Thu, 7 May 2009, Avi Kivity wrote:
>
>
>> What's your take on adding irq context safe callbacks to irqfd?
>>
>> To give some background here, we would like to use eventfd as a generic
>> connector between components, so the components do not know about each other.
>> So far eventfd successfully abstracts among components in the same process, in
>> different processes, and in the kernel.
>>
>> eventfd_signal() can be safely called from irq context, and will wake up a
>> waiting task. But in some cases, if the consumer is in the kernel, it may be
>> able to consume the event from irq context, saving a context switch.
>>
>> So, will you consider patches adding this capability to eventfd?
>>
>
> Since I received this one after your ACK on the capability of eventfd of
> triggering callbacks, I assume we're clear on this point, aren't we?
>
We are.
--
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