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, mingo@elte.hu, mst@redhat.com,
paulmck@linux.vnet.ibm.com, rusty@rustcorp.com.au
Subject: Re: [KVM PATCH 0/4] irqfd fixes/enhancements
Date: Sun, 21 Jun 2009 15:56:55 +0300 [thread overview]
Message-ID: <4A3E2E17.4010305@redhat.com> (raw)
In-Reply-To: <20090618173534.24119.95115.stgit@dev.haskins.net>
On 06/18/2009 08:44 PM, Gregory Haskins wrote:
> (Applies to kvm.git/master:c27b64a0)
>
> The following series represents my queue of fixes for issues in irqfd,
> which include enhancements to eventfd. This is a respin of the patches
> originally proposed yesterday, called "[KVM-RFC PATCH 0/2] eventfd
> enhancements for irqfd/iosignalfd", which you can find a link to the thread
> here:
>
> http://www.gossamer-threads.com/lists/linux/kernel/1091852
>
> Aside from introducing a few minor fixes (patches 1/4, 2/4), the general
> solution for module reference counting has been extracted from the
> (controversial) SRCU enhancement. We can address the SRCU topic at a later
> time. For now, fixing the race condition is a higher priority item IMO.
> Hopefully, this more focused series is more palatable for the
> reviewers/maintainers involved.
>
Applied 1-2, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-06-21 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 17:44 [KVM PATCH 0/4] irqfd fixes/enhancements Gregory Haskins
2009-06-18 17:44 ` [KVM PATCH 1/4] KVM: update inaccurate irqfd comment Gregory Haskins
2009-06-18 17:44 ` [KVM PATCH 2/4] KVM: fix irqfd error checking Gregory Haskins
2009-06-18 17:44 ` [KVM PATCH 3/4] eventfd: add generalized notifier interface Gregory Haskins
2009-06-18 17:45 ` Davide Libenzi
2009-06-18 18:46 ` Gregory Haskins
2009-06-18 18:48 ` Gregory Haskins
2009-06-18 17:44 ` [KVM PATCH 4/4] eventfd: add module reference counting support for registered notifiers Gregory Haskins
2009-06-21 12:56 ` Avi Kivity [this message]
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=4A3E2E17.4010305@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=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rusty@rustcorp.com.au \
/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