kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Rutherford <srutherford@google.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH v5 3/4] KVM: x86: Add EOI exit bitmap inference
Date: Wed, 29 Jul 2015 23:27:48 -0700	[thread overview]
Message-ID: <20150730062748.GA19303@google.com> (raw)
In-Reply-To: <55B9C2EF.7020603@siemens.com>

On Thu, Jul 30, 2015 at 08:23:43AM +0200, Jan Kiszka wrote:
> On 2015-07-29 22:27, Steve Rutherford wrote:
> > On Wed, Jul 29, 2015 at 02:38:09PM +0200, Paolo Bonzini wrote:
> >>
> >>
> >> On 28/07/2015 01:17, Steve Rutherford wrote:
> >>> diff --git a/arch/x86/kvm/ioapic.h b/arch/x86/kvm/ioapic.h
> >>> index d8cc54b..f6ce112 100644
> >>> --- a/arch/x86/kvm/ioapic.h
> >>> +++ b/arch/x86/kvm/ioapic.h
> >>> @@ -9,6 +9,7 @@ struct kvm;
> >>>  struct kvm_vcpu;
> >>>  
> >>>  #define IOAPIC_NUM_PINS  KVM_IOAPIC_NUM_PINS
> >>> +#define MAX_NR_RESERVED_IOAPIC_PINS 48
> >>
> >> Why is this needed?
> > This constant is used to bound the number of IOAPIC pins that are
> > reservable when enabling KVM_CAP_SPLIT_IRQCHIP. IIRC, x86 doesn't
> > support more than 2 IOAPICs.  
> 
> Huh? Surely not. I've already seen boxes with at least three, and I
> think you can even hot-plug them today via extension cards. Not saying
> that QEMU supports that already, even without KVM, but we must not limit
> ourselves in the kernel API.
> 
> So please remove such a static limit on how many IOAPICs userspace can
> emulate or raise it to something sufficiently large that will last long
> enough.
I'll go with the latter. I'll set it to the same size as the max size of the
GSI routing table, which needs to upper bound it.

> 
> Jan
> 
> -- 
> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
> Corporate Competence Center Embedded Linux

  reply	other threads:[~2015-07-30  6:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 23:17 [PATCH v5 1/4] KVM: x86: Split the APIC from the rest of IRQCHIP Steve Rutherford
2015-07-27 23:17 ` [PATCH v5 2/4] KVM: x86: Add KVM exit for IOAPIC EOIs Steve Rutherford
2015-07-27 23:17 ` [PATCH v5 3/4] KVM: x86: Add EOI exit bitmap inference Steve Rutherford
2015-07-29 12:38   ` Paolo Bonzini
2015-07-29 20:27     ` Steve Rutherford
2015-07-30  6:23       ` Jan Kiszka
2015-07-30  6:27         ` Steve Rutherford [this message]
2015-07-27 23:17 ` [PATCH v5 4/4] KVM: x86: Add support for local interrupt requests from userspace Steve Rutherford
2015-07-28 15:58   ` Paolo Bonzini
2015-07-28 19:06     ` Steve Rutherford
2015-07-28 22:05       ` Paolo Bonzini
2015-07-29  0:50         ` Steve Rutherford
2015-07-29 10:21       ` Paolo Bonzini
2015-07-29 10:15   ` Paolo Bonzini
2015-07-29 12:56 ` [PATCH v5 1/4] KVM: x86: Split the APIC from the rest of IRQCHIP Paolo Bonzini
2015-07-30  3:04   ` Steve Rutherford

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=20150730062748.GA19303@google.com \
    --to=srutherford@google.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@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;
as well as URLs for NNTP newsgroup(s).