From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [kvmarm] [RFC PATCH 0/3] KVM: ARM: Get rid of hardcoded VGIC addresses Date: Fri, 26 Oct 2012 06:39:06 +1100 Message-ID: <1351193946.2728.169.camel@pasglop> References: <1350173065-35350-1-git-send-email-c.dall@virtualopensystems.com> <507F172D.2030802@suse.de> <20121017221022.GA4333@bloggs.ozlabs.ibm.com> <1350518331.4678.114.camel@pasglop> <508675FC.7090901@siemens.com> <20121024005017.GA17834@bloggs.ozlabs.ibm.com> <5089656A.9010704@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Paul Mackerras , Jan Kiszka , Christoffer Dall , Alexander Graf , kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, kvm-ppc , Peter Maydell To: Paolo Bonzini Return-path: In-Reply-To: <5089656A.9010704@redhat.com> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Thu, 2012-10-25 at 18:14 +0200, Paolo Bonzini wrote: > As Jan said, there's more than a few similarities between the x86 and > PPC model. > > Taking inspiration from the x86 API, configuring the source controller > seems to be more of a task for KVM_SET_GSI_ROUTING (a very x86-centric > name, I must admit). Very x86 centric name, very x86 centric functionality as well with a very x86 centric implementation. I don't know what makes you think there's anything remotely re-usable but I looked at it a while back and there isn't that I can find. The "configuration" of the source controller consists of creating it with a number of sources and a BUID, that's about it. Then there's also APIs to extract/set its state for migration. Cheers, Ben.