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, 06 Mar 2013 15:37:36 +0100
Message-ID: <513754B0.3000800@redhat.com>
References: <469599439.3185295.1362572055225.JavaMail.root@redhat.com> <1777B6DD-B341-4531-BE43-7B0161B1D093@suse.de> <20130306131424.GR11223@redhat.com> <FA9CF50F-09B8-4DE8-A2E6-0054E89DFD4A@suse.de> <20130306135605.GA13471@redhat.com> <8A2E7B22-8933-42CF-AD7D-6AC27F1E4B1F@suse.de> <51374ED8.7010701@redhat.com> <9BDDAB95-84CC-4687-AE03-8EF81AC2837F@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Gleb Natapov <gleb@redhat.com>, 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>
To: Alexander Graf <agraf@suse.de>
Return-path: <kvm-ppc-owner@vger.kernel.org>
In-Reply-To: <9BDDAB95-84CC-4687-AE03-8EF81AC2837F@suse.de>
Sender: kvm-ppc-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

Il 06/03/2013 15:30, Alexander Graf ha scritto:
>>> >> KVM_IRQ_LINE is basically an IOAPIC interrupt line assert. That's
>>> >> fine. That ioctl should get an ioapic device handle to work on.
>> > 
>> > It would be a KVM_SET_DEVICE_ATTR in your case, right?
> No, it would be KVM_IRQ_LINE. It's basically a command ("do this
> interrupt"), not an attribute modification. Unless we want to
> implement the IRQ pin levels on the "IOAPIC" as attributes. Then it'd
> be a SET_DEVICE_ATTR. But that makes edge interrupt injection harder
> / less obvious ;).

Why is it harder?  You don't really inject interrupts, you inject
changes of the pin status, don't you?

Paolo