From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
davidel@xmailserver.org
Subject: Re: [KVM PATCH v2 2/2] kvm: add support for irqfd via eventfd-notification interface
Date: Tue, 28 Apr 2009 12:35:56 +0300 [thread overview]
Message-ID: <49F6CDFC.6000400@redhat.com> (raw)
In-Reply-To: <49F5B2DA.5060207@novell.com>
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.
next prev parent reply other threads:[~2009-04-28 9:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 4:25 [KVM PATCH v2 0/2] irqfd Gregory Haskins
2009-04-24 4:25 ` [KVM PATCH v2 1/2] eventfd: export fget and signal interfaces for module use Gregory Haskins
2009-04-24 4:25 ` [KVM PATCH v2 2/2] kvm: add support for irqfd via eventfd-notification interface Gregory Haskins
2009-04-24 17:07 ` Gregory Haskins
2009-04-24 17:47 ` Davide Libenzi
2009-04-27 8:55 ` Avi Kivity
2009-04-27 10:35 ` Gregory Haskins
2009-04-27 10:48 ` Avi Kivity
2009-04-27 13:27 ` Gregory Haskins
2009-04-28 9:35 ` Avi Kivity [this message]
2009-04-28 10:34 ` Gregory Haskins
2009-04-28 11:00 ` Avi Kivity
2009-04-28 11:04 ` Gregory Haskins
2009-04-28 11:05 ` Avi Kivity
2009-04-28 11:08 ` Avi Kivity
2009-04-28 11:38 ` Gregory Haskins
2009-04-28 11:48 ` Avi Kivity
2009-04-28 12:07 ` Gregory Haskins
2009-04-27 10:58 ` Gregory Haskins
2009-04-27 11:23 ` Avi Kivity
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=49F6CDFC.6000400@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 \
/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