From mboxrd@z Thu Jan  1 00:00:00 1970
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: in-kernel interrupt controller steering
Date: Wed, 06 Mar 2013 11:23:35 +1100
Message-ID: <1362529415.3548.15.camel@pasglop>
References: <9A4D26CC-338A-418B-B2EC-7FCA9B7E99C4@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "Overall list:Overall" <kvm@vger.kernel.org>,
	kvm-ppc@vger.kernel.org, Gleb Natapov <gleb@redhat.com>,
	Stuart Yoder <stuart.yoder@freescale.com>,
	Scott Wood <scottwood@freescale.com>,
	Paul Mackerras <paulus@samba.org>,
	Peter Maydell <peter.maydell@linaro.org>
To: Alexander Graf <agraf@suse.de>
Return-path: <kvm-ppc-owner@vger.kernel.org>
In-Reply-To: <9A4D26CC-338A-418B-B2EC-7FCA9B7E99C4@suse.de>
Sender: kvm-ppc-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Mon, 2013-03-04 at 23:20 +0100, Alexander Graf wrote:
> 7) Interrupt line connections to vcpus are implicit
> 
> We don't explicitly mark which in-kernel irqchip interrupt line goes
> to which vcpu. This is done implicitly. If we see a need for it, we
> create a new irqchip device type that allows us to explicitly
> configure vcpu connections.

I don't understand that one. The connection from irq source goes to
which vcpu is an intrinsic part of the configuration of that interrupt
line on XICS and MPIC and probably any other, which is set explicitly by
the guest using MMIO or hcalls ...

Cheers,
Ben.