From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gregory Haskins <ghaskins@novell.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
davidel@xmailserver.org, mtosatti@redhat.com
Subject: Re: [KVM PATCH v10] kvm: add support for irqfd
Date: Sun, 14 Jun 2009 16:30:35 +0300 [thread overview]
Message-ID: <20090614133035.GD10646@redhat.com> (raw)
In-Reply-To: <4A34F9D8.5040306@redhat.com>
On Sun, Jun 14, 2009 at 04:23:36PM +0300, Avi Kivity wrote:
> Michael S. Tsirkin wrote:
>
>
>
>>> I think Avi asked for this specific feature during review which is the
>>> reason why its there today. However, I agree that it would probably be
>>> a good idea to put an upper limit on the number of supported aliases
>>> that can be registered. Will fix.
>>>
>>> Thanks Michael,
>>>
>>> -Greg
>>>
>>>
>>>
>>
>>
>> Avi, can you elaborate on why do we want to map multiple fds
>> to the same gsi? I think it's better to allow a 1:1 mapping
>> only: if many processes want to trigger interrupts they can
>> all write to the same fd.
>>
>
> I don't want to assume that the eventfds all come from the same source.
>
> That said, we have a workaround, allocate a new gsi with the same routes
> and attach the excess eventfds there.
Right. So you are ok with 1:1 irqfd:gsi requirement for now?
This seems nicer than N:1 with an arbitrary N.
--
MST
next prev parent reply other threads:[~2009-06-14 13:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 14:30 [KVM PATCH v10] kvm: add support for irqfd Gregory Haskins
2009-05-20 14:35 ` Avi Kivity
2009-05-26 16:42 ` Michael S. Tsirkin
2009-05-26 18:05 ` Gregory Haskins
2009-05-26 20:00 ` Davide Libenzi
2009-05-27 13:55 ` Michael S. Tsirkin
2009-05-27 14:06 ` Gregory Haskins
2009-05-27 14:36 ` [PATCH 0/2] kvm: validate irqfd type Gregory Haskins
2009-05-27 14:37 ` [PATCH 1/2] eventfd: export eventfd interfaces for module use Gregory Haskins
2009-05-27 14:37 ` [PATCH 2/2] kvm: validate irqfd type Gregory Haskins
2009-05-27 15:06 ` [PATCH 0/2] " Gregory Haskins
2009-05-31 9:36 ` Avi Kivity
2009-05-27 18:41 ` [KVM PATCH v10] kvm: add support for irqfd Michael S. Tsirkin
2009-05-27 19:28 ` Davide Libenzi
2009-05-27 20:07 ` Gregory Haskins
2009-05-27 20:43 ` Michael S. Tsirkin
2009-05-27 20:46 ` Gregory Haskins
2009-06-11 13:16 ` Michael S. Tsirkin
2009-06-11 13:36 ` Michael S. Tsirkin
2009-06-14 12:25 ` Gregory Haskins
2009-06-14 13:20 ` Michael S. Tsirkin
2009-06-14 9:25 ` Michael S. Tsirkin
2009-06-14 12:40 ` Gregory Haskins
2009-06-14 13:19 ` Michael S. Tsirkin
2009-06-14 13:23 ` Avi Kivity
2009-06-14 13:30 ` Michael S. Tsirkin [this message]
2009-06-14 13:40 ` Avi Kivity
2009-06-14 13:50 ` Michael S. Tsirkin
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=20090614133035.GD10646@redhat.com \
--to=mst@redhat.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=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