From: Avi Kivity <avi@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
gleb@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 2/2] kvm: Add resampling irqfds for level triggered interrupts
Date: Wed, 19 Sep 2012 17:35:34 +0300 [thread overview]
Message-ID: <5059D836.8020205@redhat.com> (raw)
In-Reply-To: <1348062872.28860.24.camel@bling.home>
On 09/19/2012 04:54 PM, Alex Williamson wrote:
> On Wed, 2012-09-19 at 12:10 +0300, Avi Kivity wrote:
>> On 09/19/2012 12:08 PM, Michael S. Tsirkin wrote:
>>
>> >> Whoa. Can't we put the resampler entry somewhere we don't need to
>> >> search for it? Like a kvm_kernel_irq_routing_entry, that's indexed by
>> >> gsi already (kvm_irq_routing_table::rt_entries[gsi]).
>> >
>> > I'm not sure why would we bother optimizing this,
>>
>> Not optimizing, simplifying.
>>
>> > but if we do, I guess we could look for the irq notifier
>> > which is already indexed by gsi.
>>
>> It's not, it's looked up in a list.
>
> I'm not sure it's a simplification because to index by gsi we suddenly
> need to care how many gsis there are. I believe that currently means we
> have to assume an ioapic. Creating a dumb list is a little bit of
> overhead, but we get to stay blissfully unaware of the gsi
> implementation. Practically we're looking at a list of 4 entries, maybe
> a few times that when we expose more PCI root bridges to the guest.
Ok. I tried to see if it would fit in the routing table, but rcu means
that we'll need to have the resampler as a pointer, not a field, and
that we'll need to migrate it to the new array when rebuilt. So it ends
up not being any simpler.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-19 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 3:16 [PATCH v10 0/2] kvm: level irqfd support Alex Williamson
2012-09-18 3:16 ` [PATCH v10 1/2] kvm: Provide pre-locked setup to irq ack notifier Alex Williamson
2012-09-18 3:16 ` [PATCH v10 2/2] kvm: Add resampling irqfds for level triggered interrupts Alex Williamson
2012-09-18 23:29 ` Michael S. Tsirkin
2012-09-19 8:59 ` Avi Kivity
2012-09-19 9:08 ` Michael S. Tsirkin
2012-09-19 9:10 ` Avi Kivity
2012-09-19 13:54 ` Alex Williamson
2012-09-19 14:35 ` Avi Kivity [this message]
2012-09-19 18:23 ` Alex Williamson
2012-09-19 18:48 ` Michael S. Tsirkin
2012-09-19 19:23 ` Alex Williamson
2012-09-19 19:59 ` 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=5059D836.8020205@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@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 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.