public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: Avi Kivity <avi@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	kvm@vger.kernel.org, mtosatti@redhat.com,
	Davide Libenzi <davidel@xmailserver.org>
Subject: Re: [PATCH 0/3] RFC: virtual device as irq injection interface
Date: Mon, 01 Jun 2009 08:14:34 -0400	[thread overview]
Message-ID: <4A23C62A.9000801@novell.com> (raw)
In-Reply-To: <4A23C3CD.7060601@redhat.com>

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

Avi Kivity wrote:
> Gregory Haskins wrote:
>> A potential compromise is to investigate the POLLHUP technique that
>> Davide mentioned so that kvmfd can get notified of the closure without
>> needing an additional explicit ioctl to do it.  Note that we already
>> have irqfd in the tree so I assume we would need to do this in a ABI
>> friendly way, but its possible.
>>   
>
> We don't have irqfd in any released tree.  I'm only submitting it for
> 2.6.32 (exactly so we can iron these things out), so we can change it
> any way we like or even pull it out completely.
>
> The POLLHUP stuff is something I'd like to see in.
>
Ah, perfect.  I will submit a patch to implement this, then.

Thanks,
-Greg


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

      reply	other threads:[~2009-06-01 12:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-31 18:58 [PATCH 0/3] RFC: virtual device as irq injection interface Michael S. Tsirkin
2009-05-31 19:40 ` Avi Kivity
2009-05-31 20:10   ` Michael S. Tsirkin
2009-05-31 20:30     ` Avi Kivity
2009-06-01  4:18       ` Michael S. Tsirkin
2009-06-01  7:45         ` Avi Kivity
2009-06-01 12:00         ` Gregory Haskins
2009-06-01 12:04           ` Avi Kivity
2009-06-01 12:14             ` Gregory Haskins [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=4A23C62A.9000801@novell.com \
    --to=ghaskins@novell.com \
    --cc=avi@redhat.com \
    --cc=davidel@xmailserver.org \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox