From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Steve Rutherford <srutherford@google.com>,
kvm@vger.kernel.org
Cc: ahonig@google.com
Subject: Re: [RFC PATCH 3/4] KVM: x86: Add EOI exit bitmap inference
Date: Wed, 13 May 2015 11:24:19 +0200 [thread overview]
Message-ID: <55531843.9090304@redhat.com> (raw)
In-Reply-To: <55530702.5000407@siemens.com>
On 13/05/2015 10:10, Jan Kiszka wrote:
>>> >> There can even be multiple IOAPICs (thanks to your patches overcoming
>>> >> the single in-kernel instance).
>> >
>> > With multiple IOAPICs you have more than 24 GSIs per IOAPIC. That means
> I don't think that the number of pins per IOAPIC increases. At least not
> in the devices I've seen so far.
Sorry, that was supposed to be "more than 24 GSIs for the IOAPICs".
>> > that the above loop is broken for multiple IOAPICs.
> The worst case remains #IOAPIC * 24 iterations - if we have means to
> stop after the IOAPIC entries, not iterating over all routes.
Yes. Which is not too bad if VCPUs can process it in parallel.
>> > But perhaps when enabling KVM_SPLIT_IRQCHIP we can use args[0] to pass
>> > the number of IOAPIC routes that will cause EOI exits?
> And you need to ensure that their routes can be found in the table
> directly. Given IOAPIC hotplug, that may not be the first ones there...
Can you reserve a bunch of GSIs at the beginning of the GSI space, and
use rt->map[] to access them and build the EOI exit bitmap?
Paolo
next prev parent reply other threads:[~2015-05-13 9:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 1:47 [RFC PATCH 1/4] KVM: x86: Split the APIC from the rest of IRQCHIP Steve Rutherford
2015-05-13 1:47 ` [RFC PATCH 2/4] KVM: x86: Add KVM exit for IOAPIC EOIs Steve Rutherford
2015-05-13 7:35 ` Paolo Bonzini
2015-05-13 22:18 ` Steve Rutherford
2015-05-24 16:46 ` Avi Kivity
2015-05-27 2:06 ` Steve Rutherford
2015-05-27 5:32 ` Avi Kivity
2015-05-28 21:58 ` Steve Rutherford
2015-05-13 1:47 ` [RFC PATCH 3/4] KVM: x86: Add EOI exit bitmap inference Steve Rutherford
2015-05-13 6:12 ` Jan Kiszka
2015-05-13 8:04 ` Paolo Bonzini
2015-05-13 8:10 ` Jan Kiszka
2015-05-13 9:24 ` Paolo Bonzini [this message]
2015-05-13 10:25 ` Jan Kiszka
2015-05-13 13:04 ` Paolo Bonzini
2015-05-13 13:19 ` Jan Kiszka
2015-05-13 22:21 ` Steve Rutherford
2015-05-15 2:38 ` Steve Rutherford
2015-05-13 7:51 ` Paolo Bonzini
2015-05-13 22:24 ` Steve Rutherford
2015-05-14 9:20 ` Paolo Bonzini
2015-05-14 15:23 ` Alex Williamson
2015-05-14 15:46 ` Paolo Bonzini
2015-05-14 16:04 ` Alex Williamson
2015-05-14 22:10 ` Steve Rutherford
2015-05-14 22:35 ` Alex Williamson
2015-05-14 23:21 ` Steve Rutherford
2015-05-13 1:47 ` [RFC PATCH 4/4] KVM: x86: Add support for local interrupt requests from userspace Steve Rutherford
2015-05-13 6:12 ` Jan Kiszka
2015-05-13 22:41 ` Steve Rutherford
2015-05-15 13:27 ` Jan Kiszka
2015-05-13 7:22 ` Paolo Bonzini
2015-05-13 23:13 ` Steve Rutherford
2015-05-13 7:57 ` [RFC PATCH 1/4] KVM: x86: Split the APIC from the rest of IRQCHIP Paolo Bonzini
2015-05-13 22:10 ` Steve Rutherford
2015-05-14 9:12 ` Wu, Feng
2015-05-14 19:29 ` Andrew Honig
2015-05-15 1:28 ` Wu, Feng
2015-05-15 5:03 ` Wanpeng Li
2015-05-15 18:10 ` Steve Rutherford
2015-05-18 2:11 ` Wanpeng Li
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=55531843.9090304@redhat.com \
--to=pbonzini@redhat.com \
--cc=ahonig@google.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=srutherford@google.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;
as well as URLs for NNTP newsgroup(s).