public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Gregory Haskins <ghaskins@novell.com>,
	viro@ZenIV.linux.org.uk, kvm@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [KVM PATCH v4 2/2] kvm: add support for irqfd via eventfd-notification interface
Date: Fri, 08 May 2009 11:19:12 +0300	[thread overview]
Message-ID: <4A03EB00.2070203@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0905072012460.31280@makko.or.mcafeemobile.com>

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.


  reply	other threads:[~2009-05-08  8:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 17:57 [KVM PATCH v4 0/2] irqfd Gregory Haskins
2009-05-04 17:57 ` [KVM PATCH v4 1/2] eventfd: export eventfd interfaces for module use Gregory Haskins
2009-05-04 22:24   ` Al Viro
2009-05-05  2:17     ` Gregory Haskins
2009-05-04 17:57 ` [KVM PATCH v4 2/2] kvm: add support for irqfd via eventfd-notification interface Gregory Haskins
2009-05-05 15:45   ` Avi Kivity
2009-05-05 17:34     ` Gregory Haskins
2009-05-05 17:43       ` Avi Kivity
2009-05-05 17:56     ` Gregory Haskins
2009-05-05 18:10       ` Avi Kivity
2009-05-05 18:21         ` Gregory Haskins
2009-05-06 11:35   ` Gregory Haskins
2009-05-06 15:24     ` Davide Libenzi
2009-05-06 15:37       ` Gregory Haskins
2009-05-07  1:34         ` Davide Libenzi
2009-05-07  2:06           ` Gregory Haskins
2009-05-08 15:06             ` Davide Libenzi
2009-05-12  3:55               ` Gregory Haskins
2009-05-12  6:55                 ` Davide Libenzi
2009-05-07  9:48           ` Avi Kivity
2009-05-07 13:46             ` Marcelo Tosatti
2009-05-07 14:01               ` Gregory Haskins
2009-05-07 14:34                 ` Avi Kivity
2009-05-07 14:54                   ` Gregory Haskins
2009-05-07 15:26                     ` Avi Kivity
2009-05-07 14:46             ` Davide Libenzi
2009-05-07 15:47               ` Avi Kivity
2009-05-07 16:44                 ` Davide Libenzi
2009-05-07 18:12                   ` Avi Kivity
2009-05-08  3:13             ` Davide Libenzi
2009-05-08  8:19               ` Avi Kivity [this message]
2009-05-04 18:06 ` [KVM PATCH v4 0/2] irqfd Gregory Haskins
2009-05-04 18:52 ` Gregory Haskins
2009-05-05 14:16 ` Davide Libenzi
2009-05-05 14:27   ` Gregory Haskins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A03EB00.2070203@redhat.com \
    --to=avi@redhat.com \
    --cc=davidel@xmailserver.org \
    --cc=ghaskins@novell.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox