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 12:15:23 +0200
Message-ID: <508A62BB.4010209@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> <508A5EE3.6070709@redhat.com> <CAFEAcA8qi7-v5Noyyt_ur-u7GoKgdG4F+xa9AZD-55gqZEYvAQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	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>
To: Peter Maydell <peter.maydell@linaro.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:2029 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754324Ab2JZKPq (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 26 Oct 2012 06:15:46 -0400
In-Reply-To: <CAFEAcA8qi7-v5Noyyt_ur-u7GoKgdG4F+xa9AZD-55gqZEYvAQ@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Il 26/10/2012 12:09, Peter Maydell ha scritto:
>> >
>> > The other problem is configuring the redirection table.  If you need >64
>> > sources you need ioctls like KVM_GET/SET_IRQCHIP_ONE_REG.
> Why would you want an extra ONE_REG-like ioctl? The existing ONE_REG
> ioctls have plenty of space in the ID range to allow you to devote
> a subsection of it to your irqchip. (This is exactly how the ARM
> VGIC save/load is going to work.)

Ok, I stand corrected. :)

> Whether you want to do startup configuration and board wiring via
> the same ioctl that handles runtime state save/load/migration is
> a different question, of course.

QEMU's MSI-X routing is not x86-specific, so it should use the same
KVM_SET_GSI_ROUTING ioctl that x86 uses.

Paolo