All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <gregory.haskins@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Gregory Haskins <ghaskins@novell.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	davidel@xmailserver.org, paulmck@linux.vnet.ibm.com,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [KVM-RFC PATCH 0/2] irqfd: use POLLHUP notification for close()
Date: Thu, 04 Jun 2009 07:52:55 -0400	[thread overview]
Message-ID: <4A27B597.7090003@gmail.com> (raw)
In-Reply-To: <4A27B4F0.9060603@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

Avi Kivity wrote:
> Gregory Haskins wrote:
>>> I agree that deassign is needed for reasons of symmetry, and that it
>>> can be added later.
>>>
>>>     
>> Cool.
>>
>> FYI: Davide's patch has been accepted into -mm (Andrew CC'd).  I am not
>> sure of the protocol here, but I assume this means you can now safely
>> pull it from -mm into kvm.git so the prerequisite for 2/2 is properly
>> met.
>>   
>
> I'm not sure either.
>
> But I think I saw a "Thanks for catching that" for 2/2?
>
Ah, right!  I queued that fix up eons ago after David's feedback and
forgot that it was there waiting for me ;)

Since Paul ok'd (I think?) the srcu design, and the only other feedback
was the key-bitmap thing from Davide, I will go ahead and push a v2 with
just that one fix (unless there is any other feedback?)

-Greg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]

  reply	other threads:[~2009-06-04 11:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 15:15 [KVM-RFC PATCH 0/2] irqfd: use POLLHUP notification for close() Gregory Haskins
2009-06-02 15:15 ` [KVM-RFC PATCH 1/2] eventfd: send POLLHUP on f_ops->release Gregory Haskins
2009-06-02 15:15 ` [KVM-RFC PATCH 2/2] kvm: use POLLHUP to close an irqfd instead of an explicit ioctl Gregory Haskins
2009-06-02 17:16   ` Davide Libenzi
2009-06-02 17:42     ` Gregory Haskins
2009-06-02 18:02   ` Paul E. McKenney
2009-06-02 18:23     ` Gregory Haskins
2009-06-02 22:01       ` Paul E. McKenney
2009-06-03  1:53         ` Gregory Haskins
2009-06-03 15:04           ` Paul E. McKenney
2009-06-03 17:27             ` Gregory Haskins
2009-06-03 17:24               ` Davide Libenzi
2009-06-02 16:04 ` [KVM-RFC PATCH 0/2] irqfd: use POLLHUP notification for close() Michael S. Tsirkin
2009-06-02 16:14   ` Gregory Haskins
2009-06-02 16:20     ` Michael S. Tsirkin
2009-06-02 16:34       ` Gregory Haskins
2009-06-02 16:59         ` Michael S. Tsirkin
2009-06-02 17:02           ` Michael S. Tsirkin
2009-06-02 17:41           ` Gregory Haskins
2009-06-03  6:39             ` Michael S. Tsirkin
2009-06-03 11:34               ` Gregory Haskins
2009-06-04 10:25               ` Avi Kivity
2009-06-04 11:43                 ` Gregory Haskins
2009-06-04 11:50                   ` Avi Kivity
2009-06-04 11:52                     ` Gregory Haskins [this message]
2009-06-04 12:02                       ` 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=4A27B597.7090003@gmail.com \
    --to=gregory.haskins@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=davidel@xmailserver.org \
    --cc=ghaskins@novell.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.