From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: in-kernel interrupt controller steering
Date: Wed, 6 Mar 2013 06:57:21 -0500 (EST)
Message-ID: <1772234735.3176599.1362571041893.JavaMail.root@redhat.com>
References: <AAFBA41C-933E-4FC6-8962-280EF816AAC5@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
	Stuart Yoder <stuart.yoder@freescale.com>,
	Scott Wood <scottwood@freescale.com>,
	Paul Mackerras <paulus@samba.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	Gleb Natapov <gleb@redhat.com>
To: Alexander Graf <agraf@suse.de>
Return-path: <kvm-ppc-owner@vger.kernel.org>
In-Reply-To: <AAFBA41C-933E-4FC6-8962-280EF816AAC5@suse.de>
Sender: kvm-ppc-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

> > I agree.  But is the device really being created at CREATE_DEVICE
> > time? What happens if you create N CPUs and N-1 irqchips?
> 
> irqchip in CREATE_DEVICE is the IOAPIC, not the LAPIC. The LAPIC gets
> spawned at vcpu creation.
>
> > On x86, the LAPIC is created magically together with the VCPU.
> 
> Yes, and so far I haven't seen any proposal to change this even in
> the CREATE_DEVICE world.

But don't you need anyway an id to get/set the device properties of
the per-VCPU irqchip?  If you were adding the x86 irqchip with the
new API, what would be the replacement of KVM_GET_LAPIC/KVM_SET_LAPIC?

Paolo