From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [kvmarm] [RFC PATCH 0/3] KVM: ARM: Get rid of hardcoded VGIC
 addresses
Date: Fri, 26 Oct 2012 11:58:59 +0200
Message-ID: <508A5EE3.6070709@redhat.com>
References: <1350173065-35350-1-git-send-email-c.dall@virtualopensystems.com>  <507F172D.2030802@suse.de>  <CANM98q+gfcp86zVV0B1t2aOKTftFegs6dk-+DNc-78LijueOiw@mail.gmail.com>  <20121017221022.GA4333@bloggs.ozlabs.ibm.com>  <1350518331.4678.114.camel@pasglop>  <CANM98q+4diN7_xBtyo6AesDP=AVzj0xQ99vtgBNa=sxLifOzow@mail.gmail.com>  <508675FC.7090901@siemens.com>  <20121024005017.GA17834@bloggs.ozlabs.ibm.com>  <5089656A.9010704@redhat.com> <5089699D.3050004@siemens.com>  <50898479.8060402@redhat.com> <1351194021.2728.170.camel@pasglop>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Paul Mackerras <paulus@samba.org>,
	Christoffer Dall <c.dall@virtualopensystems.com>,
	Alexander Graf <agraf@suse.de>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	kvm-ppc <kvm-ppc@vger.kernel.org>,
	Peter Maydell <peter.maydell@linaro.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-bk0-f46.google.com ([209.85.214.46]:58734 "EHLO
	mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752161Ab2JZJ7E (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 26 Oct 2012 05:59:04 -0400
In-Reply-To: <1351194021.2728.170.camel@pasglop>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Il 25/10/2012 21:40, Benjamin Herrenschmidt ha scritto:
>> > Probably you do need a variant of KVM_CREATE_IRQCHIP to create the
>> > IOAPICs/source controllers (Paul's proposal at
>> > http://permalink.gmane.org/gmane.comp.emulators.kvm.powerpc.devel/5674
>> > for example), assign chip ids to them, set the number of input lines,
>> > etc. but the configuration should work well with the existing ioctls,
>> > with no limit on the number of sources. 
> But what do you mean by "configuration" really ? I don't see anything in
> common there.

Wiring which MSI-X interrupts go to which source controllers.  If you
have one source controller per PCI bridge, you need to tell the kernel
the mapping between MSI messages interrupts and PCI bridges, and update
it whenever the MSI masking changes.

The other problem is configuring the redirection table.  If you need >64
sources you need ioctls like KVM_GET/SET_IRQCHIP_ONE_REG.

Paolo