From: Gregory Haskins <gregory.haskins@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gregory Haskins <ghaskins@novell.com>,
kvm@vger.kernel.org, viro@ZenIV.linux.org.uk,
linux-kernel@vger.kernel.org, davidel@xmailserver.org
Subject: Re: [KVM PATCH v7 2/3] kvm: add support for irqfd via eventfd-notification interface
Date: Thu, 14 May 2009 09:12:51 -0400 [thread overview]
Message-ID: <4A0C18D3.6060905@gmail.com> (raw)
In-Reply-To: <4A0C0C96.6050600@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Avi Kivity wrote:
> Gregory Haskins wrote:
>>> Please fget() the new fd and compare the filps; fds aren't meaningful
>>> in the kernel. You can also drop _irqfd::fd.
>>>
>>
>> I like this as a second option...
>>
>>
>>> It may also be useful to compare the gsi, this allows a
>>> "make-before-break" switchover:
>>>
>>
>> ...but I like this best. Good idea.
>>
>
> I thought of comparing both.
Ah, ok. I misunderstood. We can do that.
>
>>> - guest reroutes irq to a different gsi
>>> - associate irqfd with new gsi
>>> - disassociate irqfd from old gsi
>>>
>>>
>>>> +
>>>> + irqfd_release(irqfd);
>>>> + mutex_unlock(&kvm->lock);
>>>> + return 0;
>>>>
>>> Don't return, userspace may have multiple associations?
>>>
>>
>> Parse error. Can you elaborate?
>>
>>
>
> You break out of the look when you match your irqfd. But there may be
> multiple matches.
>
> Granted, it doesn't make much sense to hook the same fd to the same
> gsi multiple times (it may make sense to hook multiple fds to a single
> gsi, or maybe a single fd to multiple gsis), but it pays to have a
> consistent do-what-I-said-even-if-it-doesn't-make-sense interface.
Ack, will do.
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]
next prev parent reply other threads:[~2009-05-14 13:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 18:26 [KVM PATCH v7 0/3] kvm: eventfd interfaces (formerly irqfd) Gregory Haskins
2009-05-12 18:26 ` [KVM PATCH v7 1/3] eventfd: export eventfd interfaces for module use Gregory Haskins
2009-05-12 19:02 ` Davide Libenzi
2009-05-12 18:26 ` [KVM PATCH v7 2/3] kvm: add support for irqfd via eventfd-notification interface Gregory Haskins
2009-05-14 9:47 ` Avi Kivity
2009-05-14 11:52 ` Gregory Haskins
2009-05-14 12:20 ` Avi Kivity
2009-05-14 13:12 ` Gregory Haskins [this message]
2009-05-14 11:22 ` Avi Kivity
2009-05-14 15:52 ` Gregory Haskins
2009-05-15 3:22 ` Davide Libenzi
2009-05-15 3:35 ` Gregory Haskins
2009-05-12 18:27 ` [KVM PATCH v7 3/3] kvm: add iofd support Gregory Haskins
2009-05-12 19:05 ` Gregory Haskins
2009-05-12 19:29 ` [KVM PATCH v7.1] " Gregory Haskins
2009-05-12 22:17 ` [KVM PATCH v7.2] " Gregory Haskins
2009-05-13 2:46 ` Gregory Haskins
2009-05-14 11:11 ` [KVM PATCH v7 3/3] " Avi Kivity
2009-05-14 12:02 ` Gregory Haskins
2009-05-14 12:22 ` 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=4A0C18D3.6060905@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=avi@redhat.com \
--cc=davidel@xmailserver.org \
--cc=ghaskins@novell.com \
--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