From: Paolo Bonzini <pbonzini@redhat.com>
To: Steve Rutherford <srutherford@google.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v7 1/4] KVM: x86: Split the APIC from the rest of IRQCHIP.
Date: Thu, 30 Jul 2015 11:38:20 +0200 [thread overview]
Message-ID: <55B9F08C.6080604@redhat.com> (raw)
In-Reply-To: <20150730083739.GB19524@google.com>
On 30/07/2015 10:37, Steve Rutherford wrote:
> This looks a bit non-sensical, but is overprepared for the introduction
> IOAPIC hotplug, which two patches down the line. Changing it is fine,
> you'll just need to merge the very same change back.
By "IOAPIC hotplug" you mean changing the number of reserved routes? Is
it necessary? You could just reserve a bunch of routes depending on the
maximum number of IOAPICs.
And especially, is it documented? :) The docs say "Fails [...] if the
irqchip is already in the kernel (i.e. KVM_CREATE_IRQCHIP has already
been called)".
As before, no need to resend patches for now. Let's finish discussing
all pending points, then I'll push what I have to kvm.git and you can
test it with your VMM. There should be time between this week and the next.
Paolo
next prev parent reply other threads:[~2015-07-30 9:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 6:21 [PATCH v7 1/4] KVM: x86: Split the APIC from the rest of IRQCHIP Steve Rutherford
2015-07-30 6:21 ` [PATCH v7 2/4] KVM: x86: Add KVM exit for IOAPIC EOIs Steve Rutherford
2015-07-30 6:21 ` [PATCH v7 3/4] KVM: x86: Add EOI exit bitmap inference Steve Rutherford
2015-07-30 6:21 ` [PATCH v7 4/4] KVM: x86: Add support for local interrupt requests from userspace Steve Rutherford
2015-07-30 8:21 ` Paolo Bonzini
2015-07-30 9:33 ` Paolo Bonzini
2015-07-30 8:21 ` [PATCH v7 1/4] KVM: x86: Split the APIC from the rest of IRQCHIP Paolo Bonzini
2015-07-30 8:37 ` Steve Rutherford
2015-07-30 9:38 ` Paolo Bonzini [this message]
2015-07-30 21:19 ` Steve Rutherford
2015-07-31 8:32 ` Jan Kiszka
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=55B9F08C.6080604@redhat.com \
--to=pbonzini@redhat.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 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.