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

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

Davide Libenzi wrote:
> On Wed, 6 May 2009, Gregory Haskins wrote:
>
>   
>> I think we are ok in this regard (at least in v5) without the callback. 
>> kvm holds irqfd, which holds eventfd.  In a normal situation, we will
>> have eventfd with 2 references.  If userspace closes the eventfd, it
>> will drop 1 of the 2 eventfd file references, but the object should
>> remain intact as long as kvm still holds it as well.  When the kvm-fd is
>> released, we will then decouple from the eventfd->wqh and drop the last
>> fput(), officially freeing it.
>>
>> Likewise, if kvm is closed before the eventfd, we will simply decouple
>> from the wqh and fput(eventfd), leaving the last reference held by
>> userspace until it closes as well.
>>
>> Let me know if you see any holes in that.
>>     
>
> Looks OK, modulo my knowledge of KVM internals.
>   

Thanks Davide,

If there isn't any more feedback on the series from Al, Avi,
etc...please formally submit your eventfd patch so this series is
available for Avi to pull in for inclusion when/if he deems it fit.

Thanks again,
-Greg



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

  reply	other threads:[~2009-05-07  2:06 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 [this message]
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
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=4A024214.9090002@novell.com \
    --to=ghaskins@novell.com \
    --cc=avi@redhat.com \
    --cc=davidel@xmailserver.org \
    --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